Deciding which step of an operation has failed

More than one step might meet the criteria set by the selection parameters. If you specify the STEPCODE parameter but not the ERRSTEP parameter, more than one step can have a return code that would cause recovery. If both the STEPCODE and JOBCODE parameters are given but not the ERRSTEP parameter, two or more steps might meet the criteria, one as determined by the JOBCODE, and the others as determined by the STEPCODE. In these cases, the first step that fulfills the selection criteria is selected as the failed step for recovery purposes; for example, when determining the restart step.

A failure can also occur at job or started-task initialization time before a step is entered. Such failures have the error code JCLI or CAN. Assume that a RECOVER statement is specified that has RESSTEP=% and no ERRSTEP parameter, indicating restart at failing step for any errors in the job. For JCLI and CAN errors, the restart is from the start of the job.

When a job or started task is transferred from one workstation to another and recovery occurs, HCL Workload Automation for Z assumes that the step that was executing at the time of failure was the step that would have followed the last step that HCL Workload Automation for Z knows completed (that is, for which it has a step-end event).

JCCE errors mean that the job completion checker (JCC) has terminated its processing of the SYSOUT file. Such errors are not associated with a specific step. If RESSTEP=% is specified but the step return codes show that the executed steps have completed successfully, the job or started task remains on the ended-in-error list. The same is true for other error codes set by JCC.