Table of SDM return codes

00000004

Abnormal termination of the address space.

00000008

Abnormal termination of concurrent copy task or service request block (SRB) in the address space running DFSMSdss.

Possible reasons for this condition are:

• There is an installation exit (such as IEFUSI) that is limiting the size of the address space's extended private area below the minimum required.
• There is an excessively large common storage configuration, including the extended common service area (ECSA) and the extended system queue area (ESQA) that is limiting the size of the address space's extended private area below the minimum required.
• An excessively large TOTALBUFFERS amount was specified in the XRC parameters. A typical XRC installation can support a maximum of 25000.
• The System Data Mover required a large number of additional temporary buffers to process non-timestamped writes or unusually skewed workload.

See z/OS DFSMS Advanced Copy Services for the requirements for a description of the virtual storage requirements of an XRC System Data Mover address space. If the system configuration changes are needed, issue an XSUSPEND command with the TIMEOUT parameter to terminate the data mover address space. After the changes are made, restart the session and resynchronize the volume pairs.

Error occurred while you are attempting to vary volume offline. The reason code associated with this return code is generated by IEEVARYD.

This return code can result when the XQUERY command is issued with session_id ALL if an active session is in the process of suspension or ending. Wait until the session has completed suspension processing or has ended before reentering the XQUERY command. If the session does not end, you might need to issue a CANCEL ANTASnnn command to force the address space to end.

For an XADDPAIR or XDELPAIR command, ensure that the volume has been specified properly. For an initial XADDPAIR or an XADDPAIR of a utility volume, ensure that the volume is online to the data mover system. After correcting the problem, reissue the XADDPAIR or XDELPAIR command.

For an XRECOVER or XADVANCE command, ensure that the volume is online to the data mover system. After correcting the problem, reissue the command.

For an XSTART command (when restarting a session), ensure that the volume is in the data mover system configuration. The storage control report associated with the restarted XRC session indicates that the storage control session is in a quiesced or suspended state. Ensure that all volumes for the storage control are in the configuration, then issue an XADDPAIR command to add this volume and other volumes in the quiesced or suspended storage control into the XRC session. If you are unable to put the volume in the data mover system configuration, you must issue a MODIFY ANTAS000,TERMSESS command for the storage control session(s) to free up resources associated with this volume and other volumes on the storage control from an LPAR which has connectivity to that device. If you do this, ALL VOLUMES on the storage control will then require a full initialization.

If you want to restore the session but do not want to resynchronize the volume pairs at this time, you can vary the volumes online, and then issue an XSUSPEND command to suspend the session followed by an XSTART command the restart the session.

If the return code appears with message ANTR5102E, verify that the volume to be recovered is online to the recovery system before issuing the XRECOVER or XADVANCE command.

When associated with the REFRESHS command error message ANTX8142E, this indicates that the secondary volser is not online to the SDM system. REFRESHS requires an online secondary volume to determine the location of the relocated volume.

• XADDPAIR command – The device characteristics of the primary volume do not match those of the secondary. The secondary volume must have the same number of tracks per cylinder and bytes per track as the primary volume. The secondary volume must also have a capacity (number of cylinders) greater than or equal to that of the primary.
• XRECOVER command – When recovering from tertiary volumes (copies of the secondary volumes), this return code will be issued if the ONLINE keyword is not used with the command. The return code can also be issued when recovering either secondary or tertiary volumes, if the device characteristics of the volume recovered do not match those recorded in the XRC state dataset for the corresponding secondary volume.
• XDELPAIR command – Current device characteristics of the indicated volume do not match the characteristics the volume had when it was added to the session. This condition might have resulted from migration of the volume from one location to another (within the same storage control or to a different storage control), or from conversion to a different device geometry; for example, from 3380 to 3390. The XDELPAIR command completes successfully, but message ANTX5011E with this return code is issued to indicate this condition.
• XSET command with REFRESHS keyword - The device characteristics of the newly detected secondary volume are incompatible with the prior secondary volume. Either the capacity (number of cylinders) of the newly detected secondary volume is less than the prior secondary volume, or the number of tracks per cylinder does not match.

See &ieag100t; for information on the DEVSERV command, which can be used with the QDASD and PATHS keywords to determine device characteristics and location.

See z/OS DFSMS Advanced Copy Services for information on allowable XRC device configurations.

For an XADDPAIR or XDELPAIR command, ensure that the volume has been specified properly and that the volume is online to the data mover system. After correcting the problem, reissue the XADDPAIR or XDELPAIR command.

For an XRECOVER command, ensure that the volume is online to the data mover system. After correcting the problem, reissue the command.

For an XSTART command, ensure that the volume is online to the data mover system. The storage control report associated with the restarted session indicates that the storage control session is in a quiesced state. Ensure that all volumes for the storage control are placed online, then issue an XADDPAIR command to add this volume and other volumes in the quiesced storage control into the session. If you want the session to be restored but do not want to resynchronize the volumes at this time, you can issue an XSUSPEND command to suspend the session followed by an XSTART command to restart the session. The session will then monitor record updates. If you are unable to place the volume online to the data mover system, you must issue an MODIFY ANTAS000,TERMSESS command for the storage control session to free up resources associated with this volume and other volumes on the storage control. All volumes on the storage control will then require a full initialization.

If the return code appears with message ANTR5102E, verify that the volume to be recovered is online to the recovery system before issuing the XRECOVER command

• The session ID specified is invalid. In this case, reissue the command with the correct session name.
• A high-level-qualifier specified on the XSTART or XRECOVER command is invalid. In this case, reissue the command with the correct high level qualifier name.
• One or more of the data sets are not allocated or are not cataloged on the data mover or recovery system. In this case, ensure that all of these data sets are allocated and cataloged to both the data mover and recovery system. Reissue the failing command.

When contacting IBM for assistance, provide a list of the XRC state, control, and journal data set names that are cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section.

When contacting IBM for assistance, provide a list of the SYS1.XCOPY or hlq.XCOPY data sets that are cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section.

The reason code associated with this return code is generated by the DYNALLOC facility. See the reason codes from the DYNALLOC topic of z/OS MVS Programming: Authorized Assembler Services Reference ALE-DYN for reason code information.

When contacting IBM for assistance, provide a list and allocation attributes of the hlq.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section.

The reason code associated with this return code is generated by the DYNALLOC facility. Reason codes of one to 16 indicate which journal data set the allocation is failing on. For reason codes outside of this range, see the DYNALLOC topic of z/OS MVS Programming: Authorized Assembler Services Reference ALE-DYN for reason code information.

When contacting IBM for assistance provide a list and allocation attributes of the hlq.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section.

The reason code associated with this return code is generated by the DYNALLOC facility. See the reason codes from the DYNALLOC topic of z/OS MVS Programming: Authorized Assembler Services Reference ALE-DYN for reason code information.

When you contact IBM for assistance, provide a list and allocation attributes of the hlq.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section.

When contacting IBM for assistance, provide a list and allocation attributes of the SYS1.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section. You can issue a DEVSERV QDASD command to dump the UCB.

When contacting IBM for assistance, provide a list and allocation attributes of the SYS1.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section.

When contacting IBM for assistance, provide a list and allocation attributes of the SYS1.XCOPY data sets cataloged on both the data mover and recovery systems, in addition to the data requested in the beginning of this section. This problem also requires a GTF trace to determine where the problem occurred during a close.

If the problem persists, issue MODIFY ANTASnnn,DUMP to collect diagnostic information.

• A specified secondary volume is already defined in a session as a primary volume.
• A specified secondary volume is already defined in a session as another secondary volume.
• A specified primary volume is already defined in a session as a secondary volume.

Issue an XQUERY command to determine what volumes are currently defined to the session. To change the status of a volume already in the session, issue an XDELPAIR command to remove the volume pair from the session, then reissue the XADDPAIR command to add the correct volumes. If an incorrect volume pair was specified with an XADDPAIR command, correct the error and reissue the command.

This condition can also occur when updates to the secondary volumes have fallen so far behind the primary system updates that the journals have been filled with unapplied data. In this case, the configuration of the XRC system can be such that the data mover cannot keep up with the primary updates. You might need to reconfigure the system or place fewer volumes under XRC control. You can suspend, reconfigure, and then restart the session.

When contacting IBM for assistance, provide a dump of the journal, state, and control data sets, in addition to the data requested in the beginning of this section.

When contacting IBM for assistance, provide a report on the cataloged data sets on both the data mover system and the recovery system, in addition to the data requested in the beginning of this section.

• No updates were made to any of the primary volumes while the session was active. Data on all secondary volumes is consistent as of the timestamp reported when the session was suspended or ended. There are no updates that need to be applied to the secondary volumes because the control data set was not initialized. If the XRECOVER command was invoked, you must clip the secondary volumes to match the primary volume serial numbers.
• No volumes have ever been added to the session. The XRECOVER or XADVANCE has no work to do and the function is complete.
• The CONTROL0 or CONTROL1 member cannot be found in the control data set. Possibly the wrong data set is cataloged on the recovery system. Ensure that the correct data set is cataloged, and then reissue the XRECOVER or XADVANCE command.

If the members do not exist and the system log indicates that an XRC session was properly started with active updates on the volumes, then contact IBM for assistance. Provide a report on the cataloged data sets on both the data mover system and the recovery system, in addition to the data requested in the beginning of this section.

If the TERTIARY parameter was specified on the XRECOVER command, message ANTR5028E might have been previously issued, indicating that an attempt was made to recover to a secondary volume that is the same device as the secondary in effect when XRC suspended or ended.

If XRC abnormally ends during an XRECOVER command, some secondary volume serial numbers can have already been updated. In this case, the XRECOVER command cannot be reissued. Relabel the secondary volumes back to their original volume serial numbers before reissuing the XRECOVER command.

If this error is associated with an XADDPAIR command for a suspended pair, use the XQUERY configuration report to determine the secondary volume that was specified when the pair was originally added to the session, then reissue the command.

When contacting IBM for assistance, provide a copy of the associated SYS1.LOGREC information and a GTF trace, in addition to the data requested in the beginning of this section.

If this error has been received with a valid active session, issue MODIFY ANTASnnn,DUMP to obtain a dump of the failing session. A dump is required in addition to the data requested in the beginning of this section.

If this error has been received with a valid active storage control session, issue MODIFY ANTASnnn,DUMP to obtain a dump of the failing condition. Issue MODIFY ANTASnnn,LISTSESS to obtain the storage control information on active sessions and MODIFY ANTASnnn,LISTDVCS to obtain the storage control information for active devices. This information is required in addition to the data requested in the beginning of this section.

If the problem persists, issue the F ANTASnnn,DUMP command to collect diagnostic information.

This error occurs if XRC encounters an error when it is writing to either the control or state data set. In most cases, the error occurs because the data set did not have sufficient space to contain XRC information. See z/OS DFSMS Advanced Copy Services to determine the proper allocation sizes for the XRC control and state data sets.

When you contact IBM for assistance, provide a copy of the failing data set, in addition to the data requested at the beginning of this section.

If the active command does not complete in a reasonable timeframe, you can issue MODIFY ANTASnnn,DUMP to capture the proper information for problem diagnosis. You might need to issue CANCEL ANTASnnn to force the address space to end.

• The specified volume can already be owned by an active XRC session.
• An I/O error has occurred while attempting to add the specified volume to the session.

  For either of the above reasons, issue MODIFY ANTAS000,LISTDVCS to the volume to determine which storage control session number owns the volume to be added. If you do not want the session to be active for the volume, you can force the storage control session to free the volume for use by issuing MODIFY ANTAS000,TERMDVC to the session.

• The storage control cache or NVS is unavailable on the primary (source) storage controls. Issue the DEVSERV system command to display the current status of cache and NVS for the subsystem and the primary volume. If the error continues after you have verified that the storage control cache and NVS are available, the storage control can have encountered an uncorrectable error. You might need to re-IML the storage control to correct the problem.

If the message issued with this return code was accompanied by an ANTX5000E, ANTX5001E, or ANTX5002E message, see those messages for further information. When contacting IBM for assistance with a problem, provide any associated SYS1.LOGREC information, in addition to the data requested in the beginning of this section. A GTF trace of the operations leading to the error can also be required.

When contacting IBM for assistance, also provide a copy of the SYS1.LOGREC data set, in addition to the data requested in the beginning of this section.

When contacting IBM for assistance, a GTF trace of the operations leading to the error can also be required in addition to the data requested in the beginning of this section.

When contacting IBM for assistance, a GTF trace of the operations leading to the error can also be required in addition to the data requested in the beginning of this section.

When contacting IBM for assistance, a GTF trace of the operations leading to the error can also be required in addition to the data requested in the beginning of this section.

When contacting IBM for assistance, a GTF trace of the operations leading to the error can also be required in addition to the data requested in the beginning of this section.

• A TERMSESS command being issued to the storage control session
• The timeout expiring on the storage control session
• Cache or NVS being turned off for a storage subsystem
• A storage control error
• A software error.

Review other diagnostic messages to determine the cause of the problem. All volumes for the storage control are suspended as a result of this error. Based on the ERRORLEVEL specification, other volumes on other storage controls can also be suspended. After determining the reason for the error and correcting the condition, you can issue an XADDPAIR command to add the suspended volumes back to the session. The suspended volumes will require a full resynchronization.

XRC has detected this error during normal data mover processing. The scope of the error is for a single storage control session. After you determine the reason for the error and correct the condition, you can issue an XADDPAIR command to add the suspended volumes back to the session.

A reason code accompanies this return code, which gives more specific information as to the reason for the suspension. Additionally, other diagnostic messages might be issued.

The system data mover has attempted to issue I/O to a device, but the I/O was not completed in the allotted time. If the accompanying reason code is 82, the timeout occurred after the I/O had been started. If the accompanying reason code is 83, the error occurred while the I/O was waiting to start.

When reading updates from cache, or writing updates to a secondary volume, this return code is issued only when the data mover determines not to retry the condition.

Retry will not be attempted if there is a command in progress (XDELPAIR, XSUSPEND, XEND), or if at least one storage control session is exceeding cache SIDEFILE limits.

If the timeout occurs while writing updates to a secondary volume, the number of retry attempts is limited to four. If the timeout occurred while reading updates from cache in a channel extended primary storage control, check the network for connectivity problems. For other timeout events, check the storage subsystems for evidence of recovery actions that can have delayed I/O completion. The z/OS® DEVSERV command can be helpful with problem determination.

When the underlying problem is corrected, issue an XADDPAIR command for all of the suspended volumes.

This error can occur for an ESS storage subsystem if the volume channel connection address is greater than 255, which is the maximum supported. In this case, ensure that the address is between 0 and 255. For a non-ESS storage subsystem, the channel connection address cannot be greater than 127. In this case, ensure that the address is between 0 and 127. If the volume serial number was specified correctly, issue a DEVSERV QDASD command for the failing volume and obtain the UCB information for the volume. Use the MODIFY command to dump the ANTASnnn address space, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. You might need to cancel ANTASnnn and restart the XRC session. The cancel will cleanup the XRC control structures and suspend all volume pairs.

• A TERMSESS command being issued to the storage control session
• The timeout expiration on a non-ESS storage subsystem session
• A storage control error
• An error in cache or NVS
• A software error.

Review other diagnostic messages to determine the cause of the problem. The data mover suspends all volumes for the storage control as a result of this error. Based on the ERRORLEVEL specification, other volumes on other storage controls can also be suspended. After determining the reason for the error, you can issue an XADDPAIR command to add the suspended volumes back to the session. The suspended volumes will require a full resynchronization.

When contacting IBM for assistance, provide a GTF trace, from both the application system and the data mover system, of I/O to the primary volume with the lost record, in addition to the data requested in the beginning of this section.

When contacting IBM for assistance, provide associated SYS1.LOGREC information in addition to the data requested in the beginning of this section.

IEF196I IEF352I ADDRESS SPACE UNAVAILABLE
IEF352I ADDRESS SPACE UNAVAILABLE

If the above messages do not appear within two minutes, issue CANCEL ANTASnnn to end the particular address space. It can be necessary to also end the ANTAS000 address space to completely end the XRC session.

An error has been detected while attempting to store a member in the hlq.XCOPY.session_id.STATE or the hlq.XCOPY.session_id.CONTROL data set with the STOW function. Determine why the STOW function failed and correct the error. In most cases, the error occurs because the data set did not have sufficient space to contain XRC information. See z/OS DFSMS Advanced Copy Services to determine the proper allocation sizes for the XRC control and state data sets.

If this error causes suspension of a session or volumes in the session, the volumes that encountered this error requires complete synchronization after you have corrected the problem. You might also need to issue the appropriate XCOUPLE command if the session was a coupled XRC session.

1. Allocate a new control or state data set.
2. Suspend the session with an XSUSPEND command.
3. Copy the existing control or state data set to the new data set.
4. Delete the existing control or state data set.
5. Rename the new control or state data set to the original control or state data set name.
6. Restart the XRC session by issuing an XSTART command.
7. Resynchronize the suspended volumes by issuing an XADDPAIR command for all of the volumes in the session.

When you contact IBM for assistance, provide a copy of the failing control or state data set in addition to the data requested in the beginning of this section.

If this return code is observed after an XSTART to restart an XRC session on a different LPAR, take the following steps to resolve the issue.

First issue F ANTAS000,LISTSESS ALL and verify that the session in error is an XRC session and that it should not belong to another XRC session.

If it should belong to another XRC session, issue an XDELPAIR, and then XADDPAIR the volume into the appropriate session.

If it should belong to this XRC session, a SUSSESS will be required to suspend the active storage control session and allow the session to be re-registered to the appropriate XRC session.

1. Cancel the session's ANTAS00n address space, if still running
2. Create and initialize a new control data set
3. Uncouple the session with XCOUPLE PURGE
4. Restart and recouple the session

• An XDELPAIR command has been issued for the specified volume which is currently a FIXED utility device. When enhanced multi reader is not being used, you must either switch to another FIXED utility device (via an XADDPAIR command) or issue the XSET UTILITY command with the FLOAT option before issuing the XDELPAIR command for the specified volume.
• When enhanced multi reader is being used via PARMLIB setting AllowEnhancedReader(YES), FIXED utility devices for the primary storage control session cannot be deleted until all other volumes in that storage control session are deleted, including all non-utility volumes and all utility volumes for the associated alias storage control sessions.
• An XADDPAIR command was issued for the specified volume which is currently a FIXED utility device, and the secondary volser specified on the XADDPAIR command is not XRCUTL. You must either switch to another FIXED utility device (via an XADDPAIR command) or issue the XSET UTILITY command with the FLOAT option before attempting to shadow the specified volume.

Reason Code

Description

0

The XDELPAIR request specified a LOGPLUS utility volume. A LOGPLUS utility volume can only be deleted by issuing the XDELPAIR request for the LOGPLUS volume associated with the LOGPLUS utility volume.

1

The XADDPAIR request was specified with the LOGPLUS option, and only a utility volume was requested to be added to a session. A LOGPLUS utility volume must be added with the LOGPLUS volume pair.

2

The XADDPAIR request was specified with the LOGPLUS option, and the LOGPLUS utility volume pair was specified before the LOGPLUS volume pair. The LOGPLUS volume pair must be specified as the first volume pair, and the LOGPLUS utility volume pair must be specified as the second volume pair.

3

The XADDPAIR request was specified with the LOGPLUS option, and the second volume pair specified on the request was not a utility volume pair.

4

The XADDPAIR request was specified with the LOGPLUS option, and either the primary volume or the utility volume specified is not online.

5

The XADDPAIR request was specified with the LOGPLUS option, and the primary volume and utility volume specified do not reside on the same storage control (LSS).

To recover from this error, the Utility volume must be removed using XDELPAIR, then re-added. if the Utility volume is associated with an Enhanced Reader primary or Single Reader storage control session, all associated volume pairs must first be removed using XDELPAIR, then re-added after the Utility volume is re-established.

If none of the above actions fixes the problem, you will need to reallocate the master data set. See the z/OS DFSMS Advanced Copy Services information, "Specifying the Master Data Set," for the attributes needed in reallocating the master data set.

F ANTAS000,CREFRESH FORCE

This return code can also refer to the cluster data set.

This return code can also refer to the cluster data set.

This return code can also refer to the cluster data set.

This return code can also refer to the cluster data set.

This return code can also refer to the cluster data set.

This return code can also refer to the cluster data set.

This return code can also refer to the cluster data set.

This return code can also refer to the cluster data set.

This return code can also refer to the cluster data set.

Issue the XQUERY master_session_name MASTER command to determine the status of each session that is associated with the master session. The coupled session status of UNK that is indicated on the XQUERY message of ANTQ8304I indicates that the master session could not communicate with the local session. Issue the XQUERY localsessionid command (at the local session system) to determine if the local session (with the UNK status) is active. If a local session is not active, see "Restarting an inactive XRC coupled session" in z/OS DFSMS Advanced Copy Services for instructions on how to restart an inactive session. If the local session is active, issue the F ANTASnnn, DUMP console command (at the local session system) to collect diagnostic information, and then contact IBM for assistance in determining the cause of the problem. You can then issue the CANCEL ANTASnnn console command, and restart the inactive session (with the instructions referred to previously in this paragraph).

This return code can also refer to the cluster data set.

1. The master data set has never been initialized. This can occur when no session has been coupled to the master session with an XCOUPLE ADD command. The command is not valid at this time; no action is necessary.
2. The master data set does not contain information for the master session name specified. This can occur when the master data set has been renamed and does not match the original master session name. Correct the master data set name and reissue the command.
3. Access to the master data set has been lost because of connectivity problems, or because the data set has been renamed or re-cataloged. Restore access to the master data set and reissue the command.

During processing of the indicated command, the attempt to enqueue the qname of SYSXRCLS and the rname of the logical session name failed. The logical session can be active on another system. Each logical session must have a unique name, and can only be active on one system at a time within the same global resource serialization ring. If you are running CXRC, issue the XQUERY MASTER command for each master session that is active in your complex to determine status of the logical session name.

Note: SDM can issue the XCOUPLE DELETE command during XCOUPLE ADD processing if a failure is detected attempting to add a session back into a master session.

If the previous error that occurred was due to an error for the cluster session to which the XRC session was coupled, and it has been determined that restarting mirroring using XRC is the correct recovery technique, after re-starting the cluster session, issue the XCOUPLE command with the ADD parameter to re-add each session that was previously in the cluster session (after the cluster session is re-started, issue the XSTATUS CLUSTER command to determine the sessions that were previously coupled via the cluster session). You can then issue the XCOUPLE command with the RELEASE parameter to release the master session from the HOLD status, and then re-add the volumes to the sessions .

• If the query shows a pending command: Before reissuing the XCOUPLE ADD command, you must either wait for the master session command to complete for all the sessions, or you can cancel the command by reissuing it with the CANCEL option. If one of the sessions encounters an error while it is executing the master command, follow the documented instructions for that return code before you attempt to issue the XCOUPLE ADD command again.
• If the query does not show a pending command:
  1. Cancel the data mover address space.
  2. Issue an XCOUPLE PURGE command to uncouple the session.
  3. Restart the data mover by using XSTART, and issue the XCOUPLE ADD command again.

1. No interlocked session that is associated with the master session can have a session status of END, SUS, or UNK.
2. The master session must not be in HOLD status.

To interlock a session, you might need to issue the XCOUPLE DELETE or XCOUPLE PURGE command to first remove a coupled session from the master session, and then issue the XCOUPLE ADD command to recouple the session. If the master session is in HOLD status, issue the XCOUPLE RELEASE command to remove this HOLD status.

1. If coupled XRC sessions are being recovered using the XRECOVER command, all sessions must complete the XRECOVER process.
2. If a coupled session in the associated master session is active, but you do not want to recover the session or cannot recover the session, issue the XCOUPLE DELETE command to remove the coupled session from the master session.
3. If a coupled session in the associated master session is inactive, you can wish to issue the XCOUPLE PURGE command to remove the session as a coupled session from the master session.

Once the appropriate actions have been taken to ensure that the coupled sessions associated with the master session can be recovered to a consistent time, issue the XCOUPLE RELEASE command to remove the HOLD status of the master session. IBM recommends that you make backup copies of secondary volumes and journals for all coupled sessions before you use this command.

An active XRC session or Cluster is already using the Cluster Identifier for this LPAR.

The Master Control Data Set cannot be located or has unusable attributes.

The Cluster Control Data Set cannot be located or has unusable attributes. This error can appear if the Cluster Control data set is allocated with extended attribute data set control blocks (format 8 and 9 DSCBs).

Unable to acquire common storage for Cluster Manager.

Commands using a Cluster Identifier as session_id are not allowed.

Cannot explicitly couple an individual XRC session to a Cluster.

An XRC couple function required the use of the cluster session, but the cluster session was found to be inactive. Ensure that the ClusterMSession and ClusterName parameters of the XRC parmlib member are specified correctly, and issue the MVS MODIFY operation of CREFRESH to start the cluster session. If XRC sessions were coupled through the cluster session, after the cluster session is restarted, issue the XCOUPLE command with the ADD parameter to re-add each session that was previously in the cluster session (after the cluster session is restarted, issue the XSTATUS CLUSTER command to determine the sessions that were previously coupled via the cluster session). You can then issue the XCOUPLE command with the RELEASE parameter to release the master session from the HOLD status, and then re-add the volumes to the sessions.

Clustering is disabled on this system.

Cluster Monitor Data Set cannot be located or has unusable attributes.

Cannot couple to a master session other than the one associated with this system's Cluster.

Maximum number of coupled session per cluster exceeded.

An I/O error occurred attempting to access the Cluster Control Data Set.

One or more sessions are coupled to the master session to be associated with the cluster.

One or more coupled sessions are currently active on the LPAR.

One or more sessions are currently coupled through the cluster.

A problem occurred while attempting to terminate clustering.

Internal error.

• Reset the ClusterMSession parameter in the ANTXIN00 parmlib membername back to the master name found in the cluster data set.
• Issue the MVS console command 'F ANTAS000,CREFRESH' to restart the cluster session.
• Issue the XRC command XSTATUS CLUSTER to determine the names of the XRC sessions coupled through the cluster session.
• Uncouple each of the XRC sessions by issuing the XRC command XCOUPLE with the appropriate parameter of DELETE or PURGE . Do the uncoupling according to whether the XRC session is active or inactive respectively.

An attempt to XCOUPLE ADD a session to a cluster failed because of excessive time spent waiting to obtain serialization.

Check SYSLOG for XRC error messages related to coupling or clustering. Check for abnormal termination of either the Cluster or data mover address spaces (ANTASnnn or ANTCLnnn). Correct error conditions and restart Cluster if necessary.

For reason codes 1 and 3, dump the Cluster address space (ANTCLnnn) for subsequent problem determination. Remove any remaining sessions from the Cluster with XCOUPLE DELETE. Disable the cluster and restart it. If the Cluster address space is not responsive, cancel and restart it. For reason code 2, determine which data mover address space (ANTASnnnn) is associated with the XCOUPLE ADD that did not complete. Dump the address space for subsequent problem determination, and then cancel it. The data mover might then be restarted and coupled.

If the desired result is to disable the HYPER-PPRC mode, the mode must be disabled through GDPS as specified in GDPS Metro/zGlobal Mirror: Planning and Implementation Guide, order number ZG24-1757. If the desired result is to have HYPER-PPRC mode enabled, then GDPS must be used to manage the session, and the mode must be configured as specified in GDPS/XRC VvRr Installation and Customization Guide, order number ZG24-6704.

Establish a PPRC relationship from the XRC primary volume to its associated HA volume, or a FAILOVER mode PPRC relationship, and reissue the XADDPAIR command.

Repair the PPRC relationship to match the previously recorded one, or use XDELPAIR to remove the XRC pair followed by XADDPAIR to permit the new PPRC relationship to be used.

Determine if the swap volume is the correct volume according to the configuration, and if its reported XRC session is active. If it is an incorrect volume then correct the PPRC relationships ,so that the primary volume is associated with the desired swap volume. If the PPRC relationship is correct, remove the swap volume from any existing XRC sessions, and/or terminate the incorrect XRC controller session. In either case, reissue the XADDPAIR command once the existing relationship(s) have been corrected or terminated.

If there is an existing XRC session in which the swap volume is a primary device, suspend or end the session. If there is no active XRC session use the SUSSESS or TERMSESS command to condition the session so it can be picked up by this system, or terminate it. Then reissue the XADDPAIR command.

Since the swap sessions will not be cleaned up automatically, the F ANTAS000,TERMSESS command(s) will need to be issued for each of the affected sessions. In addition, if this warning was issued as a result of an XEND after an unsuccessful transition from mode normal to mode HYPER-PPRC, all of the sessions in an ER group (as observed with an F ANTAS000,LISTSESS command) may need to be manually terminated on the swap device even though only a subset of swap utilities were added.

• Activating a PARMLIB member that changes the value of ALLOWENHANCEDREADER from NO to YES. To do this, all volumes in the session must first be suspended.
• Reducing the number of auxiliary storage control sessions in an Enhanced Reader SCSESSION, through a XDELPAIR command issued to a utility volume. To do this, all volumes in the associated SSID and SCSESSION must first be suspended.

If the change of AllowEnhancedReader from YES to NO is correct, follow the enhanced multiple reader disablement procedure in z/OS DFSMS Advanced Copy Services before continuing with volume resynchronization through the XADDPAIR command. If the parameter change is incorrect, issue the XSUSPEND command with TIMEOUT parameter, update the PARMLIB, and issue the XSTART command again.

• Configure sufficient alias devices for the utility volume on the swap device to satisfy the NumberReaderTasks parameter.
• Determine the number of available alias devices on the primary and swap utility volumes. Set NumberReaderTasks to the number of base address plus the least number of available alias devices.
• Allocate base addresses on the primary and swap storage controllers to serve as primary and swap utility devices. Use explicit XADDPAIR to add utility volumes until the required number of utilities is reached.

Ensure that the SWAP utility devices that are associated with the SWAP SSID are ONLINE to the SDM system. If not, vary the devices online and reissue the XSWAP SUSSWAP command.

If a large number of SSIDs are associated with this error, and the SWAP sessions are verified to be terminated, correct the problem by issuing the XSUSPEND TIMEOUT, XSTART MODE(NORMAL), and XADD SUSPENDED commands, and waiting for message ANTX8170W or ANTX8169I for all of the SWAP SSIDs or waiting for message ANTA8124I. Then issue the XSUSPEND TIMEOUT and XSTART MODE(HYPER-PPRC) commands followed by an XADDPAIR for the SWAP volume triplets.

To recover from a small number of SSIDs with this error, each associated Utility volume must be removed using XDELPAIR, and then re-added with XADDPAIR. If the Utility volume is associated with an Enhanced Reader primary storage control session or Single Reader session, all associated volume pairs must first be removed using XDELPAIR, then re-added after the Utility volume is re-established.

This return code also appears when the available WSDSs are full and the remaining cataloged WSDSs are on volumes that are offline. All volumes that contain working space data sets must be varied online.

For an XRC session, an OPEN error occurred while obtaining the format-1 DSCB for the journal, control, or state data set because of an error reading the VTOC for the volume. The data set can be cataloged but either does not exist on the volume indicated by the catalog, or an I/O error occurred while attempting to read the VTOC. This error can also appear if the control dataset is allocated in the Extended Address Space of an Extended Address Volume (EAV). Determine why the error has occurred, correct the error, and reissue the XSTART, XRECOVER, or XADVANCE command to restart the session.

For a Snapshot function, an error occurred while obtaining format-1 DSCB for a working space data set.

For an XRC session, an OPEN error occurred while obtaining the format-3 DSCB for the journal, control, or state data set because of an error reading the VTOC for the volume. The data set can be cataloged but either does not exist on the volume indicated by the catalog, or an I/O error occurred while XRC attempted to read the VTOC. Determine why the error has occurred, correct the error, and reissue the XSTART, XRECOVER, or XADVANCE command to restart the session.

For a Snapshot function, an error occurred while obtaining format-3 DSCB for a working space data set.

This return code is issued when the number of concurrent copy jobs exceeds the auxiliary storage percentage in the system in which the system data mover (SDM) is running.

For these return codes, cancel ANTAS000 and ANTASnnn and restart the session. When you contact IBM for assistance, provide associated SYS1.LOGREC information in addition to the data requested in the beginning of this section.

• The SVC dump taken at the time of the abend
• Any associated SYS1.LOGREC information in addition to
• The data requested in General Recovery Actions.

When you contact IBM for assistance, provide the SVC dump taken at the time of the abend, and any associated SYS1.LOGREC information in addition to the data requested in the beginning of this section.

When you contact IBM for assistance, provide the SVC dump taken at the time of the abend, and any associated SYS1.LOGREC information in addition to the data requested in the beginning of this section.