Renaming data sets during dump processing

You can specify new names for dumped data sets through the NEWNAMEUNCONDITIONAL keyword on the DUMP command. With this keyword you assign new names to data sets during dump processing, rather than renaming them later during restore processing. You might find NEWNAMEUNCONDITIONAL to be useful if your installation keeps its dumped data sets cataloged to avoid name contention between the data sets that are backed up (dumped) and the production data sets.

The NEWNAMEUNCONDITIONAL keyword can only be used when invoking DFSMSdss through the Application Programming Interface (API).

To assign a new name for a data set, you can specify a source data set with a corresponding new name. For VSAM data sets, DFSMSdss derives VSAM component names based on whether or not the name assigned for the VSAM cluster is currently cataloged in the standard order of search. If the data set is not cataloged, or the installation requests DFSMSdss to bypass checking to determine if the new cluster name is cataloged in the standard order of search by the way of the ADRUFO field, then DFSMSdss uses the same criteria that it uses for the RENAME or RENAMEUNCONDITIONAL keywords to determine the new names for the VSAM components (refer to Renaming data sets). For example, DFSMSdss might append .DATA (for a data component) and .INDEX (for an index component) to the new cluster name when deriving the new VSAM component names. If the new named data set is cataloged in the standard order of search, DFSMSdss associates the component names and the catalog name in the dump records for the new named data set.

Data sets that do not meet the NEWNAMEUNCONDITIONAL criteria retain their original names.

For the other dump records in the ADRTAPB Data Area, DFSMSdss associates the source SMS constructs and volume serial numbers from the source data set.

To use the NEWNAMEUNCONDITIONAL keyword, you do not require access authority to the source (READ) or the target (ALTER) data sets and their catalogs. Instead, renaming data sets is authorized through the existing ADMINISTRATOR keyword and is protected by the RACF® FACILITY class, STGADMIN.ADR.STGADMIN.DUMP.NEWNAME. This profile does not permit you to delete a data set. Also, DFSMSdss propagates any passwords retrieved from the source data set to the new named data set.

Note:
  1. If you specify the NEWNAMEUNCONDITIONAL keyword with the SPHERE keyword to process a base VSAM cluster, DFSMSdss processes the entire VSAM sphere and assigns a new name to associated alternate indexes and paths. If you do not specify rename filter criteria for all of the data sets in the sphere, DFSMSdss issues an error message and does not process the source data set.
  2. If the new name filter has errors, DFSMSdss does not process the data set. The new name is truncated to fit 44 characters. If it ends with a period, that period is also truncated.
  3. You cannot change the number of qualifiers unless you use fully-qualified names, for example, NEWNAMEUNCONDITIONAL((A.B.C,A.B.C.D)). If the new name is not fully qualified, it must contain the same number of qualifiers as the old name. For example, given the old name filter DATE.**, the new name filter DATE.*.*.LIST, DATE.MARCH.TODAY.OLDLIST is renamed, but DATE.MARCH.OLDLIST is not.
  4. GDG relative generation filtering cannot be used for old or new names.

For more information about dump records, refer to ADRTAPB data area.

For more information about ADRUFO installation options exit routine, refer to z/OS DFSMS Installation Exits.

For more information about specifying the NEWNAMEUNCONDITIONAL keyword, refer to NEWNAMEUNCONDITIONAL.