Restarting batch jobs

When an ABEND occurs during the execution of an application program that uses the QUICKSTART for MVS product, investigate the cause of the ABEND and resolve any known problems. This might involve JCL changes (perhaps to increase the SPACE= allocation of an output sequential file), or application program modifications. If application program modifications are found to be necessary, implement those modifications following the guidelines presented in this section. After any necessary modifications are performed, restart the job step using the RESTART=stepName subparameter of the job Statement. If you have a Job Restart Manager, it should be configured to do this automatically.

During application program restarts, QUICKSTART optionally (via an installation option) requests verification from the Console Operator that the application program is, indeed, in a restart mode. If the Console Operator replies that no restart is in progress, QUICKSTART ABENDs immediately. Otherwise the restart proceeds normally. Most sites do not use this option.

In API Mode the application program provides QUICKSTART with the value of the  Program Name through a field in the application program's Working Storage Section. In Transparent Mode, the Program Name is passed to QUICKSTART in a QSCTRL1 DD card. This field value is used to help generate dataset names for the QUICKSTART Checkpoint Datasets. It is very important that this Program Name, the job name, and Step Name are not altered between any of the restart attempts.

Note

If these fields are changed within the application program, QUICKSTART will be unable to associate any previously checkpointed information with the restarted application program and any restart attempt for the job step will fail. To maintain this association, the QUICKSTART Checkpoint Datasets must be renamed correspondingly.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*