DSXchange

Phil Hibbs wrote:Anything in the .dsx file that is not a job will be dropped.

Why?

Six sequences each invoking routine, those six sequences called from master sequence.

Last year there were four or five prep classes, DataStage was one of them.

APT_CONFIG_FILE is not set in your UNIX interactive process.

Code -2 means "not in a runnable state": has the job design been changed (even inadvertently) and not re-compiled?

You can compress a Data Set (you have to work out where all its data files are, of course) and doing so renders it unusable by DataStage. The gains are negligible because data are already in binary form within a Data Set.

Create more stage variables whose derivation expression tests the business rule(s) applicable to each of the first set of stage variables.

Did you post this question in the QualityStage forum for any particular reason?

... and a few other things as well, such as having APT_ORCHHOME and APT_CONFIG_FILE set. Usually all this can be achieved by executing the dsenv script in the $DSHOME directory.

would you say that parallel jobs are faster to run on the server even if there's only 1 processor compared to datastage server jobs? Probably not for small to medium volumes, because the startup overhead of a parallel job is significant compared to that of a server job. Possibly not for large volum...

In parallel @OUTROWNUM starts from 1 on every node. Prefer a stage variable or generated column that is initialized to the partition number (0, 1, 2, 3 for example) and incremented by the number of partitions (4 for example).

Use ODBC driver for text files.

Not in version 7, but yes in version 8.