DFSMSdss volume, data set and catalog access authority

DFSMSdss checks your access authority to the volume before it performs any data set access-authorization checking. You have the required volume-level authority whenever any of the following is true:

NOPASS was specified on the PPT statement of the SCHEDxx parmlib member for the ADRDSSU or user program which calls ADRDSSU. ADRDSSU (or its caller) is coded in the PGM parameter of the EXEC statement and should be authorized.
Bypass authorization checking is requested by the DFSMSdss installation authorization exit. This exit cannot be used to bypass authorization checking initiated by utilities such as IEBCOPY that are invoked by DFSMSdss.
You have the required DASDVOL access authority for the function you are trying to perform.
You are acting as a DFSMSdss-authorized storage administrator.

For SMS-managed data sets, access authorization to create, update, or delete data sets also authorizes you to create, update, or delete entries in user catalogs. However, to add or delete any entry for an SMS-managed data set in a protected master catalog, you also need UPDATE access to the master catalog. To add or delete any non-SMS entry in any protected catalog, you need UPDATE access to the catalog.

Figure 1 shows the major decisions that are made to determine if you are authorized to perform a function against a data resource. The figure does not represent the actual program flow in DFSMSdss.

Related reading: For more information about DFSMSdss use of utilities, see Moving data sets with utilities.