DSXchange

The error message suggests that your APT_COMPILER environment variable value is set to "cl" but no executable of that name can be found. This may be because the command search list environment variable (PATH) does not include "cl", or because "cl" simply does not exist on your system. Check that PAT...

The error message suggests that your APT_COMPILER environment variable value is set to "cl" but no executable of that name can be found. This may be because the command search list environment variable (PATH) does not include "cl", or because "cl" simply does not exist on your system. Check that PAT...

The error message suggests that your APT_COMPILER environment variable value is set to "cl" but no executable of that name can be found. This may be because the command search list environment variable (PATH) does not include "cl", or because "cl" simply does not exist on your system. Check that PAT...

RMM version 2.0 needs a recursive option, methinks.

Your DBA owes you at least an apology!

Welcome aboard, and thank you for posting a solution. :D

Should that last line be "PTION" or "OPTION"?
Do you know what its purpose is?

No.

The language is different, the logic is different, and parallel Transformer stage does not support reference inputs.

Maybe one of the sub-processes is still running. Try using a Monitor to see whether any stages are still running - choose the "show instances" option. Check using the list_readu command to see whether the job is locked by DataStage. Try switching to a different job in Director (status view) to see w...

SMP or MPP environment? You can't use the BASIC Transformer in a multi-machine environment unless DataStage server is installed on every machine whose fastname appears in the current configuration file. DSD.RUN is the piece of DataStage that runs "server" (DataStage BASIC) components. It is trying t...

Identical means exactly that - including operating system patches.

Have you tried re-loading the table definition, in case what's in your job is out of synch with what's in the Repository? Or re-importing, even?

What stage types are involved? You may need to run the job with APT_DISABLE_COMBINATION set to True to diagnose this one properly.

As far as DB2 is concerned, your DataStage job is just another client application. So all you need to do is exactly what you would need to do to connect via the DB2 command line interface. Nothing more. Remember that environment variables for DataStage processes are set in the dsenv script on UNIX p...

They are being recognized as NChar or NVarChar, and two bytes per character are being reserved.

True. Nested Ereplace() functions would but, like you, I would prefer the clarity of separate, cascading stage variables for ease of maintenance.