Advanced Topics › Control and Checkpoint File Considerations › How You Allocate Control and Checkpoint Files › Allocate Checkpoint Files

Allocate Checkpoint Files

Checkpoint files are not shared like DASD control files so you must allocate a unique checkpoint file for each system. You can allocate checkpoint files on non-shared DASD volumes and place them on volumes with other data sets. Checkpoint files are accessed much less frequently than control files.

You use the ALLOCATE command to allocate new or relocated DASD checkpoint files. Checkpoint files are not shared files like DASD control files, so you must allocate a unique checkpoint file for each system.

To allocate a checkpoint file

1. Issue the following command to determine the next available checkpoint file number identified by the checkpoint file prefix (MIM.SYSx. MIMCKP):

   DISPLAY FILES 
   

2. Customize the sample JCL found in the ALLOCKPT member of the CAI.CBTDJCL data set to create a new checkpoint file.
3. Issue the following command:

   ALLOCATE DSNAME=newdsn,DDNAME=MIMCKPnn
   

   nn

   Specifies the number of the new checkpoint file.

4. To confirm that the new file was added to the checkpoint file list, reissue the following command:

   DISPLAY FILES