z/OS DFSMSdfp Checkpoint/Restart
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


SYSCHK DD Statement

z/OS DFSMSdfp Checkpoint/Restart
SC23-6862-00

If you wish to perform a deferred checkpoint restart you must include a SYSCHK DD statement in the resubmitted job. This DD statement specifies the checkpoint data set that contains the checkpoint entry to be used in the restart. The SYSCHK DD statement cannot be included when a deferred step restart is to be performed.

The statement must precede the first EXEC statement in the job that performs a deferred restart at checkpoint. It must follow the JOBLIB DD statement if the JOBLIB DD is present. The desired checkpoint entry must be named by the checkid subparameter of the JOB statement RESTART parameter.

The following requirements and restrictions apply to the SYSCHK DD statement:
  • The statement must contain or imply DISP=(OLD,KEEP).
  • For SMS-managed data sets, UNIT and VOL=SER are not required.
  • The statement must define the checkpoint data set. It must specify its name. If it is not cataloged, the statement must also specify the device type or device number and specify the volume serial number.
  • If the volume containing the checkpoint data set is mounted on a JES3-managed device, the SYSCHK DD statement must not request deferred mounting.
  • The SYSCHK data set cannot be multivolume or concatenated. If the checkpoint data set is multivolume, the SYSCHK DD statement must specify, as the first volume of the data set, the volume and data set name that contain the desired checkpoint entry. The serial number of the volume containing a particular entry appears in the console message that is written when the entry is written.
  • If the checkpoint data set is partitioned, the DSNAME parameter on the SYSCHK DD statement must not contain a member name.
  • If a RESTART parameter without the checkid subparameter is included in a job, a SYSCHK DD statement must not appear before the first EXEC statement of the job.
  • If a RESTART parameter is not included in a job, a SYSCHK DD statement appearing before the first EXEC statement in the job is ignored.
  • A SYSCHK DD statement appearing in a step or procedure step of a job is treated as an ordinary DD statement; that is, the name SYSCHK has no special meaning in that case.
An example of a non-SMS SYSCHK DD statement is:
   //SYSCHK DD  DSN=dsname,DISP=OLD,UNIT=name,
   //           VOL=SER=volser

For existing SMS-managed data sets, the system ignores the UNIT keyword and any volume serial on the DD statement.

An example of an SMS SYSCHK DD statement is:
   //SYSCHK DD  DSN=dsname,DISP=OLD

     

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014