DFSMSrmm automatic tape security processing assumes that when a tape is mounted for output as a scratch tape it will not be RACF protected. During the open processing for the tape data set either DFSMSdfp or your installation exits will cause some RACF profiles to be created. DFSMSrmm predefined processing also ensures that, when TAPEVOL and TAPEDSN are active, RACF predefined TAPEVOL profiles with an empty TVTOC are created for scratch volumes. To enforce a DFSMSrmm standard, that all tapes are RACF protected when the data set is closed, DFSMSrmm checks that a RACF security profile exists for the volume. If a RACF security profile does not exist, DFSMSrmm creates one and places the owner of the tape in the access list for the TAPEVOL profile with ALTER authority. The process ensures that your current tape security mechanism should continue to work as long as it is based on TAPEVOL profiles. If you do not want DFSMSrmm to create and maintain RACF TAPEVOL profiles (for example, you are using RACF TAPEDSN or DEVSUPxx TAPEAUTHDSN), specify TPRACF(NONE).