Job completion code: +JOBRC

JOBRC allows the user to assign a completion code for the entire job based on the completion codes of its steps. z/OS 1.13 allows the user to set the job’s completion code in the JCL JOB statement using the JOBRC parameter. This parameter determines how the JOBRC is calculated from the completion codes of its steps.

The parameter has the following options:

• The highest return code from the steps (the default) – this is the same as how Control-M assigned the job’s completion code prior to z/OS 1.13. If the job's execution fails because of an ABEND, the job completion code is set to the last ABEND code.
• The return code of the last step - in this case the job’s completion code is based on the completion code of its last executed step.
• The return code of a specific step - in this case the job’s completion code is based on the completion code of a specific step identified by its name.

Control-M extracts the JOBRC, which is calculated by JES2 or JES3 based on the JOBRC parameter specified in the JCL JOB statement, and use it for the job analysis during post processing.

An ON PGMSTEP +JOBRC statement can specify any DO action to be processed when the extracted JOBRC fits the codes specified in the statement. JOBRC is extracted in all z/OS releases (in releases earlier than z/OS 1.13, it is set equal to MAXRC) so ON PGMSTEP +JOBRC can be handled in any z/OS release.

In some special situations Control-M does not extract the JOBRC. Either Control-M is not able to extract JOBRC (when JOBRC not supplied by z/OS or JES), or it is assumed that users do not require that Control-M extract JOBRC (when the results based on JOBRC would be different than what users actually need). Some special situations are described in the following examples:

• The job execution was terminated by the 'Cancel' operator command.
• The job execution was terminated prematurely according to the COND= parameter specified in the JOB JCL statement.
• The job execution is the restart run performed by Control-M/Restart and the ALLRUNS Control-M/Restart installation parameter, which specifies whether Control-M considers during post processing all the previous runs of a job, is activated.

If JOBRC is not extracted, the ON PGMSTEP +JOBRC statement is ignored.

An ON PGMSTEP +JOBRC statement cannot be connected by AND/OR Boolean relationships with other ON PGMSTEP statements.

Since JOBRC is not used for evaluating the OK/NOTOK status of job when DO OK/NOTOK actions are defined in the ON PGMSTEP statements of step(s), DO OK/NOTOK actions in ON PGMSTEP +JOBRC cannot be defined together with DO OK/NOTOK in the ON PGMSTEP statements of step(s).