Saving the current user catalog of a pubset

To save the user catalog, the $TSOS.SYSSRPM.BACKUP file must be saved with the ARCHIVE subsystem (SAVE statement) or HSMS subsystem (BACKUP-FILES statement). For the user, the process is basically the same as saving any other file, with the file name functioning simply as a placeholder. During the SAVE run, the current data is transferred from user management to ARCHIVE/HSMS while the actual.BACKUP file continues to act as a placeholder and remains empty.
For the saved data to take effect, the .BACKUP file must be read in from the backup prior to IPL or IMCAT (with RESTORE/RESTORE-FILES) and the IPL or IMCAT must be parameterized accordingly.

If a differential save of the file is required (operation SAVE ...,CHANGED=YES), this will always be performed, because the file will have been reopened by the system task that manages it after it was last processed by ARCHIVE.

An export for the .BACKUP file is rejected.

Since it is impossible to say for sure whether or not the contents of the saved user catalog have been manipulated during reconstruction, systems support must protect the file with suitable organizational measures.