If a job cannot complete executing because of system failure and the job requested job journaling, the job is restarted (warm started) by the system. If the job is eligible for automatic restart, the operator is sent message IEF225D asking if the job should be restarted. If the job is not eligible for automatic restart or if the operator indicated that restart should not be attempted, any temporary or VIO data sets the job allocated are deleted and the job is processed based upon the FAILURE option specified in the MAIN JCL statement. If FAILURE=RESTART is specified, JES3 automatically reschedules the job for execution from the beginning of the first step.

If automatic restart is requested for a job, the job's data sets are set up by JES3 for the first job step and not for the step being restarted. Canceling a job in a dependent network prevents successor jobs from executing if they are dependent upon successful completion of the canceled job. Any operator commands in the input stream of the job step being restarted are not executed. Restart of JES3 controlled jobs may be accompanied by message IAT2006 and/or IAT2575. For responses to these messages see z/OS JES3 Messages.

Note: A job that contains references to non-SMS-managed generation data sets that are referenced by a relative generation number of +1 or greater and with a disposition of OLD, SHR, or MOD is failed by the JES3 interpreter service unless the UNIT parameter is included on the DD statement. With UNIT specified, the JES3 interpreter service permits this data set to be allocated on a deferred basis.