You can control the actions that DFSMSrmm takes on RACF tape profiles through the DFSMSrmm OPTION TPRACF command and your installation's RACF options. For more information on OPTION TPRACF, see Defining system options: OPTION.

If you are running DFSMSrmm with DFSMShsm, see Securing tapes when running DFSMShsm and DFSMSrmm. See z/OS Security Server RACF System Programmer's Guide for information about RACF tape security. See z/OS MVS Initialization and Tuning Guide for information about DEVSUPxx tape security.

Independent of the TAPEAUTHDSN setting, DFSMSrmm TPRACF processing considers just the RACF tape protection options. Using those RACF options to protect volumes, you can specify one of these actions:

No protection

If neither TAPEVOL nor TAPEDSN is active then DFSMSrmm takes no action, regardless of the setting of the TPRACF option.

TAPEVOL

TPRACF(N)—no action.

TPRACF(P)—a TAPEVOL profile is created or deleted only as a result of issuing a DFSMSrmm ADD, CHANGE, or DELETE subcommand for a private volume from a RACF-protected pool. This includes scratch tapes that are assigned by the user or librarian by using the RMM GETVOLUME subcommand.

If you require tape volume protection for volumes that are used for nonspecific tape requests, you can either:

1. Specify the JCL PROTECT=YES option, and DFSMSdfp processing protects the volume.

   Or

2. Leave DFSMSrmm to protect the volume when a data set on the volume is closed, by creating a TAPEVOL profile.

DFSMSrmm automatically deletes any TAPEVOL profile for recycled scratch tapes when they return to scratch. If you use nonspecific mounts and scratch pools, no TAPEVOL profile exists while the volume is in scratch status.

TPRACF(A)—The same as TPRACF(P).

TPRACF(C)—DFSMSrmm processing is limited to cleaning up the existing TAPEVOL profile when volumes are deleted from a RACF-protected pool and when recycled scratch tapes return to scratch.

TAPEDSN

TPRACF(N)—no action.

TPRACF(P), TPRACF(C), and TPRACF(A)—The processing is the same for all options. DFSMSrmm does not cause any RACF profiles to be created at any time. During recycling or releasing of tapes, DFSMSrmm checks for discrete RACF data set profiles for data sets known to be on the volume, and automatically deletes them.

TAPEVOL and TAPEDSN

TPRACF(N)—no action.

TPRACF(A)—TAPEVOL profiles are created for identified, RACF- controlled, pools of non-scratch tapes when you use the RMM ADD, CHANGE and DELETE subcommands. No TVTOC is created in these circumstances.

DFSMSrmm assumes that correct DFSMSdfp and RACF processing, when a data set on a volume is opened, result in both TAPEVOL and discrete DATASET profiles being created. DFSMSrmm automatically deletes any such profiles for recycled scratch tapes when they return to scratch.

If a volume is unprotected when a data set on the volume is closed, DFSMSrmm automatically protects the volume with a TAPEVOL profile. If it is the first file of an IBM standard label tape being processed, DFSMSrmm creates a TVTOC containing an entry for the first file. This enables the installation to use RACF generic data set profiles to control access to the tape data sets, even when the JCL does not include the PROTECT=YES option.

TPRACF(P) processing is the same as TPRACF(A) except that all scratch tapes, whether defined by RMM TSO subcommand or returned to scratch by expiration processing, are protected by predefined RACF TAPEVOL profiles. The TAPEVOL profile includes an empty TVTOC so that RACF considers the volume to be scratch.

TPRACF(C)—DFSMSrmm processing is limited to cleaning up the existing TAPEVOL and discrete DATASET profile when volumes are deleted from a RACF-protected pool and when recycled scratch tapes return to scratch.

Table 1 shows DFSMSrmm processing when RACF is active and OPTION TPRACF is set for volume pools identified as DFSMSrmm and RACF-managed. The processing is dependent on the combinations of RACF TAPEVOL class and TAPEDSN option, and the TPRACF value. The DFSMSrmm EDGRMMxx parmlib VLPOOL RACF(Y) is in effect.