DSXchange

The processing in Server isn't all that different from PX. Hashed files do the lookup part and you need to handle the 'CDC' by comparing old and new data yourself.

What's "not working" about what you are doing? And isn't that backwards from your original post?

Try without the semicolon. I have called packages from the SP stage without issue in the past, any reason not to use it?

I don't see why not, a proc is a proc, package or otherwise. Have you tried it? Had issues? Have a more specific question?

Then some combination of a check of the day plus the %E format tag to get the 'day of week' to check for days 1 thru 3 seems to be in order.

"Normal maintenance" doesn't really tell anyone anything. And are you saying someone edited your dsenv file and removed the Oracle environment variables? If so, that needs to be restored, a uvregen done and DataStage restarted for those changes to take effect.

Unless they mean the first three business days, or the first three weekdays of the month.

Stored Procedure stage.

How one would check is detailed here.

Silly question perhaps, but is your installation "NLS Enabled"? Meaning, was that option selected when the product was installed? Not certain that's even a issue here, more of a curiousity on my part.

Good job tracking that down... not sure that is a "workaround", however.

Interesting... what kind of operations / transformations are you performing on those decimals in the job?

Rather than continuing to guess what may or may not be going on here, why don't we wait for the OP to come back and hopefully clear things up for us?

You've already answered this - run fewer jobs at the same time, your system does not have infinite resources and cannot handle the load when all run simultaneously.

Any other way to answer your second question? No.