The checkpoint file $TSOS.ARCHIVE.CHKPT is created with this file name during the first ARCHIVE run. It must remain under this user ID and its name may not be changed.
The checkpoint file contains an entry for each current save version and, if the run was carried out with RESTART=YES, restart points, i.e. checkpoints written by ARCHIVE from which abnormally terminated ARCHIVE runs can be restarted. Information is also written to this file (even with RESTART=NO) in the case of RESTORE runs for partially saved files. The file ARCHIVE.CHKPT is cataloged under TSOS. It can be deleted at any time by the system support if it is too large and contains no tasks (ARCHIVE or HSMS) which have to be restarted.
/MODIFY-FILE-ATTRIBUTES. If the file does not have this read password, ARCHIVE will not accept it as a valid checkpoint file.If the checkpoint file has become too large and does not contain any processes waiting to be started (ARCHIVE or HSMS), the system support can delete it (DELETE-FILE ...,IGNORE-PROTECTION=*READ-PASSWORD).
After specification of the read password, the checkpoint file can be reorganized using PERCON (see the “PERCON” manual [13]) even if it is not empty. Prior to this, however, the system support must replace the read password assigned by ARCHIVE by another one (see the first note above in this list).
Any alias name is ignored if the complete name of the checkpoint file is specified.