General page

The General page contains the following fields.

Job version number

The version number of the sequence job, expressed as N.n.n, where N is the version number, and n.n is the bug fix number.

• The version number checks the compatibility of the job with the version of IBM® InfoSphere® DataStage® installed. This number is set automatically when InfoSphere DataStage is installed and cannot be edited.
• The bug fix number reflects minor changes to the job sequence design or properties. To change this number, select it and enter a new value directly or use the arrow buttons to increase the number.

Allow Multiple Instance

Enables the Director client to run multiple instances of this sequence job.

Short job description

An optional brief description of the sequence job.

Full job description

An optional detailed description of the sequence job.

The following compilation options specify details about restarting the sequence job if one of the jobs fails.

Add checkpoints so sequence is restartable

Enables this job to be restarted upon failure. If you enable this feature on a project-wide basis in the InfoSphere DataStage Administrator client, this option is selected by default when the sequence job is created.

Automatically handle activities that fail

Automatically handles failing jobs within a sequence (this means that you do not have to have a specific trigger for job failure). If you enable this feature on a project-wide basis in the InfoSphere DataStage Administrator client, this option is selected by default when the sequence job is created.

Important: When using this feature, avoid using any routines within the sequence job that return any value other than zero to indicate success. In InfoSphere DataStage, non-zero values indicate a failure.

For each activity that does not have a specific trigger for error handling, code is inserted that branches to an error handling point. If the compiler inserts code to handle errors, the following sequence of actions occur if a job within the job sequence fails:

• A warning is logged to indicate that the job finished with warnings.
• If the sequence job has an exception handler defined, the code uses that exception handler.
• If there no exception handler is defined, the sequence job fails with a message.

Log warnings after activities that finish with status other than OK

Generates a message in the sequence log if a job in the sequence job finishes with a non-zero completion code (for example, warnings or fatal errors). Messages are also logged for routine or command activities that fail.

Log report messages after each job run

Generates a status report for a job immediately after the sequence job runs. The following example shows the type of information that is included in the report:

**************************************************
STATUS REPORT FOR JOB: jobname
Generated: 2003-10-31 16:13:09
Job start time=2003-10-31 16:13:07
Job end time=2003-10-31 16:13:07
Job elapsed time=00:00:00
Job status=1 (Finished OK)
   Stage: stagename1, 10000 rows input
   Stage start time=2003-10-31 16:17:27, end time=2003
   -10-31 16:17:27, elapsed=00:00:00
      Link: linkname1, 10000 rows
   Stage: stagename2, 10000 rows input
   Stage start time=2003-10-31 16:17:28, end time=2003
   -10-31 16:17:28, elapsed=00:00:00
      Link: linkname2, 10000 rows
      Link: linkname3, 10000 rows