DATASETCONFLICT parameter
The optional DATASETCONFLICT parameter of the ARECOVER command allows more flexibility for conflict resolution options. This parameter applies to INCLUDE, ALLOCATE, and ACCOMPANY data sets, with some restrictions. Like-named conflicts are evaluated based on the new name for any data sets renamed by RECOVERNEWNAMEALL or RECOVERNEWNAMELEVEL.
- If you specify RENAMESOURCE(level), the ABACKUP data set is recovered with the new high-level qualifier specified by level.
- If you specify RENAMETARGET(level), the
existing data set at the recovery site is renamed with the specified
high-level qualifier, and the ABACKUP data set is recovered with its
original name.
RENAMETARGET(level) performs an ALTER NEWNAME for the existing data set name. Special care should be taken when you change the high-level qualifier so that the existing data set does not become uncataloged, which may occur when no catalog alias exists for the new high-level qualifier.
- If you specify REPLACE, the existing data set at the ARECOVER site is deleted, and the ABACKUP data set is recovered.
- If you specify BYPASS, the ABACKUP data set is skipped and not recovered.
- BYPASS
- RENAMETARGET (if target data set restrictions are met)
- RENAMESOURCE (not supported for ACCOMPANY data sets)
If one or more verification errors occur (and are not resolved), the data sets receiving the verification errors are not recovered, but (when EXECUTE has been specified) processing continues. This causes a RESTART data set to be created. Data sets that did not receive verification errors are recovered.
Related reading
- For more information about using the DSCONFLICT parameter on ARECOVER to allow the EATTR information from the ABACKUP site to be restored, see EAV considerations for recovery functions.
- For more information about the ALTER NEWNAME function, see z/OS DFSMS Access Method Services Commands.