z/OS DFSMSrmm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Data set profile processing implications

z/OS DFSMSrmm Implementation and Customization Guide
SC23-6874-00

If you only use RACF SETROPT TAPEDSN and RACF DATASET data set profiles for tape data sets, you need to consider the implications described in this topic. If you use TAPAUTHDSN=YES in DEVSUPxx to support tape data set security, you do not need to consider this information.

The objective should be to get to standard RACF tape security without using installation exits. However, the introduction of the TAPEDSN option or use of TAPEDSN only can cause some complications. When TAPEDSN is in effect and a TAPEVOL profile with no TVTOC exists, only the owner can access the data set. This happens because RACF does not use the data set profiles unless the TAPEVOL profile contains a TVTOC. When no security profile has been created by DFSMSdfp or RACF installation exits, DFSMSrmm creates a TAPEVOL profile with a TVTOC, a UACC(NONE) and the volume owner in the access list. The first file is added to the TVTOC using RACFIND=NO so that any generic data set profiles your installation has can be used with tape data sets. Once the first file entry is created RACF will maintain the TVTOC for any future tape activity on the same volume.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014