DSXchange

First suggestion - search here for that error message, it has been discussed here many times.

What kind of volume are we talking about in this table? If it's not too large, then a 'Clear' (transactional delete) rather than a truncate would avoid the problem as well. What batabase, btw?

Does one not have to license Server jobs for Sequence jobs to function, or will they work regardless?

Go back up from there to the first BEGIN DSxxxxx record, depending on what you mean be "build name". If it means "job name" then go back up to the first BEGIN DSJOB record you find and the Identifier record immediately after that would be the job name.

ray.wurlod wrote:Clear (probably) issues a DELETE command, which will be logged in the transaction log.

Right, it does.

Then how exactly would it return any rows? What is it doing?

Ah... there was another post with this exact same issue. I didn't see the first place it was set, just the later one where it looks more correct. Seems like that one should 'correct' the issue with the first one.

Seems like the FOR loop is handling that aspect ok to me. I'm just wondering why the loop when all it's going to return for the "Ans" is the last iteration of the loop?

I think you're in the wrong thread, Ray.

So... this stored procedure is a source in your job?

What is the abort? Is your password encrypted and if so, does it work as an environment variable when not encrypted?

That wouldn't cause this problem. Perhaps others but not this one.

Make sure your LD_LIBRARY_PATH is all one line, that there's no hard return in it where it looks like it breaks.

That won't help, it's not the field delimiter that's the issue, it's the fact that string fields are double-quoted and then have them inside as well. You could try removing that property from the field and then trim the quotes from inside the job, I would think.

It would be good to know, one way or the other. And you still need to take this error to your DB2 DBA.