Deferred restart
If the programmer submitting the job has provided for a deferred restart and the job ends abnormally, the programmer must resubmit the job for the deferred restart. To restart the job, the programmer must provide a restart deck for submission to the system through the system input reader. The JCL statements to be included in the restart deck are described in detail in z/OS MVS JCL User's Guide.
- The job entry subsystem is the same.
- The release number is the same.
- The link pack area modules in use at the checkpoint reside in the same storage locations.
- An area of storage identical to the original area is available to a V=R job.
IEF209I VIRTUAL STORAGE UNAVAILABLE FOR jobname.stepname.procedure
- The link pack area expands into the required storage. This expansion can occur if an IPL has been performed between the original execution of the job and the restart. If it does occur, contact your system programmer for a respecification of the system parameters and reIPL using the new values.
- The system storage area expands into the required storage. When this expansion occurs, contact your system programmer for a respecification of the SQA and CSA system parameter and reIPL using the new values.
When a job restarts correctly, you receive two messages: IEF006I JOB RESTARTING and IEF008I JOB RESTARTED. If, for V=R jobs, these messages do not appear, enter DISPLAY A,L to see if a system task or other job is using the required storage. You can then stop or cancel the conflicting job. The system might ask you to mount data volumes other than those required at the beginning of the job. In addition, any card input data sets that have been used by the failing job step must again be made available to the system.
For more information on deferred restart, see z/OS DFSMSdfp Checkpoint/Restart.