Retaining cycles of dump tapes

You can move dump cycles to storage locations for disaster recovery. Use additional options for pseudo-generation data groups, to retain and move by CYCLES using the old naming format as shown in Figure 1.

Figure 1. Moving dumps to storage locations

RMM ADDVRS -
DSNAME('bprefix.DMP.T¬¬¬¬¬¬.class.D¬¬¬¬¬.V%%%%%%') -
    COUNT(100) CYCLES LOCATION(REMOTE) STORENUMBER(2) -
    DELAY(1)

bprefix: Specifies the data set name mask that identifies the application.
T*: Is the time mask to mask the time the dump was created.
class: Specifies the DUMPCLASS you have defined to DFSMShsm.
D*: Is the date mask to mask the date the dump was created.
V%%%%%%: The six character volume serial number.
COUNT(100): Specifies to retain all dump cycles managed by DFSMShsm. 100 is the limit for the number of dump cycles.
CYCLES: Specifies that DFSMSrmm retain data sets based on cycles or copies of a data set.
LOCATION(REMOTE): Specifies the storage location called REMOTE to which the number of volumes for the data sets specified in STORENUMBER should be moved.
STORENUMBER(2): Represents a number less than the total number of versions to be kept. All other cycles are retained, up to the COUNT value in the HOME location.
DELAY(1): The current cycle is kept in the library for one day before being removed to the storage location.

You might need to use both types of dump vital record specifications until you have replaced all old retained volumes.