DSXchange

If you want some help with your batch job you'd need to post the code or at least enough of it to emcompass the "won't compile" part and people here could get you going there. However, a Sequence job (not a Server job) with the Start/End Loop and UserVariables stage to run your Parallel jo...

Hmmm... from what I recall, usually those "DSD.WriteLog" fatal messages are user controlled aborts. Meaning a routine or derivation (etc) has coded into it a call to the DSLogFatal() function and something triggered that code.

Any chance something like that is going on?

A function should work, I would think, then you could just include it as a column value in your reference sql.

Go for it. Whatever is easiest, perhaps adding the corrected job to the zip as a separate dsx with "_new" or "_corrected" appended to the job name?

And... your resolution was?

No, that's the place.

Never said it was a good idea but it would work.

Or a very simple Server job will handle this all automagically.

I thought this was a consistent error rather than a "sometimes works and sometimes doesn't" kind of issue. The latter generally falls into two camps - data related or a resource issue. Yours is sounding like a resource issue. And I didn't realize you were talking about a Server Shared Cont...

You'd have to know your maximum possible key values and define a output link for each. Do you?

Involve your official support provider. And find out exactly what kind of "space issue" you had, particularly where and how it was "taken care of".

The only people that will have 'that info' are people working at your company.

What happens if you map your target IP_ID field from the reference IP_ID field?

Where was using an "undefined" array size ever mentioned? All I've been trying to get you to try is an array size of 1. One. Uno. Ek.

Regardless, involve your official support provider. Seems to me you've either hit a limitation in the product or a bug.

I assume we're talking about "looping" inside a PX job rather than a Sequence job, the latter of which goes back well before the 8.x version. First question would have to be why - what makes you think you need to do any kind of "looping" in a job? What are you trying to accomplis...