NEWNAMEUNCONDITIONAL


>>-+----------------------------------------------------------+-><
   '-+-NEWNAMEUnconditional-+--+-(pfx)----------------------+-'   
     '-NEWNUNC--------------'  |    .-,-----------.         |     
                               |    V             |         |     
                               +-(----(--on,nn--)-+--)------+     
                               |         .-,-----------.    |     
                               |         V             |    |     
                               '-(pfx),----(--on,nn--)-+--)-'

NEWNAMEUNCONDITIONAL specifies a new name for a source data set during logical dump processing. This keyword provides an alternative to renaming data sets during RESTORE processing. You might also find this keyword to be useful in avoiding name contention between data sets that are backed up (dumped) and data sets that are active on your system.

NEWNAMEUNCONDITIONAL can only be used when invoking DFSMSdss through the application programming interface (API).

NEWNAMEUNCONDITIONAL specifies that a source data set should be given a new name during dump processing, regardless of whether or not a data set already exists with the same name.

pfx: Specifies the prefix to be used to replace the first-level qualifier of the data set name. It is optional. If you use it, you must specify it as the first parameter in the list of sub-keywords. You might want to use a prefix only if you do not specify the (on,nn) parameters, or if the old name filters do not match the data set name.
on: Specifies the old name to be used as a filtering criterion.
nn: Specifies the new name to be used if the data set name matches the old name filtering criterion (on).

The syntax rules for the (on,nn) parameters are the same as those for the RENAME keyword in a RESTORE operation. If the new name filter has errors, the data set is not dumped and an error message is issued. For data set naming conventions, see INCLUDE.

Note:

DFSMSdss does not verify whether the attributes of the source data set match those of the new-named data set. It is the responsibility of the program invoking DFSMSdss to perform this verification. This could cause the RESTORE operation to fail when attempting to restore to an existing data set when the attributes of the data set you are trying to restore to do not match.
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.** and the new-name filter DATE.*.*.LIST, DATE.MARCH.TODAY.OLDLIST is renamed, but DATE.MARCH.OLDLIST is not.
To change the number of qualifiers, specify fully-qualified names, for example, NEWNAMEU((A.B.C,A.B.C.D)).
If necessary, DFSMSdss truncates the new name to 44 characters. If the new name ends with a period, that period is also truncated.
You cannot use GDG relative generation filtering for old or new names.