DATASETCONFLICT: Resolving data set naming conflicts

Explanation: DATASETCONFLICT is an optional parameter used to resolve any data set naming conflicts.

Note: DATASETCONFLICT may be specified in conjunction with the RECOVERNEWNAMEALL or RECOVERNEWNAMELEVEL parameters.

Subparameter	Explanation
RENAMESOURCE	DATASETCONFLICT(RENAMESOURCE(level) specifies that data sets from the aggregate backup output files are recovered with the new high-level qualifier specified by the level option.
RENAMETARGET	RENAMETARGET(level) specifies that existing data sets at the recovery site are renamed with the high-level qualifier specified by level, and data sets from the aggregate backup output files are recovered with their original names. An ALTER NEWNAME is performed for the existing data set name. For a detailed explanation of the ALTER NEWNAME function, refer to z/OS DFSMS Access Method Services Commands.
BYPASS	DATASETCONFLICT(BYPASS) specifies that the data sets from the aggregate backup output files are skipped and not recovered.
REPLACE	DATASETCONFLICT(REPLACE) specifies that the existing data set at the recovery site is deleted and replaced with the data set from the aggregate backup output files.

Special care should be taken when changing the high-level qualifier so that the existing data set does not become uncataloged. This may occur when no catalog alias exists for the new high-level qualifier.

Note: When using REPLACE, the data set is deleted prior to attempting the recovery of the data set from the aggregate backup output files. If the recovery fails for any reason, the data set remains deleted. Reasons for failure include, among others:

I/O errors on the input tape
Failure to allocate the new data set
Recovering at a site that does not support the type of data set being recovered.

Not all actions performed by DATASETCONFLICT subparameters are valid for all data sets. If conflicts still exist, see Performing aggregate recovery for more information on data set naming resolution.

Defaults: None.