ANTA5107E
XADDPAIR FAILED FOR VOLUME PAIR(primary_volser,secondary_volser) FOR SESSION(session_id), RC=return_code REAS=reason_code

Explanation

The XADDPAIR command for the volume pair indicated by primary_volser in session session_id failed with return code return_code and reason code reason_code. If secondary_volser is XRCUTL, this was an attempt to add a utility volume. Otherwise, it was an attempt to add a data volume pair.

System action

If this was an attempt to add a new data volume pair to the session, the volume pair has not been added. If this was an attempt to re-add an existing data volume pair to the session, the volume pair remained in the state it was in prior to the XADDPAIR attempt. XRC activity continues on other volume pairs in the session.

If this was an attempt to add a new utility volume to the session, the volume has not been added. If this was an attempt to re-add an existing utility volume to the session, the state of the volume and its associated storage control sessions might vary, so further investigation is required, as described in the "System programmer response" below.

System programmer response

See SDM and XRC return codes for an explanation of the return and reason codes. Also look for any preceding error messages that might provide additional diagnostic information.

For failures involving data volume pairs, or Utility volumes for Standard Single Readers, correct the error and reissue the XADDPAIR command.

For failures involving utility volumes for Enhanced Multiple Readers: Prior to re-issuing the XADDPAIR command, use the XQUERY command with the STO DETAIL keywords to determine the state of the storage control sessions in the Enhanced Reader group. If some of the sessions in the group are active, use the F ANTAS000,SUSSESS command to suspend these active sessions, and then reissue the XADDPAIR command. In addition, if an attempt to change auxiliary session configuration failed, also use the F ANTAS000,LISTSESS ALL command to determine whether extraneous storage control sessions need to be cleaned up.

If errors persist after these actions, search the problem reporting databases for a solution. If no solution exists, contact the IBM® Support Center for additional problem determination assistance.

Source

Extended remote copy (XRC).