Before aggregate backup control file, data file, and instruction/activity
log file tape volumes can be protected with RACF®, you must first define an aggregate backup
tape connected set by issuing the following command:
RDEFINE TAPEVOL HSMABR
RACF must be active and
the SETSYS TAPESECURITY(RACF) or TAPESECURITY(RACFINCLUDE) options must
be in effect for DFSMShsm to use RACF to
protect aggregate backup output tape volumes and add them to the HSMABR
tape connected set. For more RACF information
see
RACF environment for DFSMShsm.
Note: These tapes are not automatically
added to RACF unless the above
conditions are met at the recovery site. If these conditions are met,
the tapes are added to RACF (at
the recovery site) when the ARECOVER command is issued for this aggregate.
If TAPESECURITY(RACF) or TAPESECURITY(RACFINCLUDE) is specified and TAPESECURITY(EXPIRATION)
TAPESECURITY(EXPIRATIONEXCLUDE) is not specified,
then the expiration date is not written to the tape header label,
and the ARCEDEXT installation exit is not invoked.
Tape volumes added to
the HSMABR RACF tape
connected set are automatically removed by aggregate version rolloff
processing during aggregate backup processing, during EXPIREBV processing,
or if an aggregate backup failure occurs after the output tapes are
opened. A tape volume may be deleted from the HSMABR tape connected
set by entering the following RACF command:
RALTER TAPEVOL HSMABR DELVOL(volser)
ADDSD 'outputdatasetprefix.**'
If you use RACF DATASET
class profiles instead of TAPESECURITY(RACF) to protect the tapes and create the DATASET
profiles, you could define ADDSD to specify that ABARS created aggregates
are protected. You need a profile for each aggregate group you have
defined that uses a different aggregate group prefix.