Rename processing with RACF

The normal order of processing when ISPF is asked to rename a data set is as follows:

The new data set name is cataloged using SVC 26
The data set is renamed using SVC 30
The old data set name is uncataloged using SVC 26

There are three occasions, however, when ISPF will deviate from this order of processing:

If the data set is a System Managed (SMS) data set, the update of the catalog (both cataloging the new name and uncataloging the old name) is handled by the operating system when the SVC 30 is issued. In this case, ISPF does not issue either of the SVC 26 requests.
If the data set is an uncataloged data set, no catalog update will be done. The data set is renamed using the SVC 30 only.
If the data set is cataloged, but the user specified both the data set name and volume, panel ISRUARP2 is displayed. The user has the option of specifying whether the catalog processing should be done. If the user indicates (via a NO in the "Reply to uncatalog the data set" field) that no catalog processing should be done, only the SVC 30 is used to rename the data set. If the reply is YES, the SVC 30 as well as both SVC 26 requests are issued.

If an error is encountered during a rename request, an attempt is made to return the data set to its original name, and to reset the catalog entries to their original status (remove the new name from the catalog and leave the old name in the catalog).

This order of processing is intended to minimize the possibility that an uncataloged data set will result if an error is encountered during the rename process. Errors may be encountered due to certain combinations of RACF® data set profiles and user access to the groups under which those data set profiles fall. When an error occurs, the user receives a message indicating the status of the data set name, and of the catalog entries.

See the z/OS Security Server RACF Security Administrator's Guide or equivalent documentation for your security package, to determine the authorization levels required for each of these operations. The user will need authorization first to catalog the new data set name, then to rename the data set, and then to uncatalog the old data set name. This will require adequate authorization to any discrete or generic data set profiles involved and to the catalogs involved. Be aware that a discrete data set profile is renamed when the data set is renamed.