ARC6402I
CONCURRENT COPY INITIALIZATION IS COMPLETE FOR AGGREGATE agname. ANY SERIALIZATION HAS BEEN RELEASED. JOB = jobname.

Explanation

The initialization of the concurrent copy session completed. Therefore, serialization of the data being dumped with concurrent copy is no longer necessary and it was released. The data is now available for update activity without affecting the dump operation already in progress.
  • agname is the name of the aggregate group processing.
  • jobname is the name of the job submitted by the ABACKUP command if issued by a batch job, a batch TMP, or a TSO terminal.
    Note: If the ABACKUP command was issued from the console, then jobname is CONSOLE.

System action

Aggregate backup processing continues. Issued By: ABARS secondary address space.

Operator response

Serialization was released for all data sets processed by the concurrent copy function in ABARS aggregate backup. This message can be used by the console operator to submit a follow-on job, initiate a data base application, or request another backup. This message can also be used as input for console automation products to invoke similar activities.

Programmer response

This message informs you the level 0 DASD data sets dumped with concurrent copy, are now available for update activity. See the DFSMSdss message ADR734I for the number of data sets successfully established into the concurrent copy session, and the total number of data sets selected for concurrent copy. If the number of concurrent copy data sets is less than the number of selected data sets, one or more ADR735W messages are issued indicating what data sets were not successfully established into the concurrent copy session and why.

Source

DFSMShsm

Parent topic: ARC messages