Retaining DFSMShsm control data set backup tapes

To keep all cycles of DFSMShsm control data set and journal backup tapes until DFSMShsm releases them, issue RMM ADDVRS subcommands as shown in Figure 1:

Figure 1. Keeping DFSMShsm control data set and journal backup tapes

RMM ADDVRS DSNAME('authid.%CDS.BACKUP.V¬¬¬¬¬¬¬') -
    COUNT(99999) CYCLES
RMM ADDVRS DSNAME('authid.JRNL.BACKUP.V¬¬¬¬¬¬¬') -
    COUNT(99999) CYCLES

authid.**: Specifies the DFSMShsm prefix used for control data set backups.
%: Represents the characters M, B, or O used by DFSMShsm for each of its control data sets.
V¬¬¬¬¬¬¬: Represents the version number DFSMShsm maintains as a pseudo-generation data group.
COUNT(99999): Specifies to retain all data sets forever or until DFSMShsm releases the volume by notifying DFSMSrmm through the EDGTVEXT installation exit.
CYCLES: Specifies that DFSMSrmm retain data sets based on cycles or copies of a data set.

All versions of each of the control data set and journal backups are retained until released when DFSMShsm calls DFSMSrmm to release the tape volume. You can optionally use any of the RMM ADDVRS subcommand operands to meet your movement and retention requirements. For example, you can use the LOCATION and STORENUMBER operands to identify that movement is required.