On a restart:
- The joblog and all other SYSOUTs will be extended with new data unless they have already been printed/deleted.
- Any DISP=NEW datasets will cause an already existing dataset to be deleted before allocation.
- Any DISP=MOD datasets that already exist will be extended.
- Any DISP=OLD datasets will be over-written.
At the conclusion of the restarted job, its new execution state (step condition codes) will be saved for a future restart.
Restart processing might issue one or more messages about steps that are skipped and the COND CODES used for those steps when
conditional evaluations are performed. For details, see the message topics listed below under
Related reference.[9]
Notes:
- A non-unique restart step/procstep is resolved to its first occurrence and a message is issued upon restart. This is the same
behavior as RESTART= on the JOB statement.
- When a job is deleted from the
Output Hold queue in ESMAC, from the casout command, or via the automated spool cleanup mechanism, all traces of the job are removed
and it can no longer be restarted.