DSXchange

You can use user variables (see User Variables in job sequences). You can also use the $UserStatus activity variable downstream of a Job activity.

Create a before-job subroutine that checks whether the job is being run under control. If it is not, set the error flag (ErrorCode argument) to a non-zero value, and log a message indicating that the job can not be run in isolation.

Use the DIGITS Transform.

Exporting a single routine using the command line is not possible.

It's called InstConf.pdf and it's to be found on each machine on which DataStage client is installed, at C:\Program Files\Ascential\DataStage7.5\Docs (if you installed into the default location).

Incorporate the following code at the top of your routine.

Recompile the routine, and all will be well.

The header file JOBCONTROL.H contains definitions for all the mnemonics for constants used in the DataStage API.

Yes that is correct, because the two caches are separate. Disable cache and set "lock for update" in your job design.

Try asking specific questions on DSXchange. DSXchange is not intended to be a substitute either for training or for support. It is a user forum only. Start a new thread for each new question.

Stage variables in Transformer stage, detecting change of key value and populating the appropriate fieds (change if non-zero). Output second row only.

The run that had the failure had a buffering problem (shortage of memory? I/O device?) - the run that did not have the failure also did not have the buffering problem. These intermittent faults are the hardest to diagnose!

There is online help, there are manuals and there is the Search utility in this forum.

Do you want one of us to take your interview and/or certification exam too?

For less than 30c per day you can purchase premium membership which will allow you to read fully answers by the five premium posters and to have access to a greater range of the training and other materials offered by DSXchange. All revenue raised from premium memberships is devoted to hosting and ...

Looks to me like your scheduler (AutoSys) is changing the PATH environment variable to suit its own purposes - putting itself up front. DataStage jobs pick theirs up from the dsenv script. For whatever reason (primarily because AutoSys works via dsjob command) the PATH environment variable is not be...

No, they'll write at the same time. It's only when the Hashed File stage as an input link and an output link that what your vendor calls "dangerous" occurs, or when you're writing to the hashed file in one stage with write cache enabled and reading from the hashed file in another stage with read cac...

Put a Column Generator stage on each left input link to generate the six columns. Map the relevant column only from the right input to the output. Run all these through a Funnel stage then through a Transformer or Aggregator stage to select the appropriate value.