Saving the user definition file

ARCHIVE allows the user definition file $TSOS.SYSSRPM to be backed up. This file can however not be saved in itself, but the content can be copied to the file
$TSOS.SYSSRPM.BACKUP and can then be saved.

The files $TSOS.SYSSRPM and $TSOS.SYSSRPM.BACKUP exist on every pubset and are managed by SRPM. They are opened on importing the pubset and closed on exporting it.

• The file $TSOS.SYSSRPM with the user definitions cannot be saved, exported or migrated.

• The file $TSOS.SYSSRPM.BACKUP is usually empty and is used to save the file $TSOS.SYSSRPM.
  $TSOS.SYSSRPM.BACKUP can however be saved, but not exported or migrated. Only a full save is possible.

  The file $TSOS.SYSSRPM.BACKUP cannot be exported for security reasons. Systems support however can transfer it to another system if necessary using the SAVE/RESTORE functions. With the SAVE/RESTORE functions, ARCHIVE guarantees that only a user with TSOS privilege can restore this security-sensitive file.

Saving the file $TSOS.SYSSRPM.BACKUP

A save can be initiated in ARCHIVE with the SAVE statement or in HSMS with the BACKUP-FILES statement. If an ARCHIVE subtask processes the file $TSOS.SYSSRPM.BACKUP during a save, the following actions are automatically carried out:

1. ARCHIVE notifies SRPM that the save of the user definition file has begun.

2. SRPM copies the data from $TSOS.SYSSRPM to $TSOS.SYSSRPM.BACKUP.

3. ARCHIVE saves the file $TSOS.SYSSRPM.BACKUP on the specified save volume.

4. Once the save of the file $TSOS.SYSSRPM.BACKUP has finished, ARCHIVE informs SRPM.

5. For security reasons, SRPM deletes the data from the file $TSOS.SYSSRPM.BACKUP.