DSXchange

Two readers per node?

So there's still the same total volume of data. Why do you believe this will alter any problem you're having with heap allocation?

Prevention is always better than cure. Make sure that whatever it was that timed out does not need to do so. Often timeouts are caused by overloaded servers. In this particular case the problem appears to be in the IPC interface between the parallel job and the server shared container.

Give thought to better subject selection please.

But you're not one of the ancient masters of the UniVerse.

All of these are documented in the manual and in the tutorial. I, for one, do not propose to waste my time replicating those sources. To get you started, name type is a generated field containing "I" for "individual name" or "O" for "organizational name" when ...

I believe that this becomes possible in 8.1 (or maybe 8.1.1).

Anyone with anything to say will do so when they can.

Meantime what experimentation have you done, and with what results?

(It's not always fun being on the leading edge.)

Define "performance". You can install NLS but not enable it; this will work like you did not install it. Enable/disable NLS via the NLSMODE configuration parameter in the uvconfig file. With NLS enabled, there is necessarily a processing overhead, because DataStage now uses Unicode interna...

If the output is Decimal(15,2) then the "padding" will occur automatically. If the output is a string, then you need something like Right(Str("0",15) : InLink.TheField, 15) It will be more efficient to initialize a stage variable to Str("0",15) rather than calculate tha...

By "sync" do you mean that you need to verify that they are the same, or force them to be the same? If the latter, what do you need to do with jobs that are still under development and have not yet been tested?

I think the time has come for Kshitij Rawat to write out in English the precise transformation requirement.

By doing that, the actual question may answer itself.

UV.ACCOUNT is not in the XMETA database at all. It is a "system table" for the DataStage server engine itself.