Figure 1 shows how to keep 10 tapes written by ABARS that were created under DFSMS, and provide storage location management for them based on cycles as if they are a generation data group definition.

When you define a vital record specification as shown in Figure 1, DFSMSrmm keeps 10 versions of each of the aggregate backup output data sets and any copies ABARS created. DFSMSrmm retains the latest 10 versions in the REMOTE location and any others in the home location. If there is only one copy of each aggregate backup version produced, and there are 10 versions of each aggregate backup, DFSMSrmm keeps 10 versions of each aggregate backup. If there are 2 copies of each, DFSMSrmm keeps 10 versions of each copy of each aggregate backup.

In the example, the COUNT and STORENUMBER are the same. You could use different values where STORENUMBER is less than or equal to COUNT when you want to store a number of tapes offsite.

RMM ADDVRS DSNAME('outputdatasetprefix.%.C%%V¬¬¬¬') -
    COUNT(10) CYCLES -
    LOCATION(REMOTE) STORENUMBER(10) -

outputdatasetprefix

Specifies the same value as entered in the ISMF aggregate processing application as the prefix to be used for output data set.

%

Represents the characters D, C, O, and I that are used by DFSMShsm ABARS processing.

C%%

Represents the copy number.

V¬¬¬¬

Represents the version number DFSMShsm maintains as a pseudo-generation data group.

COUNT(10)

Specifies the number of versions of the aggregate backup to retain.

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(10)

Represents a number of versions to be kept in a storage location.