Run Time Module Restart/Rerun Mode Processing 

In Restart/Rerun mode, the Run Time Module retrieves all information for the JOB from the Journal for the last run of the JOB and compares it to the current JOB. All step, program, and dataset information must match the current run of the JOB exactly. If it does not, the Run Time Module will fail. The Run Time Module then determines which JOB steps to rerun, performs catalog and dataset maintenance, GDG bias adjustment, and then causes the appropriate JOB steps to be rerun.

The Run Time Module then examines the PARM= information passed on the EXEC statement that executes the Run Time Module to see if the steps to be rerun have been explicitly specified. If they have been, it attempts to rerun those steps. If the step specified is one that the Run Time Module has determined is not restartable or is marked in the Journal as not restartable, the Run Time Module will fail and the JOB will not be rerun.

If specific restart information is not supplied in the PARM= parameter, the Run Time Module detects the first step in the JOB that failed in the last run of the JOB and restarts the JOB either in that step or in the first restartable step prior to the step that failed.

After determining which steps are to be rerun, the Run Time Module deletes and uncatalogs any datasets that were created and/or cataloged in the previous execution of the steps that are to be rerun. It also resets single volumes, sequential, and DASD datasets allocated DISP=MOD to their state prior to that previous execution of the JOB. GDG bias adjustment is performed as part of this procedure. GDG bias adjustment consists of replacing the relative GDG dataset names with the explicit GDG dataset names allocated in the previous execution of the JOB.

Finally, the Run Time Module will modify the relevant MVS control blocks so that only the required steps will be executed.

Note: The UC4 melder steps will never be skipped by Run Time Module processing.