Using RACF DATASET class profiles

You can implement tape data set protection for DFSMShsm volumes by using DATASET profiles just as you can for any other DASD or tape data set in the system. This is applicable for installations that do not want to use the SETSYS TAPESECURITY values of either RACF, or RACFINCLUDE, because you do not want the RACF® TAPEVOL class to be active. If you do not use RACF or RACFINCLUDE, then you must use EXPIRATION, EXPIRATIONINCLUDE, or the default of PASSWORD.

You have two choices for using RACF DATASET class profiles:

Driven by SETROPTS TAPEDSN
Driven by DEVSUPxx TAPEAUTHDSN=YES

In either case you must have generic DATASET class profiles created that cover each of the data set name prefixes that DFSMShsm currently uses:

ADDSD 'mprefix.**': Specifies the DFSMShsm-defined migrated data set prefix.
ADDSD 'bprefix.**' : Specifies the DFSMShsm-defined backup and dump data set prefix.
ADDSD 'authid.**': Specifies the DFSMShsm prefix used for control data set backups.
ADDSD 'bprefix.DMP.**': If you want dump tapes to be protected in a different way to backup tapes.
ADDSD 'outputdatasetprefix.**': Specifies that ABARS created aggregates are protected.

The access list for these data set profiles should only have the DFSMShsm or ABARS userid added to it. For more information, see Creating user IDs.

For information about security options, see z/OS Security Server RACF Security Administrator's Guide.

For information about the DEVSUPxx parmlib member, see z/OS MVS Initialization and Tuning Reference.

For more information about protecting DFSMShsm tape volumes with TAPEVOL, see Protecting tapes.