Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Determining RMM versus NORMM z/OS DFSMSrmm Implementation and Customization Guide SC23-6874-00 |
|
DFSMSrmm uses this procedure to determine whether to use the RMM or NORMM entity name:
Note: Even if you specify BLP, DFSMSrmm uses the VOL1 and the HDR1
label from the mounted volume as part of determining whether
to use RMM or NORMM text in the entity name.
DFSMSrmm uses STGADMIN.EDG.IGNORE.TAPE.RMM.volser only for volumes that are to be handled as RMM. . DFSMSrmm uses STGADMIN.EDG.IGNORE.TAPE.NORMM.volser only for volumes that are to be handled as NORMM. The third entity name, STGADMIN.EDG.IGNORE.TAPE.volser, is used only when the first SAF authorization check for either RMM/NORMM determines that the resource is not protected. For example, if you want DFSMSrmm to ignore volume A00001 that is defined to DFSMSrmm, you could define the STGADMIN.EDG.IGNORE.TAPE.*.* UAC(NONE) profile, which protects both STGADMIN.EDG.IGNORE.TAPE.RMM.volser and STGADMIN.EDG.IGNORE.TAPE.NORMM.volser resources. When DFSMSrmm calls SAF to check the authorization using the entity name STGADMIN.EDG.IGNORE.TAPE.RMM.A00001, it will be authorized or not based on the access list you set up for the STGADMIN.EDG.IGNORE.TAPE.*.* profile. When DFSMSrmm ignores a volume as requested by the EDG_EXIT100 installation exit and the user is authorized to ignore processing, this overrides any decision taken by RACF as a result of authorization checks issued by OPEN processing. You can tailor the EDGUX100 exit module to prevent DFSMSrmm from overriding the decision in the case of SAF return code 8 (not authorized). |
Copyright IBM Corporation 1990, 2014
|