Some DataStage jobs (both Server and Parallel) feature an embedded Job Control Routine, written in DataStage BASIC. Rather than reproduce this Job Control routine as an embedded component of the generated Parallel Job, S2PX will instead separate the Job Control code into a newly-generated Custom Routine which is sequenced by an overarching generated Job Sequence.

Canvas Stages and Job Control

Here’s an example of a Sequence Job generated from a Server Job which features a Before Routine, After Routine, Job Control and a canvas of processing stages:

Generated Routine

The generated routine will be named after the original job with JobControl appended. For example, a Job named ProcessMyData will have its Job Control moved into a newly created DataStage BASIC Routine named ProcessMyDataJobControl. All generated routines will take a single argument (Arg1) and will feature a #INCLUDE DSINCLUDE JOBCONTROL.H entry to enabled the Job Control code to work without modification.

Open

Open

No Canvas Stages and Job Control

In cases where a Server Job does contain Job Control code but does not have any Stages on its Canvas then the generation of a (redundant) Parallel job is omitted, and the Sequence Job contains only the generated Job Control routine (along with Before and After routines, as appropriate.) For example: