DSXchange

Just to confirm, you use -wait or -jobstatus - not both. Wait means wait for the job to complete and pass back a standard zero/non-zero return code while jobstatus means wait for the job to complete and pass back an internal 1/2/3 (etc) return code.

Should work fine with the -wait instead of -jobstatus, I do believe. However, I for one would never use the Before area for something like that, really should be part of a Sequence IMHO.

Hmmm... looks like someone missed the NEVER in the previous post.

Perhaps Ernie might know how to increase the memory space for the process, but that should certainly be one way around your "OutOfMemoryError" issue.

Import fewer files at one time.

Double-check where you posted, where we are right now. We are not in the parallel jobs forum.

No, the comment from Ray is directed at your choice of forum to post in.

While you may not be able to do that, you can certainly do that in a Server job.

Would make a nice addition to the FAQ forum, me thinks.

The problem is not "with the table" but rather with how the data is being sent to the table, something that is causing a deadlock to occur. Talk to your DBA about possible causes and solutions to that error, so you understand what is going on in the database. Typically in DataStage it invo...

You mean, other than what has already been posted?

If by "job run level" you mean "dsjob from the command line" then you need to use the -warn option as noted in this thread. Running from the Director you will have a Limits tab where tha ... unfortunately it is not triggered from the command line. but triggered using sequence. i...

Yes, the encryption is not strong and certainly not meant to be any kind of crack proof - any frequent readers here should remember it has already been "cracked"... more than once. You can compare encrypted values across jobs to ensure the original values are indentical, other than that I'...

From what I can tell, yes.

That is how you should do it, if that's not working you'll need to report it to your official support provider. What exact 8.x version are you running?