For DFSMSrmm to maintain the access list when TPRACF(A) or TPRACF(P) is in use, use the RMM TSO subcommands to change access lists, rather than RACF. You can use RACF commands to add users and owners if the times when DFSMSrmm updates, deletes, or creates the TAPEVOL profiles are well defined, and during the time a volume is not scratch. The RACF profile is updated only if the DFSMSrmm volume access list is updated.

If you use TPRACF(A) or TPRACF(P), DFSMSrmm ensures that your tapes are protected by RACF. DFSMSrmm ensures that all non-scratch tapes are protected by a discrete RACF TAPEVOL profile. DFSMSrmm checks that a RACF profile exists whenever a data set is written on a tape. If a profile does not exist, DFSMSrmm creates one. Therefore you do not need to use RACF installation exits to set the JCL PROTECT=YES option or specify PROTECT=YES in your JCL. Additionally, because DFSMSrmm creates a TVTOC when the RACF TAPEDSN option is used, you can use generic data set profiles for all tape data sets without changes to JCL or installation procedures.

Be careful about using RACF profiles to maintain a list of users who own and can access volumes. When you use the RMM ADDVOLUME and CHANGEVOLUME subcommands, you can maintain up to 12 users and owners for each volume. If the volume is in a RACF-controlled pool and RACF TAPEVOL class is active, the TAPEVOL profile access list is maintained with the list of users who can access the volume and the owner's user ID. If you change the RACF TAPEVOL profile access list using RACF commands, the DFSMSrmm control data set does not reflect the changes. The next time that DFSMSrmm updates the RACF TAPEVOL profile, it creates the access list from the volume information, but does not include any users or owners you added using RACF commands.