ARC6296I
CONFLICT RESOLUTION ACTION action FROM THE {CONFLICT RESOLUTION DATA SET | DATASETCONFLICT PARAMETER | INSTALLATION-WIDE EXIT ARCCREXT} {IS INVALID | DID NOT RESOLVE THE CONFLICT | IS NOT AUTHORIZED} FOR DATA SET data-set-name FROM listtype LIST DURING AGGREGATE RECOVERY

Explanation

A like-named conflict has been found during ARECOVER processing. The requested action has been either invalid, not RACF-authorized, or did not resolve the like-named conflict for the data set.
  • action indicates the requested conflict resolution action for the data set.
  • CONFLICT RESOLUTION DATA SET indicates that the action is from the conflict resolution data set.
  • DATASETCONFLICT PARAMETER indicates that the action is from the DATASETCONFLICT parameter.
  • INSTALLATION-WIDE EXIT ARCCREXT indicates that the action is from the installation-wide exit ARCCREXT.
  • IS INVALID indicates that the action is invalid for the data set.
  • IS NOT AUTHORIZED indicates that the action is not RACF-authorized.
  • DID NOT RESOLVE THE CONFLICT indicates that the action did not resolve the like-named conflict for the data set.
  • data-set-name indicates the data set name in conflict.
  • listtype indicates the data set came from the INCLUDE, ACCOMPANY, or ALLOCATE list.
If IS INVALID is indicated, the action is invalid because:
  • If the action is RENAMESOURCE:
    • RENAMESOURCE is not supported for migrated VSAM data sets, or for ACCOMPANY (tape) data sets.
  • If the action is RENAMETARGET:
    • RENAMETARGET is not supported for existing catalogs, generation data group (GDG) or generation data set (GDS) data sets, or tape data sets, and is only supported for the following catalog entry types:
      • non-VSAM DASD
      • VSAM cluster (not a catalog)
      • VSAM alternate index (AIX®)
      • Data or index component, or path, related to a VSAM cluster (not a catalog) or AIX
  • If the action is REPLACE:
    • REPLACE is not supported for ALLOCATE or ACCOMPANY data sets, or existing catalogs, and is only supported for the following catalog entry types:
      • Non-VSAM.
      • VSAM cluster (not a catalog).
      • VSAM AIX.
      • If a conflict is detected for a data component, index component, or path related to a VSAM cluster (not a catalog) or a VSAM AIX, the entire related VSAM base cluster is replaced.
    If IS NOT AUTHORIZED is indicated, the user did not have RACF® facility class authorization to the STGADMIN.ARC.ARECOVER command profile. RACF authority to resolve the conflict has been denied for one of the following reasons:
    • If the action is REPLACE:
      • The user does not have RACF FACILITY class authorization to the: 
        STGADMIN.ARC.ARECOVER.agname.REPLACE
        command profile.
      • The user has the proper FACILITY class authorization, but does not have RACF ALTER access authority to the indicated data set.
    • If the action is RENAMETARGET:
      • The user does not have RACF FACILITY class authorization to the: 
        STGADMIN.ARC.ARECOVER.agname.RENTGT
        command profile.
      • The user has the proper FACILITY class authorization, but does not have RACF ALTER access authority to the indicated data set.
    If DID NOT RESOLVE THE CONFLICT is indicated, the following are possible reasons why the action did not resolve the like-named conflict:
    • If the action is RENAMESOURCE:
      • The new name of the data set already exists at the ARECOVER site.
      • If the data set is VSAM, all components of the source data set must be renamed and checked for existing duplicates. Either the cluster or components are not renamed because of existing duplicates.
      • If the data set is a GDS, both the GDS and the GDG base must be renamed and checked for existing duplicates. Either the GDS or the GDG base are not renamed because of existing duplicates.
      • If the data set is an integrated catalog facility (ICF) user catalog, another ICF user catalog to be recovered may include an alias that would cause the catalog to fail the DEFINE. ICF user catalogs cannot have their alias defined in another ICF user catalog.
    • If the action is RENAMETARGET:
      • The new name of the data set already exists at the ARECOVER site.
      • If the data set is VSAM, all components of the target data set must be renamed and checked for existing duplicates. Either the cluster or components are not renamed because of existing duplicates.
      • Another data set being recovered is already being renamed to the new target data set name selected for the data set.
    • If the action is REPLACE:
      • ARECOVER has detected this multivolume data set which is cataloged at the ARECOVER site. ARECOVER is unable to resolve the conflict because one or more of the indicated volumes are offline and an F1DSCB has been detected on at least one of the online volumes.

System action

DFSMShsm processing continues.

Programmer response

Change the requested conflict resolution action, or provide the required RACF authority. The order of priority for conflict resolution is:
  • If a conflict resolution data set exists and there is an entry for the data set in conflict, the requested action is taken. The action may be changed (prior to issuing the ARECOVER command) from BYPASS to the desired action, or the entry in the conflict resolution data set may be deleted.
  • If the DATASETCONFLICT parameter has been specified on the ARECOVER command, and the conflict is not resolved, the action indicated by the subparameter is taken if it is valid. If required, change the subparameter to the desired action.
  • If the conflict is not resolved, and the installation-wide exit ARCCREXT is active, the exit is called to resolve the conflict. In this case, the exit must be changed to specify the desired action.

Once the conflict resolution action is requested, or the conflict is resolved through external means, reissue the ARECOVER command to recover the remaining data sets.

Source

DFSMShsm

Parent topic: ARC messages