Channel return codes

Edit online
Channel return codes are provided for reference.

8 Command Agent on Enterprise Storage Server Failed Command.

Explanation

This return code means that the Enterprise Storage Server agent failed the command before it was run on the ESS-800.

User response

This error is unexpected. Contact IBM Support. If problem continues, restart copy services to clear problem.

24 Too many tasks are running on the Enterprise Storage Server currently.

Explanation

This return code means that the Enterprise Storage Server agent cannot process any more commands at this current time on the ESS-800.

User response

Wait and try again. If problem continues, restart copy services to clear problem.

91 Configuration build error.

Explanation

This return code means that a problem occurred in building the configuration that is returned from the Enterprise Storage Server.

User response

This error is unexpected. Contact IBM Support. If problem continues, restart copy services to clear problem.

92 Configuration retrieval error.

Explanation

This return code means that a problem occurred on the Enterprise Storage Server when the configuration information was gathered.

User response

This error is unexpected. Contact IBM Support. If problem continues, restart copy services to clear problem.

93 Configuration retrieval error.

Explanation

This return code means that the Enterprise Storage Server agent is starting up so no commands are able to be issued currently.

User response

Wait and try again. If problem continues, restart copy services to clear problem.

100 Not connected with server.

Explanation

This return code means that the CSM server is not connected with the ESS/DS server.

User response

Ensure that the configuration is correct and that the ESS/DS server is running, and then try again.

101 Connection lost with server after command was sent.

Explanation

This return code means that the CSM server lost the connection with the ESS/DS server after the command to the server was sent.

User response

Ensure that the configuration is correct and that the ESS/DS server is running, and then try again. The command might have already run successfully so be sure to check the results before you try the command again.

102 Invalid server version.

Explanation

This return code means that the ESS/DS server does not support the specified client request.

User response

Ensure that the configuration is correct and that the ESS/DS server is running at the supported level, and then try again.

120 Problem sending data to the server.

Explanation

This return code means that a problem occurred in sending data to the ESS/DS server.

User response

Ensure that the communications path between the CSM server and the ESS/DS server is valid and working, and that the ESS/DS server is running. Then, try again.

121 Problem reading data sent from the server.

Explanation

This return code means that a problem occurred in reading data from the ESS/DS server.

User response

Ensure that the communications path between the CSM server and the ESS/DS server is valid and working, and that the ESS/DS server is running. Then, try again.

122 Problem committing data that is sent to the server.

Explanation

This return code means that a problem occurred in committing data that is sent to the ESS/DS server.

User response

Ensure the communications path between the CSM server and the ESS/DS server is valid and working, and that the ESS/DS server is running. Then, try again.

130 Command timeout.

Explanation

This return code means that the ESS/DS server took longer to process the command than the allowed timeout time, so the CSM server timed out the request.

User response

Ensure that the configuration is correct and that the ESS/DS server is running. Before you retry the command, ensure that it did not already run successfully.

131 Command timeout on the ESS/DS server.

Explanation

This return code means that the ESS/DS server internally took longer to process the command than the allowed timeout time, so the ESS/DS server timed out the request.

User response

Ensure that the configuration is correct and that the ESS/DS server is running. Before you retry the command, ensure that it did not already run successfully.

140 Cluster failover occurred.

Explanation

This return code means that the ESS/DS server initiated a cluster failover after the command to the old valid cluster was sent.

User response

Ensure that the ESS/DS server is running with the cluster failover. Before you retry the command, ensure that it did not already run successfully.

150 Invalid LSS number on ESS/DS server.

Explanation

This return code means that the specified LSS number to run the command is not valid on the ESS/DS server.

User response

Ensure that the configuration is correct and that the ESS/DS server is running and try again. If this problem persists, contact IBM Support. To clear up, you might have to restart copy services on the ESS/DS.

151 Invalid Enterprise Storage Server name returned from the ESS/DS server.

Explanation

This return code means that an invalid Enterprise Storage Server name was returned from the ESS/DS server.

User response

Ensure that the configuration is correct and that the ESS/DS server is running, and then try again. If this problem persists, contact IBM Support; To clear up, you might have to restart copy services on the ESS/DS.

160 Invalid null parameter.

Explanation

This return code means that a null parameter was found for the specified inputs.

User response

This error was unexpected, contact IBM Support.

170 Duplicate request from client.

Explanation

This return code means that a duplicate request was sent from the client to the ESS/DS server. The old request fails and the new request continues to run.

User response

See the results from the new request.

180 No heartbeat mappings exist.

Explanation

This return code means that no heartbeat mappings existed on the ESS/DS for the specified configuration.

User response

Re-create the heartbeat mappings on the ESS/DS and try again.

181 Heartbeat not supported.

Explanation

This return code means that the heartbeat was not supported on the ESS/DS server.

User response

Ensure that the ESS/DS level is at the correct supported level and try again.

190 Problem in getting results of command from ESS/DS server.

Explanation

This return code means that the ESS/DS server had a problem in getting the results of the command. This issue might or might not be OK, it depends on whether the command was successful.

User response

Check the sense data returned for the command to see whether the command ran successfully. If not, capture the data to send to support to find out why it failed. If this problem persists, you might have to restart copy services.

222 Command buffer on ESS/DS is full.

Explanation

This return code means that the command buffer on the ESS/DS is too full to allow any more commands to be issued.

User response

Wait and try again. If this problem persists, capture logging data and contact IBM Support. To fix this problem, you might have to restart copy services.

255 Client closed connection before command was completed.

Explanation

This return code means that the client connection to the ESS/DS server was closed before the command was completed.

User response

Ensure that the command was issued successfully. If not, run the command again when the client connection to the ESS/DS is running.

901 No UCB found for a storage device.

Explanation

Ensure that the volumes are attached and are online at least once on this z/OS system.

User response

Attach and vary online the volumes on this z/OS System.

904 IOS connection no longer active.

Explanation

The address space that allows CSM to connect to z/OS is not active.

User response

Ensure that prerequisite levels of z/OS IOS are installed, and that the address space is active.

905 No UCB was found for a volume.

Explanation

Ensure that the volumes are attached and are online at least once on this z/OS system.

User response

Ensure that the volume is attached and is online at least once on this z/OS system.

906 Invalid function

Explanation

The z/OS system does not support this function.

User response

Ensure that prerequisite levels of z/OS IOS are installed for this function.

912 Insufficient RACF authority.

Explanation

Either no facility class is defined, or the facility class is defined but the user does not have access.

User response

To list this class, issue the command RLIST FACILITY ANT.ReplicationManager .

To add the appropriate permissions, issue commands similar to the commands that are in the following list. Replace USER_ID with the correct user.

RDEFINE FACILITY ANT.REPLICATIONMANAGER UACC(NONE) PERMIT ANT.ReplicationManager CLASS(FACILITY) ID(USER_ID) ACCESS(control)

After these changes are completed, restart the copy services management server.

914 Address space load failed.

Explanation

The address space that allows CSM to connect to z/OS might not be loaded.

User response

Ensure that prerequisite levels of z/OS IOS are installed, and that the address space is active.

919 UCBINFO error occurred.

Explanation

An internal error occurred when you process a z/OS command.

User response

Contact IBM software support.

920 IOSCDR error occurred. Possibly, one or more volumes are boxed.

Explanation

One of more volumes might be boxed. Use the d,u,dasd z/OS command to identify the boxed volumes.

User response

Ensure that all volumes are no longer boxed, then reissue the command.

921 Failure allocating an input buffer.

Explanation

An internal failure over allocating storage when you process a z/OS command.

User response

Contact IBM software support.

922 Failure allocating storage.

Explanation

An internal failure over allocating storage when you process a z/OS command.

User response

Contact IBM software support.

925 No paths to the volume.

Explanation

No paths accessible by z/OS were found to the volume.

User response

Ensure that the volume consists at least one path accessible by z/OS.

926 Address space unavailable; shutdown requested.

Explanation

The address space that allows CSM to connect to z/OS is unavailable, and a shutdown was requested.

User response

Ensure that prerequisite levels of z/OS IOS are installed, and that the address space is active.

927 Address space is unavailable; shutdown active.

Explanation

The address space that allows CSM to connect to z/OS is unavailable because a shutdown is active.

User response

Ensure that prerequisite levels of z/OS IOS are installed, and that the address space is active.

960 The z/OS system request timed out.

Explanation

A synchronous z/OS request for either FlashCopy or Safeguarded Copy was timed out. For Safeguarded Copy, this situation occurs if the timeout value exceeds and one or more devices are still preparing for the backup command.

User response

Ensure that no hardware or connectivity problems exists. Contact IBM Hardware Support if the problem persists.

961 CCW request not started.

Explanation

This return code is set for CCWs that might not be attempted by the time that z/OS abandoned the request. This code might be seen for the CCWs that IOS might not process yet because of errors that are encountered on CCWs earlier in processing or after a timeout condition.

User response

Check other error messages and ensure that all other issues are resolved. Contact IBM software support if the problem persists.

962 Invalid CCW received by z/OS.

Explanation

This code is returned if a CCW other than an expected one is received by z/OS. This situation is not expected, and is the result of an internal error.

User response

Contact IBM software support.

963 Unexpected relationship state was found.

Explanation

This code is returned if an invalid Safeguard Copy relationship state was found for a device.

User response

Contact IBM software support.

964 Unable to serialize with HyperSwap.

Explanation

Unable to serialize with HyperSwap. This situation might happen if a HyperSwap is started at the same time that the FlashCopy or Safeguarded Copy command is issued.

User response

Wait for the HyperSwap to complete and then retry the command.

973 Failure releasing storage.

Explanation

An internal failure in releasing storage when you process a z/OS command.

User response

Contact IBM software support.

990 Internal task error.

Explanation

An internal task control block failure when you process a z/OS command.

User response

Contact IBM software support.

998 An internal z/OS error occurred.

Explanation

An internal error occurred when you process a z/OS command.

User response

Contact IBM software support.

999 An abend occurred in z/OS.

Explanation

An abend occurred when you process a z/OS command.

User response

Contact IBM software support.

524292 An AOM error occurred when the command was issued.

Explanation

An AOM error 8 with reason code 4 was received when the command was issued.

User response

Refer to the command error message IWNH1575E.

524328 An AOM error occurred when the command was issued.

Explanation

An AOM error 8 with reason code 0x28 was received when the command was issued.

User response

Refer to the command error message IWNH1575E.

x0100 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0200 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0300 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x03E7 An error that involved an invalid UCB for the device.

Explanation

Of the set of volumes on an LSS to be managed, if one of the volumes is attached to z/OS, then they all must be attached to z/OS. One or more such volumes are not attached to z/OS.

User response

Ensure that all LSS volumes to be managed are either attached to MVS or not attached to z/OS.

x0400 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0500 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0700 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0800 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0900 The operation failed because a Storage Control restart is in process.

Explanation

An operation for an active channel program was queued in a Storage Control when a warm start was received by the path.

User response

Wait until the warm start completes, and then retry the command.

x0A01 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0A02 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0A03 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0A04 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0B00 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0D00 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0E00 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0F00 Internal Error.

Explanation

An unexpected internal error occurred.

User response

This error is unexpected, contact IBM Support.

x0F04 Attempt to activate Cache Fast Write Access and Cache Fast Write Access status is pending.

Explanation

An attempt was made to activate Cache Fast Write Access and Cache Fast Write Access status is pending.

x0F05 The addressed volume size is greater than the maximum allowed for the specified command.

Explanation

The addressed volume size is greater than the maximum allowed for the specified command.

x0F06 Attempt to Destage Modified Tracks with the non-volatile storage status failed or attempt to Discard DASD Fast Write data with data in the failed NVS for the device.

Explanation

An attempt was made to Destage Modified Tracks with the non-volatile storage status failed or attempt to Discard DASD Fast Write data with data in the failed NVS for the device.

x0F09 Attempt to Force Deactivate DASD Fast Write for Device and no data was pinned for the volume in the non-volatile storage.

Explanation

An attempt was made to Force Deactivate DASD Fast Write for Device and no data was pinned for the volume in the non-volatile storage.

x0F0D Command requires non-volatile storage and non-volatile storage is not available.

Explanation

Command requires non_volatile storage and non-volatile storage is not-available.

x0F11 For an Establish Peer-to-Peer Remote Copy Pair command, the primary device was not suspended.

Explanation

For an Establish Peer-to-Peer Remote Copy Pair command for resynchronization, the primary device was not suspended, or the addressed volume was not in a Cascading PPRC state and also in a Trusted Primed for Resynchronization State. Or the primary device was suspended, but the secondary device was not simplex or suspended Or the addressed volume was in a Cascading PPRC state and also in a Trusted Primed for Resynchronization State, but the secondary device was not suspended.

x0F12 For an Establish Peer-to-Peer Remote Copy Pair command with full copy or no copy, the primary and secondary devices are not Simplex.

Explanation

Attempt to establish a PPRC pair with full copy or no copy and the primary and secondary devices are not Simplex.

x0F13 An attempt to establish, suspend, or end a PPRC pair or establish a FlashCopy pair failed.

Explanation

An attempt was made to establish, suspend, or end a CKD PPRC pair and the secondary device is busy, reserved, or participating in a Concurrent Copy or XRC session that is not suspended.

When you attempt to establish, suspend, or end a Fixed Block PPRC pair or establish a FlashCopy pair, the LUN cannot be long busy, uninstalled, waiting for a Start Unit command, with Format Failed status, active on another interface, in a hardware failure state, or performing a Write Same or Format Unit.

x0F15 An Establish Peer-to-Peer Remote Copy Pair was received for a suspended volume that contains Pinned Data.

Explanation

An Establish Peer-to-Peer Remote Copy Pair was received for a suspended volume that contains Pinned Data.

x0F16 The address that is specified for the secondary of a PPRC pair is not correct.

Explanation

The address that is specified for the secondary of a PPRC pair is not correct.

x0F1B A suspend or end was issued for a PPRC pair to a volume that is Simplex or not participating in the operation for which the command is designed.

Explanation

Attempt to issue a Suspend Peer-to-Peer Remote Copy Pair order or Terminate Peer-to-Peer Remote Copy Pair order to a volume that is Simplex or not participating in the operation for which the command is designed.

x0F1C Attempt to Suspend Peer-to-Peer Remote Copy Pair with the primary as the suspended device while the pair Peer-to-Peer Remote Copy pending.

Explanation

Attempt to Suspend Peer-to-Peer Remote Copy Pair with the primary as the suspended device while the pair Peer-to-Peer Remote Copy pending.

x0F1D A Diagnostic Control command other than Diagnostic Initialize Subsystem that is failed for the subsystem.

Explanation

A Diagnostic Control command with an order other than x0B (Diagnostic Initialize Subsystem) was received on a subsystem that was in FC condition (Status Cannot be Determined) or a Diagnostic Control with an order other than x0F was received on a device that had an unreadable Partition Status Area.

x0F1F A Establish Data Mover Session, Establish Peer-to-Peer Remote Copy Pair, or DSO Establish FlashCopy command was received. The volume is restricted from participating in a Copy Services relationship due to volume expansion.

Explanation

A Establish Data Mover Session, Establish Peer-to-Peer Remote Copy Pair, or DSO Establish FlashCopy command was received. The volume is restricted from participating in a Copy Services relationship due to volume expansion.

x0F20 A Diagnostic Control command with a conditional Diagnostic Initialize Subsystem order was received and the subsystem contains a valid Global subsystem status track.

Explanation

A Diagnostic Control command with a conditional Diagnostic Initialize Subsystem order was received and the subsystem contains a valid Global subsystem status track.

x0F22 A device specified in a PPRC establish, a FlashCopy establish, a Safeguarded Copy Recovery command or Manage PPRC Session Members command is invalid.

Explanation

A device specified in a PPRC establish, a FlashCopy establish, a Safeguarded Copy Recovery command or any of the volumes specified in a Manage PPRC Session Members command is unconfigured, is in CE Mode or Status cannot be determined state (Sense format F, Message C).

x0F25 An attempt was made to Make Cache Storage Unavailable for Subsystem or Make non_volatile storage Unavailable for Subsystem while that storage is initializing.

Explanation

An attempt was made to Make Cache Storage Unavailable for Subsystem or Make non-volatile storage Unavailable for Subsystem while that storage is initializing.

x0F26 The two devices that are specified in the PPRC establish pair command are compatible.

Explanation

The two devices that are specified the PPRC establish pair command are not the same track capacity; not the same format (fixed block or CKD); the Standard or Track Space Efficient Secondary device is not greater than or equal to the capacity of the primary device; the Extent Space Efficient volumes are not the same capacity; or Establish Peer-to-Peer Remote Copy Pair specified a primary Extent Space Efficient volume and a secondary Track Space Efficient volume.

x0F28 Attempt to Read Pinned Tracks and the Cache Storage is failed or unavailable.

Explanation

An attempt was made to Read Pinned Tracks and the Cache Storage is failed or unavailable.

x0F29 Attempt to run a Perform Subsystem Function, Set Special Intercept Condition order on an interface on which no path group was established.

Explanation

Attempt to run a Perform Subsystem Function, Set Special Intercept Condition order on an interface on which no path group was established.

x0F2C A Diagnostic Control, Diagnostic Initialize Subsystem is received and a previous Diagnostic Initialize Subsystem is in progress.

Explanation

A Diagnostic Control, Diagnostic Initialize Subsystem is received and a previous Diagnostic Initialize Subsystem is in progress.

x0F2E A PSF Commit or other destage request cannot be performed because Internal Command Chains are not allowed as a result of a permanent device error.

Explanation

A PSF Commit or other destage request cannot be performed because Internal Command Chains are not allowed as a result of a permanent device error.

x0F2F A command was chained from a Reset Allegiance that was unsuccessful.

Explanation

A command was chained from a Reset Allegiance that was unsuccessful.

x0F30 A command chained from a Sense that bypassed device busy encounters the device busy condition.

Explanation

A command chained from a Sense that bypassed device busy encounters the device busy condition.

x0F34 Interface ID not a channel interface for this subsystem.

Explanation

Interface ID not a channel interface for this subsystem.

x0F37 A copy services command was received while the subsystem was attempting to install a new microcode load.

Explanation

A Establish FlashCopy, Withdraw FlashCopy, Establish Peer-to-Peer Remote Copy Paths, Establish Peer-to-Peer Remote Copy Pair, Establish Data Mover Session, Global Mirror Start Increment, Manage PPRC Sessions, Start / Resume Global Mirror was received while the subsystem was attempting to install a new microcode load.

x0F3B The mode of the device does not match the mode that is required by the subcommand modifier of Diagnostic Control command with the Emulation Control subcommand.

Explanation

The mode of the device does not match the mode that is required by the subcommand modifier of Diagnostic Control command with the Emulation Control subcommand.

x0F47 Attempt to read a sidefile and another channel program is already actively reading the sidefile.

Explanation

Attempt to read a sidefile and another channel program is already actively reading the sidefile.

x0F48 The device address is not associated with a Data Mover, Peer-to-Peer Remote Copy, or FlashCopy Session. Attempt to run a Session order or command on a channel path that owns the session and the addressed device is not in a grouped state on the path group.

Explanation

The device address is not associated with a Data Mover, Peer-to-Peer Remote Copy, or FlashCopy Session. Attempt to run a Session order or command on a channel path that owns the session and the addressed device is not in a grouped state on the path group.

x0F49 A command other than Sense ID, Read Device Characteristics, Read Configuration Data, Sense Subsystem Status, Read Subsystem Data, or Perform Subsystem Function (with an order of prepare to read subsystem data) was received on a device that was busy and the I/O was started with either a Sense ID, Read Device Characteristics, Read Configuration Data, Reset Summary Unit Check, or a Sense Subsystem Status command.

Explanation

A command other than Sense ID, Read Device Characteristics, Read Configuration Data, Sense Subsystem Status, Read Subsystem Data, or Perform Subsystem Function (with an order of prepare to read subsystem data) was received on a device that was busy and the I/O was started with either a Sense ID, Read Device Characteristics, Read Configuration Data, Reset Summary Unit Check, or a Sense Subsystem Status command.

x0F4C The MPLF partition is invalid or not initialized.

Explanation

The MPLF partition is invalid or not initialized.

x0F4D The MPLF user token is not valid or not defined for this channel interface and Partition.

Explanation

The MPLF user token is not valid or not defined for this channel interface and Partition.

x0F51 The establish PPRC paths command or the establish PPRC Copy Pair with Failover option, would cause more than the maximum number of secondary controllers to be identified.

Explanation

The establish PPRC paths or the establish PPRC Copy Pair with Failover option, would cause more than the maximum number of secondary controllers to be identified. The maximum number of secondary controllers maybe four or sixteen depending on the level of microcode.

x0F52 The PPRC operation or a channel extender that is being used for a copy operation is reporting an error and the command cannot be completed.

Explanation

The PPRC operation or a channel extender that is being used for a copy operation reports an error and the command cannot be completed due to any or a combination of the following:
  1. Abnormal conditions at the secondary controller.
  2. Abnormal conditions that are related to the secondary device.
  3. The communications paths between the primary and remote controller are not functioning.
  4. Communications might not be established with the secondary control unit.

x0F53 The SSID, Logical Subsystem Number (LSS), or sequence number parameters that are contained in this command do not match the formation that is stored in the control unit.

Explanation

The SSID, Logical Subsystem Number (LSS), or sequence number parameters that are contained in this order do not match the formation that is stored in the control unit. This reason code might be presented for incorrect information for either the primary or secondary controller.

x0F54 The conditions at the secondary controller would not allow the PPRC operation to function properly.

Explanation

The conditions at the secondary controller would not allow the Peer-to-Peer Remote Copy operation to function properly. Secondary cache that is not enabled for the controller or device, or NVS at the secondary is not available.

x0F55 One or more paths to the secondary control unit failed to be established.

Explanation

One or more paths to the secondary control unit failed to be established. Query the logical paths to determine their status.

x0F56 Establish to a PPRC or FlashCopy pair was issued for a volume that contains pinned data.

Explanation

Establish to a PPRC or FlashCopy pair was issued for a volume that contains pinned data.

x0F57 The addressed device is in a suspended PPRC state. All write commands with Normal Authorization indicated are rejected.

Explanation

The addressed device is in a suspended PPRC state. All write commands with Normal Authorization indicated are rejected.

x0F58 A command was received that conflicts with an established PPRC state for the device.

Explanation

A command was received that conflicts with an established PPRC state for the device.

x0F59 The remove PPRC path command failed because PPRC pairs are still active between the controllers.

Explanation

A Remove PPRC Paths order was received and the devices are in a PPRC state on the controller. All devices that were using the identified secondary paths must be stopped in a simplex state before Remove PPRC Paths can succeed.

x0F5A The primary control unit is timed out when you attempt to communicate with a PPRC secondary device.

Explanation

The primary control unit that is timed out attempting to communicate with a PPRC secondary device. If this error is returned on a control command, Command Reject sets on in sense. If returned on a write command, environmental data presents sets on in sense.

x0F5B The secondary PPRC device address indicates a device outside of the address range, which is supported or installed on the secondary controller.

Explanation

The secondary PPRC device address indicates device outside of the address range that is supported or installed on the secondary controller.

x0F5C The Withdraw from Data Mover Session order with the Withdraw Totally bit set might not be processed because no devices are in an unreserved state or just one device is in the session.

Explanation

The Withdraw from Data Mover Session order with the Withdraw Totally bit set might not be processed because no devices are in an unreserved state or just one device is in the session.

x0F5D Attempted to group too many channels in the path group.

Explanation

Attempted to group too many channels in the path group.

x0F5E Attempted to create too many path groups.

Explanation

Attempted to create too many path groups.

x0F5F An establish PPRC Paths command was issued on a primary control unit port and one of the paths that are specified in the parameters is the same as the one the establish PPRC Paths command was received on.

Explanation

An establish PPRC Paths command was issued on a primary control unit port and one of the paths that are specified in the parameters is the same as the one the establish PPRC Paths command was received on. The order must be received on a path that would not be converted to host channel mode.

x0F60 The secondary volume for an establish PPRC pair command or the target volume for an establish FlashCopy command is in a grouped state, which implies the volume is online to a host.

Explanation

The secondary volume for an establish PPRC pair command or the target volume for an establish FlashCopy command is in a grouped state, which implies the volume is online to a host. This state conflicts with the order's flag byte setting, which disallows the operation if the volume is online.

x0F61 This operation might not be started on an unassigned alias.

Explanation

This operation might not be started on an unassigned alias.

x0F62 The logical subsystem that is specified in the command parameters is not owned by the cluster that the current chain is executing.

Explanation

The logical subsystem that is specified in the command parameters is not owned by the cluster that the current chain is executing in. Note: This problem is due to specifying a fixed block device that uses a CKD device address on the ESCON interface. When the CKD device address is detected, the controller code assumes that the device address is the one, the operation is for. However, if it is for a device in the other cluster, the microcode does not have a mechanism to transfer ownership of the operation to the correct cluster. Until this issue is fixed, the operation is unit that is checked with this reason code.

x0F63 This operation might be issued on an alias address.

Explanation

This operation might be started on an alias address.

x0F64 This operation might not be issued on an alias address.

Explanation

This operation might not be issued on an alias address.

x0F65 The Establish PPRC Pair command or the Establish FlashCopy command might not complete. A target Fixed Block LUN cannot be reserved to another initiator, or the target Fixed Block LUN is not ready.

Explanation

The Establish PPRC Pair command or the Establish FlashCopy command might not complete. A target Fixed Block LUN cannot be reserved to another initiator, or the target Fixed Block LUN is not ready.

x0F66 A Perform Write Monitor Action detected a condition that does not allow the operation to be successful. Byte 9 of the sense specifies the specific reason.

Explanation

Volume with requested track format might not be allocated.

Sense Byte 9 Definition
01
A Start Write Monitor is issued to a volume with an active Write Monitor.
02
A Stop or Reset Write Monitor action is issued to a volume without an active Write Monitor.

x0F67 Alias access is attempted with incorrect base specified.

Explanation

Alias access that is attempted with incorrect base specified.

x0F68 Specified RAID rank is not part of this subsystem.

Explanation

Specified RAID rank is not part of this subsystem.

x0F69 A PPRC prefix command or Write Fixed Block Data command was issued to a PPRC secondary, which was suspended by the command.

Explanation

A PPRC prefix command or Write Fixed Block Data command was issued to a PPRC secondary, which was suspended by the command.

x0F6A A PSF Manage Alias Address order that uses Aliases across CU images format was received, but the host did not indicate it supports Aliases across CU images.

Explanation

A PSF Manage Alias Address order that uses Aliases across CU images format was received, but the host did not indicate it supports Aliases across CU images.

x0F70 A PPRC prefix command or Write Fixed Block Data command was issued to a simplex volume (secondary volume was stopped).

Explanation

A PPRC prefix command or Write Fixed Block Data command was issued to a simplex volume (secondary volume was stopped).

x0F71 An Establish Peer-to-Peer Remote Copy Pair command was issued specifying 3-site Incremental Resync Establish and 3-site Incremental Resync mechanism was not running.

Explanation

An Establish Peer-to-Peer Remote Copy Pair command was issued specifying 3-site Incremental Resync Establish and 3-site Incremental Resync mechanism was not running.

x0F72 An Establish Peer-to-Peer Remote Copy Pair command was issued specifying 3-site Incremental Resync Establish and the secondary 3-site Incremental Resync time sequence is newer than the primary 3-site Incremental Resync time sequence.

Explanation

An Establish Peer-to-Peer Remote Copy Pair command was issued specifying 3-site Incremental Resync Establish and the secondary 3-site Incremental Resync time sequence is newer than the primary 3-site Incremental Resync time sequence.

x0F73 An Establish Peer-to-Peer Remote Copy Pair command was issued specifying 3-Site Incremental Resync Establish, and the specified primary and secondary are not both targets of the same Peer-to-Peer Remote Copy primary, or the specified primary's secondary is not the same volume as the specified secondary's primary volume.

Explanation

An Establish Peer-to-Peer Remote Copy Pair command was issued specifying 3-Site Incremental Resync Establish, and the specified primary and secondary are not both targets of the same Peer-to-Peer Remote Copy primary, or the specified primary's secondary is not the same volume as the specified secondary's primary volume.

x0F74 An error occurred for a command that was attempting to establish or end a Peer-to-Peer Remote Copy Multi-Target relationship.

Explanation

An error occurred for a command that was attempting to establish or end a Peer-to-Peer Remote Copy Multi-Target relationship. The following reasons can cause the errors as defined by sense byte 9.

Sense Byte 9 Definition
01
Establish Peer-to-Peer Remote Copy Pair is establishing a Peer-to-Peer Remote Copy Multi-Target relationship and the Peer-to-Peer Remote Copy Multi-Target Microcode Engineering Change is not active on all Central Electronics Complexes of the Primary Control Unit.
02
Establish Peer-to-Peer Remote Copy Pair is establishing a Peer-to-Peer Remote Copy Multi-Target relationship and one or more of the Secondary Control Units do not have the Microcode Engineering Change active that supports Peer-to-Peer Remote Copy Multi-Target.
03
An Establish Peer-to-Peer Remote Copy Pair command would result in a Peer-to-Peer Remote Copy primary with more than two active secondary relationships.
04
An Establish Peer-to-Peer Remote Copy Pair command would result in a Peer-to-Peer Remote Copy primary with more than three secondary relationships.
05
The addressed device was a secondary of a Peer-to-Peer Remote Copy Multi-Target relationship and the Establish Peer-to-Peer Remote Copy Pair command that is attempted to make it a primary of another Peer-to-Peer Remote Copy Multi-Target Relationship.
0A
An Establish Peer-to-Peer Remote Copy Pair command is issued to a volume with Bytes 32 - 35 bit 9 (Initiate PPRC Failover Mode for recovery site) set to one and Bytes 32 - 35 bit 17 (Convert to Peer-to-Peer Remote Copy Multi-Target on Cascaded Failover) set to zero and the volume is a cascaded Peer-to-Peer Remote Copy volume (both a primary and a secondary volume) and is also the primary of two or more relationships (Peer-to-Peer Remote Copy Multi-Target configuration).
0C
For Toggle Peer-to-Peer Remote Copy Multi-Target Incremental Resync bitmaps, Bytes 4-5 (Primary Volume ID) or Bytes 6-15 (Primary Control Unit Sequence Number) did not match the primary volume for the Toggle Volume ID (Bytes 2-3).
0D
The Peer-to-Peer Remote Copy Multi-Target Incremental Resync relationship between the partner secondaries cannot be created because more than 16 LSS associations are established for the partner secondary volume that is running the command.
0E
The Peer-to-Peer Remote Copy Multi-Target Incremental Resync relationship between the partner secondaries cannot be created because more than four volume relationships are associated with the volume that is running the command.
0F
The Peer-to-Peer Remote Copy Multi-Target Incremental Resync relationship cannot be created because Out-of-Sync Track bitmap (OOS) Bitmaps are not available.
10
For Toggle Peer-to-Peer Remote Copy Incremental Resync bitmaps, the Out-Of-Sync Track bitmap (OOS) bitmaps cannot be toggled because a FlashCopy operation is pending and the setting of the Out-Of-Sync Track bitmap (OOS) bitmaps for the FlashCopy operation is in progress.
12
A Toggle Peer-to-Peer Remote Copy Multi-Target Incremental Resync bitmaps command was issued to a device that was previously in a Preserver Mirror FlashCopy relationship and the relationship was stopped by a Withdraw FlashCopy command with Bytes 2 - 3 bit 10 (Force Withdraw for Preserve Mirror Relation) set to one.
13
Once the Cascading PPRC Failover Mode is removed and if an Establish Peer-to-Peer Remote Copy Pair Bytes 32 - 35 bit 17 (Convert to Multiple Target Peer-to-Peer Remote Copy on Cascaded Failover) is set to zero, ensure that bit 17 is set during a failover to a cascading PPRC relationship.
14
A Peer-to-Peer Remote Copy Multi-Target 3 site Incremental Resync pair exists.
15
A Peer-to-Peer Remote Copy Multi-Target 3 site Incremental Resync pair exists on the target.

User response

Correct the problem that is causing the error and issue the command again.

x0F75 An Establish Peer-to-Peer Remote Copy Pair command would result in a Peer-to-Peer Remote Copy primary with two synchronous secondary or two Async Peer-to-Peer Remote Copy secondary.

Explanation

An Establish Peer-to-Peer Remote Copy Pair command would result in a Peer-to-Peer Remote Copy primary with two synchronous secondary or two Async Peer-to-Peer Remote Copy secondary.

x0F76 An Establish Peer-to-Peer Remote Copy Pair command was issued to a Peer-to-Peer Remote Copy primary in a Cascading PPRC configuration and would result in the Peer-to-Peer Remote Copy primary having more than one secondary.

Explanation

An Establish Peer-to-Peer Remote Copy Pair command was issued to a Peer-to-Peer Remote Copy primary in a Cascading PPRC configuration and would result in the Peer-to-Peer Remote Copy primary having more than one secondary.

x0F77 A Suspend or Resume Control command was issued to a volume that did not have 3-Site Incremental Resync active.

Explanation

A Suspend or Resume Control command was issued to a volume that did not have 3-Site Incremental Resync active.

x0F79 The command is not allowed through a Soft Fence State. Byte 9 of the sense indicates the specific reason.

Explanation

The command is not allowed through a Soft Fence State. Byte 9 of the sense indicates the specific reason.
01
The device that is in the Soft Fenced State is either the Channel Connection device, a Peer-to-Peer Remote Copy primary device, or a FlashCopy source device.
02
The device that is in the Soft Fenced State is either a Peer-to-Peer Remote Copy secondary or a FlashCopy target device.

User response

Ensure one or more volumes are no longer in a soft fenced state. If you use z/OS Basic HyperSwap, this feature can be achieved by issuing the z/OS command SETHS UNFENCE.

x0F7A CKD access to a Fixed Block volume failed.

Explanation

CKD access to a Fixed Block volume failed. Byte 9 of the sense specifies the specific reason.

Sense Byte 9 Definition
01
A CKD Reserve command attempted to reserve a Fixed Block volume but the Fixed Block volume is reserved to a SCSI Host.
02
A CKD I/O was issued to a Fixed Block volume but the Fixed Block volume is reserved to a SCSI Host.

x0F7B A Resource Group policy was violated.

Explanation

A Resource Group Policy was specified and the current user did not have sufficient authority to run the command. Byte 9 of the sense specifies the specific reason.

Sense Byte 9 Definition
01
Global Mirror Session Number violation (Destination Device detected violation) or Global Mirror Master violation (Connection LSS detected violation).
02
Global Mirror Session Subordinate Disallowed.
03
Global Mirror Session Disallowed (Destination Device detected violation).
04
Encryption Group Scope Mismatch (Primary/Source detected violation).
05
Resource Scope violation (Source detected violation, default case).
06
Resource Scope violation (Target detected violation, default case).
10
CKD PPRC Secondary Resource Scope violation (Primary detected violation).
11
CKD PPRC Primary Resource Scope violation (Secondary detected violation).
12
CKD FlashCopy Full Volume Target Resource Scope violation (Source detected violation).
13
CKD FlashCopy Full Volume Source Resource Scope violation (Target detected violation).
14
CKD FlashCopy Dataset Target Resource Scope violation (Source detected violation).
15
CKD FlashCopy Dataset Source Resource Scope violation (Target detected violation).
20
FB PPRC Secondary Resource Scope violation (Primary detected violation).
21
FB PPRC Primary Resource Scope violation (Secondary detected violation).
22
FB FlashCopy Full Volume Target Resource Scope violation (Source detected violation).
23
FB FlashCopy Full Volume Source Resource Scope violation (Target detected violation).
24
Reserved for FB FlashCopy Dataset Target Resource Scope violation (Source detected violation).
25
Reserved for FB FlashCopy Dataset Source Resource Scope violation (Target detected violation).
30
Passthrough Global Resource Scope violation (Connection Device detected violation).
31
Passthrough Global Resource Scope violation (Connection LSS detected violation).
40
User Resource Scope violation (Destination Logical volume detected violation).
41
User Resource Scope violation (Destination LSS detected violation).
42
User Resource Scope violation (Create Resource detected violation).
43
User Resource Scope violation (Modify Resource detected violation).
44
User Resource Scope violation (Delete Resource detected violation).

User response

Verify that the correct LSS and Volume was used. If so, verify that correct user ID is being used. If the correct user id is being used, then verify that the user ID has sufficient authority to perform the requested action. Once the permissions issue is corrected, try the command again.

x0F80 Attempt to run a Global Command on an interface that was unavailable for Global Commands by a Perform Subsystem Function.

Explanation

Attempt to run a Global Command on an interface that was unavailable for Global Commands by a Perform Subsystem Function, Set Special Intercept Condition order.

x0F81 An attention was presented on an interface that was unavailable for Global Commands by a Perform Subsystem Function.

Explanation

An attention was presented on an interface that was unavailable for Global Commands by a Perform Subsystem Function.

x0F82 No resources available to create relationships for the establish FlashCopy command or the number of relationships exceed the maximum that is allowed.

Explanation

No resources available to create relationships for the establish FlashCopy command or the number of relationships exceed the maximum that is allowed.

x0F83 2107 battery feature unavailable or not installed. FlashCopy requires the battery for proper operation.

Explanation

2107 battery feature unavailable or not installed. FlashCopy requires the battery for proper operation.

x0F84 The FlashCopy volumes that are not specified in the same Logical Subsystem or they are not of the same size and format.

Explanation

The FlashCopy volumes that are not specified in the same Logical Subsystem or they are not of the same size and format.

x0F85 The target FlashCopy volume is a PPRC primary or secondary or is an XRC primary volume or is in a Concurrent Copy session.

Explanation

The target FlashCopy volume is a PPRC primary or secondary or is an XRC primary volume or is in a Concurrent Copy session.

x0F86 The feature that the command references is not installed, enabled, or supported by the subsystem.

Explanation

The feature that the command references is not installed, enabled, or supported by the subsystem. Contact hardware support for more information on adding the feature.

x0F87 Outboard copy operations are not allowed to overwrite the volume. The volume is in use by another copy operation such as XRC or TDMF.

Explanation

Outboard copy operations are not allowed to overwrite the volume. The volume is in use by another copy operation such as XRC or TDMF.

x0F88 An Establish Peer-to-Peer Remote Copy Pair command specified Copy All Tracks and the secondary device is a FlashCopy source volume whose target volume is a Track Space Efficient volume.

Explanation

An Establish Peer-to-Peer Remote Copy Pair command specified Copy All Tracks and the secondary device is a FlashCopy source volume whose target volume is a Track Space Efficient volume. A full copy of the data would cause all tracks to be copied to the space efficient volume.

x0F89 Establish FlashCopy specified a Preserve Mirror Required or Preferred operation. A condition that prevents the Preserve Mirror operation from being successful.

Explanation

Establish FlashCopy specified a Preserve Mirror Required or Preferred operation. A condition that prevents the Preserve Mirror operation from being successful. Byte 9 of the sense specifies the specific reason.

Sense Byte 9 Definition
01
The specified source volume is NOT a Peer-to-Peer Remote Copy primary device.
02
The secondary volume to the specified source volume and the secondary volume to the target volume are not in the same Storage Facility Image (SFI).
03
The Peer-to-Peer Remote Copy relationship between the specified source volume and its secondary volume is NOT full-duplex.
04
The Peer-to-Peer Remote Copy relationship between the specified target volume and its secondary volume is NOT full-duplex.
05
The secondary control unit does not contain the installed microcode, which supports Preserve Mirror operations.
06
The FlashCopy Preserve Mirror inband command was not successful at the secondary control unit because a Preserve Mirror relationship existed.
07
An error was detected while the Define Subsystem Operation command to the secondary volume was sent. This sense is generated when a DSO read/write sent to the secondary control unit failed.
08
Restore FlashCopy with Changed Tracks in the Change Recording bitmap was set and Preserve Mirror Required was set and the existing FlashCopy relation was not a Preserve Mirror relation.
09
Establish FlashCopy specified a Preserve Mirror (Remote Pair FlashCopy) operation and the source or target device is a Peer-to-Peer Remote Copy Multi-Target primary device and Use Remote Pair FlashCopy is not set for any PPRC relationship or is set for more than one PPRC relationship.
0A
Bytes 24 - 25 bit 10 (Start/Continue Change Recording Type 2) was set to '1' and the secondary control unit does not contain the installed microcode, which supports Change Recording Type 2.
0B
Establish FlashCopy specified a Preserve Mirror (Remote Pair FlashCopy) operation and the source or target device is a Peer-to-Peer Remote Copy Multi-Target primary device and Bytes 2 - 3 bit 7 (Start Change Recording Type 1) or Bytes 24 - 35 bit 10 (Start/Continue Change Recording Type 2) is set to 1 and the Peer-to-Peer Remote Copy Multi-Target relationship that was previously designated for Use Remote Pair FlashCopy (Preserve Mirror) no longer has that designation.
0C
Establish FlashCopy specified Bytes 2 - 3 bit 13 (Target Volume might be an XRC Primary Volume), the target volume is an XRC primary volume, and the XRC session was not enabled for XRC Remote Pair FlashCopy.
0D
Establish FlashCopy specified Bytes 2 - 3 bit 13 (Target Volume might be a XRC Primary Volume), the target volume is an XRC primary volume in an XRC active state and the source volume is not an XRC primary volume.
0E
Establish FlashCopy specified Bytes 2 - 3 bit 13 (Target Volume might be a XRC Primary Volume), the source, and the target volumes are XRC primary volumes in the XRC active state but the source and target volumes are not in the same XRC session.
0F
Establish FlashCopy specified Bytes 2 - 3 bit 13 (Target Volume might be a XRC Primary Volume), the target volume is an XRC primary volume and the source volume is an XRC primary volume in the suspended state.
10
Establish FlashCopy specified PPRC Remote Pair FlashCopy Preferred in Byte 26 (PPRC Remote Pair FlashCopy - Preserve Mirror) and the volume is in a Multiple Target Peer-to-Peer Remote Copy relationship.
11
Establish FlashCopy specified PPRC Remote Pair FlashCopy Preferred in Byte 26 (PPRC Remote Pair FlashCopy - Preserve Mirror) and the FlashCopy target volume is both an XRC primary volume and PPRC primary volume.
12
Establish FlashCopy specified Bytes 2 - 3 bit 13 (Target Volume might be a XRC Primary Volume) and the XRC Session is not enabled to suspend instead of offloading Long Busy sense.
13
For Establish FlashCopy or Withdraw FlashCopy, and error occurred when you set the XRC bitmaps for the FlashCopy source or target volume.
14
Establish FlashCopy specified PPRC Remote Pair FlashCopy Preferred in Byte 26 (PPRC Remote Pair FlashCopy - Preserve Mirror) and the DS8000 no longer supports PPRC Remote Pair FlashCopy Preferred.

x0F8A A Restore FlashCopy relationship command was received and the volumes were not in a persistent relationship whose background copy was completed.

Explanation

A Restore FlashCopy relationship command was received and the volumes were not in a persistent relationship whose background copy was completed.

x0F8B Critical Volume mode was specified with an asynchronous PPRC operation.

Explanation

Critical Volume mode was specified with an asynchronous PPRC operation.

x0F8E An establish FlashCopy specified a FlashCopy target volume that was already an Global Mirror primary volume or was the primary of a synchronous PPRC pair whose secondary is a Cascaded Peer-to-Peer Remote Copy volume.

Explanation

An establish FlashCopy specified a FlashCopy target volume that was already an Global Mirror primary volume or was the primary of a synchronous PPRC pair whose secondary is a Cascaded Peer-to-Peer Remote Copy volume.

x0F8F A volume cannot be in both an XRC session and an Async Peer-to-Peer Remote Copy session simultaneously.

Explanation

A volume cannot be in both an XRC session and an Async Peer-to-Peer Remote Copy session simultaneously.

x0F90 Withdraw FlashCopy was issued to a PPRC Secondary Volume and the relationship was established as a Preserve Mirror operation and the command was issued from a Host (out of band command).

Explanation

Withdraw FlashCopy was issued to a PPRC Secondary Volume and the relationship was established as a Preserve Mirror operation and the command was issued from a Host (out of band command).

x0F91 A Perform Subsystem Function Prepare to Read Lock Data command was received requesting Multi-Path Lock Facility data and the data was not available.

Explanation

A Perform Subsystem Function Prepare to Read Lock Data command was received requesting Multi-Path Lock Facility data and the data was not available for presentation because either the requested Multi-Path Lock Partition is not initialized, or cache is not available for use.

x0F92 An Establish FlashCopy or Withdraw FlashCopy detected a condition for the target volume that does not permit the operation to be successful.

Explanation

An Establish FlashCopy or Withdraw FlashCopy detected a condition for the target volume that does not permit the operation to be successful. Byte 9 of the sense specifies the reason.

Sense Byte 9 Definition
01
Establish FlashCopy specifies a FlashCopy Target volume that is in the process of a Peer-to-Peer Remote Copy Cascading Failover/Failback recovery operation.

Establish FlashCopy specifies a FlashCopy Target volume that is also a Peer-to-Peer Remote Copy volume which was established with Start Local 3-Site Incremental Re-sync with or without initialization set

02
Withdraw FlashCopy was issued to a FlashCopy relationship with its target volume in the process of a Peer-to-Peer Remote Copy Cascading Failover/Failback recovery operation AND the Background Copy for that FlashCopy relationship has not completed

Withdraw FlashCopy was issued to a FlashCopy relationship with its target volume a Peer-to-Peer Remote Copy volume which was established with Start Local 3-Site Incremental Re-sync with or without initialization set AND the Background Copy for that FlashCopy relationship has not completed.

03
Establish FlashCopy is not allowed between a T10 Data Integrity Field (DIF) LUN and a Standard (non T10 DIF LUN).

x0F93 A cache storage control command cannot be accepted now because a Multi-Path Lock Disconnect operation is in progress for an initialized Multi-Path Lock Partition.

Explanation

A cache storage control command cannot be accepted now because a Multi-Path Lock Disconnect operation is in progress for an initialized Multi-Path Lock Partition.

x0F94 A command was received specifying that it was supposed to be sent to the PPRC remote control unit for execution. The volume that is receiving the command is not a PPRC primary, or a PPRC primary does not exist for the specified remote secondary.

Explanation

A command was received specifying that it was supposed to be sent to the PPRC remote control unit for execution and the volume that is receiving the command is not a PPRC primary, or a PPRC primary does not exist for the specified remote secondary.

x0F95 A Multi-Path Lock Facility order that can generate an Attention message cannot be accepted because the subsystem message buffer is full.

Explanation

A Multi-Path Lock Facility order that can generate an Attention message cannot be accepted because the subsystem message buffer is full.

x0F96 An establish PPRC pair command attempted to perform a transition between modes that is not allowed.

Explanation

An establish PPRC pair command attempted to perform a transition between modes that is not allowed. The only valid transition to PPRC Extended Distance is from a state of suspension.

x0F97 Processing for a Withdraw FlashCopy failed for a Preserve Mirror relation. Byte 9 of the sense specifies the reason.

Explanation

Processing for a Withdraw FlashCopy failed for a Preserve Mirror relation. Byte 9 of the sense specifies the reason.

Sense Byte 9 Definition
01
An error occurred sending a Withdraw FlashCopy to the secondary volume or the Withdraw FlashCopy cannot be sent to the secondary volume.

x0F98 An establish FlashCopy command with Incremental PPRC was issued for a volume that is not in the correct PPRC state.

Explanation

An establish FlashCopy command with Incremental PPRC was issued for a volume that is not in the correct PPRC state. The PPRC Primary volume was not suspended at the time the establish FlashCopy command was issued.

x0F99 A command was received specifying an operation that is not supported on the hardware or software level of 2107.

Explanation

A command was received specifying an operation that is not supported on the hardware or software level of 2107.

x0F9A The volume types for a Establish FlashCopy or Establish Peer-to-Peer Remote Copy Pair is restricted.

Explanation

The establish command specified a volume type that is restricted for the given type of relationship. Byte 9 of the sense specifies the specific reason.

Sense Byte 9 Definition
01
Establish Peer-to-Peer Remote Copy Pair specified a restricted volume type combination. The specified secondary volume was a Extent Space Efficient volume.
03
Establish Peer-to-Peer Remote Copy Pair specified a restricted volume type combination. The specified primary volume was an Extent Space Efficient volume.
10
Establish FlashCopy specified a restricted volume type combination. The specified target volume was a Extent Space Efficient volume.
12
Establish FlashCopy specified a restricted volume type combination. The specified source volume was an Extent Space Efficient volume.

x0F9B An establish FlashCopy order or establish PPRC Pair command was rejected because the target LUN is reserved to another initiator.

Explanation

An establish FlashCopy order or establish PPRC Pair command was rejected because the target LUN is reserved to another initiator.

x0F9C An establish FlashCopy command cannot complete due to internal hardware conditions or lack of resources to manage the relationship.

Explanation

An establish FlashCopy command cannot complete due to internal hardware conditions or lack of resources to manage the relationship.

x0F9D An establish FlashCopy command cannot complete because the maximum number of relationships for the volume was exceeded. (Data Set level FC only).

Explanation

An establish FlashCopy command cannot complete because the maximum number of relationships for the volume was exceeded. (Data Set level FC only).

x0F9E PPRC Extended Distance mode cannot be specified whether Alphabet PPRC and FlashCopy Incremental Copy is also specified.

Explanation

PPRC Extended Distance mode cannot be specified whether Alphabet PPRC and FlashCopy Incremental Copy is also specified.

x0F9F Destage of modified tracks that are failed because the Space Efficient Repository or the Space Efficient Extent Pool is out of space.

Explanation

Destage of modified tracks that are failed because the Space Efficient Repository or the Space Efficient Extent Pool is out of space.
  • A Establish FlashCopy order cannot complete when the source or target volume is a Track or Extent Space Efficient volume and destage of either volume's modified tracks fails due to out of space in the Space Efficient Repository or the Space Efficient Extent Pool.
  • A Peer-to-Peer Remote Copy secondary device encountered a write failure due to an out of space condition in the Space Efficient Extent Pool.

x0FA0 A FlashCopy Remote command must specify the remote source volume to be the secondary PPRC volume for the PPRC primary volume this command was addressed to.

Explanation

A FlashCopy Remote command must specify the remote source volume to be the secondary PPRC volume for the PPRC primary volume this command was addressed to.

x0FA1 The source and destination ports for a PPRC path over FCP must be unique.

Explanation

The source and destination ports for a PPRC path over FCP must be unique. Any single port cannot be used as both source and destination.

x0FA2 An Establish PPRC Path command must specify all ESCON paths or all FCP paths. ESCON and FCP paths might not be mixed within the same command.

Explanation

An Establish PPRC Path command must specify all ESCON paths or all FCP paths. ESCON and FCP paths might not be mixed within the same command.

x0FA3 The primary and secondary WWNN (World-Wide Node Name) must be a valid WWNN for a 2107 box.

Explanation

The primary and secondary WWNN (World-Wide Node Name) must be a valid WWNN for a 2107 box.

x0FA4 If FCP paths are specified in the PPRC Establish Path command, then the protocol of the adapters that are specified in the command might not be FCAL (Fibre Channel Arbitrated Loop).

Explanation

If FCP paths are specified in the PPRC Establish Path command, then the protocol of the adapters that are specified in the command might not be FCAL (Fibre Channel Arbitrated Loop).

x0FA5 The FlashCopy operation does not allow the specification of extents - it is only valid for full volume.

Explanation

The FlashCopy operation does not allow the specification of extents - it is only valid for full volume.

x0FA6 An establish FlashCopy command cannot complete because the maximum number of FlashCopy target relationships that are exceeded for one or more of the sources tracks specified in the Establish FlashCopy extents.

Explanation

An establish FlashCopy command cannot complete because the maximum number of FlashCopy target relationships that are exceeded for one or more of the sources tracks specified in the Establish FlashCopy extents. The number of target relationships might be reduced by withdrawing existing relationships, or waiting for existing relationships to complete (through background copy completing).

x0FA7 An establish FlashCopy command cannot complete because it did not specify that an existing target track to become a source track.

Explanation

An establish FlashCopy command cannot complete because it did not specify that an existing target track to become a source track. Any single track might not be both a source and a target track, and a target track might have one source only.

x0FA8 A withdraw FlashCopy order cannot complete because the maximum number of relationships for the volume was exceeded.

Explanation

A withdraw FlashCopy order cannot complete because the maximum number of relationships for the volume was exceeded. If a Withdraw FlashCopy command causes relationships to be split, this can cause the number of relationships to increase. The number of relationships might be reduced by withdrawing existing relationships, or waiting for existing relationships to complete (through background copy completing).

x0FA9 An establish FlashCopy was received while the volume was inhibited for FlashCopy relationship establish.

Explanation

An establish FlashCopy was received while the volume was inhibited for FlashCopy relationship establish.

x0FAA For PPRC Extended Distance, an invalid transition between establishment modes was attempted. A transition from Extended Distance to any mode other than PPRC Synchronous mode is not allowed.

Explanation

For PPRC Extended Distance, an invalid transition between establishment modes was attempted. A transition from Extended Distance to any mode other than PPRC Synchronous mode is not allowed.

x0FAB A Phase 1 FlashCopy command was received on a volume that has Phase 2 relations.

Explanation

A Phase 1 FlashCopy command was received on a volume that has Phase 2 relations.

x0FAC A command was received that is no longer supported for FlashCopy.

Explanation

A command was received that is no longer supported for FlashCopy.

x0FAD A FlashCopy operation cannot be completed because one or more specified volumes were in an offline or inaccessible state.

Explanation

A FlashCopy operation cannot be completed because one or more specified volumes were in an offline or inaccessible state.

x0FAE An establish FlashCopy command cannot complete because it specified an existing target track to become a target track.

Explanation

An establish FlashCopy command cannot complete because it specified an existing target track become a target track. Any single track might not be both a source and a target track, and a target track might have one source only.

User response

For the flash to successfully verify that the target track is not already an existing target track and then retry the command. If a relationship exists to this target, then it needs to be withdrawn before the new one can be established.

x0FAF An establish FlashCopy command cannot complete because it specified that an existing source track to become a target track. Any single track might not be both a source and a target track, and a target track might have one source only.

Explanation

An establish FlashCopy command cannot complete because it specified that an existing target track to become a target track. Any single track might not be both a source and a target track, and a target track might have one source only.

x0FB0 An attempt was made to Establish ESCON PPRC paths between two control units with FCP paths that are existing between the control units, or an attempt was made to Establish FCP PPRC paths between two control units with ESCON paths that are existing between the control units.

Explanation

An attempt was made to Establish ESCON PPRC paths between two control units with FCP paths that are existing between the control units, or an attempt was made to Establish FCP PPRC paths between two control units with ESCON paths that are existing between the control units. The World Wide Node Name or Control Unit Serial Number for the secondary control unit might not be obtained, so the determination that the command was acting on an existing association was made based on the secondary SSID, which might not be unique.

x0FB1 An attempt was made to Establish FCP PPRC paths on a port with existing FICON logical paths.

Explanation

An attempt was made to Establish FCP PPRC paths on a port with existing FICON logical paths.

x0FB2 An attempt was made to Establish or Remove ESCON PPRC paths between two control units with FCP paths that are existing between the control units, or an attempt was made to Establish or Remove FCP PPRC paths between two control units with ESCON paths that are existing between the control units.

Explanation

An attempt was made to Establish or Remove ESCON PPRC paths between two control units with FCP paths that are existing between the control units, or an attempt was made to Establish or Remove FCP PPRC paths between two control units with ESCON paths that are existing between the control units.

x0FB3 A PPRC secondary volume was found to be in an unconfigured, or undefined state.

Explanation

A PPRC secondary volume was found to be in an unconfigured, or undefined state.

x0FB4 An Establish FlashCopy command attempted to reverse the order of the FlashCopy relation, and the target bitmap was not all zeroes.

Explanation

An Establish FlashCopy command attempted to reverse the order of the FlashCopy relation, and the target bitmap was not all zeroes.

x0FB5 A Establish PPRC Paths command failed because device 0 is not configured in the secondary Logical Subsystem.

Explanation

A Establish PPRC Paths command failed because device 0 is not configured in the secondary Logical Subsystem.

x0FB6 The state of an existing FlashCopy relation does not allow the specified establish FlashCopy, withdraw FlashCopy, Start (Checkin) Consistency Group, Perform Safeguarded Copy Recovery or Release Allocated Space operation.

Explanation

The state of an existing FlashCopy relation does not allow the specified establish FlashCopy, withdraw FlashCopy, or Release Allocated Space operation.

Sense Byte 9 Definition
00
Reason Code Qualifier not specified
01
Establish FlashCopy specified starting a new change recording relation and a change recording relation already exists. Establish FlashCopy specified Start/Continue Change Recording Type 1 set to one, Restore set to zero and a Change Recording Type 1 relation existed for the specified source and target.
  • Establish FlashCopy specified Start/Continue Change Recording Type 2 set to one, Restore set to zero and a Change Recording Type 2 Relation existed for the specified source and target.
02
Establish FlashCopy specified Start/Continue Change Recording Type 1 set to one, Restore set to one, and Change Recording Type 1 was NOT active for the specified source and target.
03
Establish FlashCopy specified Start/Continue Change Recording Type 2 set to one, Restore set to one, and Change Recording Type 2 was NOT active for the specified source and target.
04
For Establish FlashCopy, no relationship was found for the restore (FlashCopy increment) or the fast reverse restore request.
  • Establish FlashCopy specified Restore, Source, and Target Volumes and a Full Volume Relationship with Change Recording was not found.
  • Establish FlashCopy specified Restore, Source Volume Only and a Full Volume Relationship with Change Recording Type 1 was not found.
  • Establish FlashCopy specified Fast Reverse Restore and the target address that is specified in the parameters was NOT the existing relation's source address.
05
Establish FlashCopy change recording type mismatch. Establish FlashCopy specified Start/Continue Change Recording Type 1 and a Change Recording Type 2 relationship exists for the specified source and target volume.
  • Establish FlashCopy specified Start/Continue Change Recording Type 2 and a Change Recording Type 1 relationship exists for the specified source and target volume.
06
Establish FlashCopy specified Revertible and the relationship was already in a revertible state and its sequence number is NOT equal to the sequence number specified in Bytes 36-39.
07
Establish FlashCopy specified Revertible and the specified source and target volumes reverses the original relationship.
08
Establish FlashCopy specified Fast Reverse Restore and the relationship is NOT reversed by the specified parameters.
09
Establish FlashCopy specified Restore and not Fast Reverse Restore or specified Revertible AND a previous Establish FlashCopy specified Fast Reverse Restore for the relationship.
0A
Establish FlashCopy specified Restore or Revertible AND the relationship is in a failed state due to out of space condition on a space efficient target volume or the volume is fenced.
0B
Withdraw FlashCopy specified Revert or Commit AND the relationship is in a failed state.
0C
Withdraw FlashCopy specified Revert or Commit AND the relationship does not exist for the specified volumes.
0D
Release Allocated Space encountered an error.
  • Release Allocated Space specified a volume that is an Extent Space Efficient volume and is in a Concurrent Copy, Peer-to-Peer Remote Copy, or XRC relationship.
  • Release Allocated Space specified Release Space by Extent and the volume that is specified in Bytes 4-5 is in a FlashCopy relationship and one or more of the extents specified overlap with an existing FlashCopy relationship on the device.
  • Release Allocated Space specified Release Space by Extent and the volume that is specified in Bytes 4-5 in a Track Space Efficient volume.
0E
An error occurred on the Remote Peer-to-Peer Remote Copy Control Unit or Global Mirror Subordinated Control Unit.
0F
The Establish FlashCopy® specified target volume is a Peer-to-Peer Remote Copy Primary Volume and the volume is waiting to release space.
10
Establish FlashCopy specified Start/Continue Change Recording Type 1 or Start/Continue Change Recording Type 2 and the specified target volume is a source volume of an existing relationship.
11
Establish FlashCopy specified a source or target volume that is in an existing relationship, which specified Revertible and that relationship is in a revertible state.
12
Establish FlashCopy specified a source volume that is the target of an existing incremental relationship.
13
Release Allocated Space Phase 2 Restriction: When Guarantee Tracks are Logically Initialized was set to one, the volume is an Extent Space Efficient volume, and the specified extents were not aligned to a DS8000 extent boundary.
14
Establish FlashCopy specified a source volume that is the target volume of an existing relationship and the existing relationship for the volume is in the failed state.
15
Withdraw FlashCopy is removing a relationship (Volume A to Volume B) where the target volume (Volume B) is also the source of a cascaded relationship (Volume B to Volume C). The relationship (Volume A to Volume B) did not complete the background copy. Withdraw of the relationship (Volume A to Volume B) does not complete until the background copy finishes.
16
For Establish FlashCopy, the specified target volume is the source volume of Safeguarded Copy relationship or incremental is set on the FlashCopy, which is not allowed onto a Safeguarded source.
17
For Establish FlashCopy Create Safeguarded Copy Consistency Group Reservation, the backup volume does not exist.
18
For Establish FlashCopy Create Safeguarded Copy Consistency Group Reservation, the source volume is the target of a different FlashCopy relationship.
19
For Establish FlashCopy Create Safeguarded Copy Consistency Group Reservation, the source volume is the target of Safeguarded Copy recovery relationship.
1A
For Establish FlashCopy Create Safeguarded Copy Consistency Group Reservation, the source volume is in a Safeguarded Copy reservation state with a different sequence number.
1B
For Establish FlashCopy Create Safeguarded Copy Consistency Group Reservation, the number of consistency groups exceeds the maximum that is allowed by the Control Unit.
1C
For Withdraw FlashCopy Consistency Group Action OR Perform Safeguarded Copy Recovery, the specified sequence number did not match an existing sequence number for the volume.
1D
For Start (Checkin) Consistency Group, the volume does not have a consistency group reservation.
1E
For Start (Checkin) Consistency Group, the specified sequence number did not match the consistency group reservation sequence number.
1F
For Start (Checkin) Consistency Group, the Safeguarded Copy consistency group reservation timer expired before the command was received.
20
For Consistency Group Created, the FlashCopy, Peer-to-Peer Remote Copy, or the Safeguarded Copy long busy timer expired before the command was received or for a Safeguarded Copy a previous Start (Checkin) Consistency Group command specifying Freeze Volume with the designated sequence number was not received.
21
For Establish FlashCopy, the volume consists an active Safeguarded Copy consistency group relationship and the specified Sequence Number is not greater than the Sequence Number of the active consistency group relationship.
22
For Perform Safeguarded Copy Recovery, the specified source volume is in more than one recovery relationship.
23
For Perform Safeguarded Copy Recovery, the command tried to change a recovery relationship that was performing a background copy to one without a background copy.
24
A Withdraw FlashCopy command is attempting to remove a Consistency Group but the Sequence Number is associated with a recovery action for the volume.
25
For Perform Safeguarded Copy Recovery, the designated sequence number is the active Safeguarded Copy consistency group.
26
FlashCopy onto Global Mirror target cannot be performed because a Global Mirror force Consistency Group is in progress.
27
For Perform Safeguarded Copy Recovery, the specified source volume is in a PPRC suspended state.
28
For Perform Safeguarded Copy Recovery, the specified target volume is not in a PPRC simplex state.
29
For Perform Safeguarded Copy Recovery, the specified target volume is not in a FlashCopy simplex state.
2A
For Perform Safeguarded Copy Recovery, PPRC path could not be created between the Recovery and the Production volumes.
2B
For Perform Safeguarded Copy Recovery, a PPRC pair could not be established on a specified target due to internal hardware conditions or lack of resources that are required to manage the relationship.
2C
For Establish FlashCopy, a FlashCopy pair could not be established because the specified target is a Safeguarded Copy source and a Safeguarded Copy reservation is active for the volume.
2D
For Establish FlashCopy Create Safeguarded Copy Consistency Group Reservation, an out of space condition is detected on the backup volume or extent pool volume.

x0FB7 An establish FlashCopy command was received and VM mini-disk mode was specified, but the existing FlashCopy relation does not have VM mini-disk mode set OR, the establish FlashCopy command received does not specify VM mini-disk mode, but the existing FlashCopy relation does have VM mini-disk mode specified.

Explanation

An establish FlashCopy command was received and VM mini-disk mode was specified, but the existing FlashCopy relation does not have VM mini-disk mode set OR, the establish FlashCopy command received does not specify VM mini-disk mode, but the existing FlashCopy relation does have VM mini-disk mode specified.

x0FB8 A withdraw FlashCopy command was received specifying revert or commit, but the existing relation is not revertible.

Explanation

A Establish FlashCopy command was received specifying revertible and the relation is already in a revertible state and has a sequence number identical to the sequence number specified in Establish FlashCopy. A withdraw FlashCopy command was received specifying revert or commit, but the existing relation is not revertible.

x0FB9 A withdraw FlashCopy command attempted to split an existing full volume incremental FlashCopy relation.

Explanation

A withdraw FlashCopy command attempted to split n existing relation and a condition exists that prevents the Withdraw FlashCopy from being successful. Cases are:
  • An existing full volume incremental FlashCopy relation
  • A full volume relation with a Track Space Efficient target volume.
  • The relation is a Preserve Mirror relation, the existing relation is a Full Volume relation, and the relation is being split.
  • The relation is a non-Preserve Mirror relation and Start Background Copy and Terminate Relationship is set, the existing relation is a Full Volume relation, and the relation is being split.

x0FBA Change Recording was specified by an establish FlashCopy, Global Mirror Start Increment command, or an Establish PPRC Pair command with PPRC Failover Mode specified or start 3-Site Incremental Resync but Change Recording is already active, and was not previously activated by the same operation type.

Explanation

Change Recording was specified by an establish FlashCopy, Global Mirror Start Increment command, or an Establish PPRC Pair command with PPRC Failover Mode specified or start 3-Site Incremental Resync but Change Recording is already active, and was not previously activated by the same operation type.

x0FBB A withdraw FlashCopy specified extents, which contain a full volume source relation. The command operates on all non_full volume source relations and on all target relations that have tracks in the specified extents.

Explanation

A withdraw FlashCopy specified extents, which contain a full volume source relation. The command operates on all non_full volume source relations and on all target relations that have tracks in the specified extents.

x0FBC A Establish FlashCopy command specified that Fast Reverse Restore was received while a previous Fast Reverse Restore operation was in progress.

Explanation

A Establish FlashCopy command specified that Fast Reverse Restore was received while a previous Fast Reverse Restore operation was in progress.

x0FBD The Space Efficient Volume does not allow the specified Establish FlashCopy, Withdraw FlashCopy, or Establish Peer-to-Peer Remote Copy Pair command parameters.

Explanation

The Space Efficient Volume does not allow the specified Establish FlashCopy, Withdraw FlashCopy, or Establish Peer-to-Peer Remote Copy Pair command parameters:
  • A Establish FlashCopy command did not specify Permit Track or Extent Space Efficient Target and the specified target is a Track or Extent Space Efficient volume.
  • An Establish Peer-to-Peer Remote Copy Pair command did not specify Permit Track or Extent Space Efficient Secondary and the specified secondary is a Track or Extent Space Efficient volume.
  • A Establish FlashCopy command specified Perform Background Copy and Permit Space Efficient Target and the target volume is a Space Efficient Volume.
  • A Establish FlashCopy command specified a Preserve Mirror operation and the local FlashCopy target or the remote FlashCopy target are Space Efficient volumes.
  • A Withdraw FlashCopy command specified Start Background Copy and one or more target volumes are Space Efficient volumes.
  • A Withdraw FlashCopy command specified Terminate All Relations and the command was received on the source volume and one or more target volumes are Space Efficient volumes.

User response

If the session is a FlashCopy session that is using space efficient volumes as targets, the no copy option must be set on the session prior to issuing the Flash command. Permit Space Efficient Target is always set for you by the code.

x0FBE Release Allocated Space failed because the specified Space Efficient Repository or Space Efficient Extent Pool was offline when you attempt to release space. A Space Efficient Volume Query might not complete because the associated Space Efficient Repository or Space Efficient Extent Pool is offline.

Explanation

Release Allocated Space failed because the specified Space Efficient Repository or Space Efficient Extent Pool was offline when you attempt to release space. A Space Efficient Volume Query might not complete because the associated Space Efficient Repository or Space Efficient Extent Pool is offline.

x0FBF An establish PPRC pair command specifying PPRC Failover Mode or PPRC Failback mode has detected a condition that does not allow the operation to be successful. Byte 9 of the sense specifies the specific reason.

Explanation

An establish PPRC pair command specifying PPRC Failover Mode or PPRC Failback mode has detected a condition that does not allow the operation to be successful. Byte 9 of the sense specifies the specific reason.
Sense Byte 9 Definition
00
An Establish PPRC command specifying PPRC Failover Mode or PPRC Failback mode was received, but the PPRC remote copy pair is already in the requested state.
01
An Establish PPRC command specifying PPRC Failover Mode and Prepare for Safeguarded Copy Incremental Recovery was received, but the PPRC remote copy pair is already in the requested state.

x0FC0 For PPRC Failover Mode, the primary volume information is not correct for a volume that is a PPRC secondary volume or a Cascading PPRC volume in the receiving 2107; for that secondary or cascading volume, information is stored identifying its primary volume.

Explanation

For PPRC Failover Mode, the primary volume information is not correct for a volume that is a PPRC secondary volume or a Cascading PPRC volume in the receiving 2107; for that secondary or cascading volume, information is stored identifying its primary volume. The secondary volume that is specified is not the same information that is stored for that primary volume.

x0FC1 For PPRC Failover Mode, the addressed volume is not a Peer-to-Peer Remote Copy secondary volume in full-duplex mode, or a Cascading Peer-to-Peer Remote Copy volume whose secondary state is not full-duplex or suspended.

Explanation

For PPRC Failover Mode, the addressed volume is not a Peer-to-Peer Remote Copy secondary volume in full-duplex mode, or a Cascading Peer-to-Peer Remote Copy volume whose secondary state is not full-duplex or suspended.

For PPRC Failover Mode with Override 3-Site Incremental Resync Checking set, the addressed device was a Peer-to-Peer Remote Copy primary volume.

x0FC2 For PPRC Failback Mode, the primary volume information is not correct for a volume that is a PPRC primary volume or a Cascading PPRC volume in the receiving 2107.

Explanation

For PPRC Failback Mode, the primary volume information is not correct for a volume that is a PPRC primary volume or a Cascading PPRC volume in the receiving 2107; for a primary volume, information is stored identifying its secondary volume. The specified secondary volume information is not the same information that is stored for that secondary volume. For a Cascading volume, information is stored identifying its primary volume. The current specified secondary volume information is not the same information that is stored for that primary volume.

x0FC3 For PPRC Failback Mode, the addressed volume is not a PPRC primary in a suspended state, or a Cascading PPRC volume whose primary state and secondary state is suspended.

Explanation

For PPRC Failback Mode, the addressed volume is not a PPRC primary in a suspended state, or a Cascading PPRC volume whose primary state and secondary state is suspended.

x0FC4 For Global Mirror, consistency cannot be maintained due to a timeout of a paused increment or for other conditions that caused the volume to be in an incorrect state.

Explanation

For Global Mirror, consistency cannot be maintained due to a timeout of a paused increment or for other conditions that caused the volume to be in an incorrect state.

x0FC5 For Global Mirror, a close session cannot be performed because volumes are still in the session.

Explanation

For Global Mirror, a close session cannot be performed because volumes are still in the session.

x0FC6 For Cascading PPRC modes, the specified secondary volume might not be in a PPRC primary synchronous mode in any state of suspension, pending duplex, or full-duplex.

Explanation

For Cascading PPRC modes, the specified secondary volume might not be in a PPRC primary synchronous mode in any state of suspension, pending duplex, or full-duplex.

x0FC7 For Cascading PPRC modes, when this command specifies a secondary volume that is determined to be in a PPRC relationship, that relationship must be established in a Cascading PPRC state.

Explanation

For Cascading PPRC modes, when this command specifies a secondary volume that is determined to be in a PPRC relationship, that relationship must be established in a Cascading PPRC state.

x0FC8 For Cascading PPRC modes, if the command specifies Cascading PPRC with synchronous mode, the volume that is receiving this command as specified in the primary volume parameter might not be a PPRC secondary volume in PPRC Global Copy mode.

Explanation

For Cascading PPRC modes, if the command specifies Cascading PPRC with synchronous mode, the volume that is receiving this command as specified in the primary volume parameter might not be a PPRC secondary volume in PPRC Global Copy mode.

x0FC9 The specified session is already open for the LSS or the maximum number of sessions that are allowed are already met.

Explanation

The specified session is already open for the LSS or the maximum number of sessions that are allowed are already met.

x0FCA The specified volume is already associated with another session.

Explanation

The specified volume is already associated with another session or the specified volume is the primary of a Peer-to-Peer Remote Copy pair, which was established with ESCON paths.

x0FCB A Manage PPRC Session Members command to add or remove volumes are received by the subsystem but did not complete successfully.

Explanation

The Manage PPRC Session Members command for add or remove of volume members failed for one of the following reasons:
  • No open session equal to the session specified in the parameters.
  • The command specified a format that is incompatible with the format of the volumes that are already members of the session.

User response

All volumes need to be removed from the existing session on the hardware and then readded back in using the same format.

x0FCC A Global Mirror Start Increment order was received by the subsystem and the session or members of the session are not in the correct state.

Explanation

A Global Mirror Start Increment order was received by the subsystem and the session or members of the session are not in the correct state, the Peer-to-Peer Remote Copy pairs are established with ESCON paths, or the Peer-to-Peer Remote Copy pairs are completing error recovery.

x0FCD A Global Mirror session was not in Consistency Group In Progress State when the Global Mirror subordinate issued the Revertible Establish FlashCopy command to the remote 2107 as part of the formation of a Consistency Group.

Explanation

A Global Mirror session was not in Consistency Group In Progress State when the Global Mirror subordinate issued the Revertible Establish FlashCopy command to the remote 2107 as part of the formation of a Consistency Group.

x0FCE Pause/Terminate Global Mirror specified Pause Global Mirror with Consistency but a condition was detected that does not allow the operation to be successful.

Explanation

Pause/Terminate Global Mirror specified Pause Global Mirror with Consistency but a condition was detected that does not allow the operation to be successful..

x0FD0 PPRC paths are not established between the master 2107 and one or more of the subordinate 2107s specified in a Start or Resume Global Mirror command OR ESCON paths are specified by the Start or Resume Global Mirror command.

Explanation

PPRC paths are not established between the master 2107 and one or more of the subordinate 2107s specified in a Start or Resume Global Mirror command OR ESCON paths are specified by the Start or Resume Global Mirror command.

x0FD1 Incorrect parameters were specified for the Start or Resume Global Mirror Session command, or the Start or Resume Global Mirror Session command was issued while the Global Mirror session wasn't paused, or the Start or Resume Global Mirror Session command was issued while a Pause or Terminate Global Mirror command was in process or this 2107 supports only a single Global Mirror master per storage system and a Start or Resume Global Mirror command was issued on an Global Mirror master 2107, with a different Global Mirror master running on this 2107.

Explanation

This return code might have different meanings, which depend on microcode level. For hardware, which supports multiple Global Mirror Masters per storage system: A Start or Resume Global Mirror command with Byte 1, bit 0 set to one was received on a global mirror master 2107, and the specified parameters did not match the existing global mirror session, the existing global mirror session was not paused or the existing global mirror session is processing Pause or Terminate Global Mirror command. Or the Start / Resume Global Mirror command was issued to a Logical Subsystem other than the one on which this session was initially started. For hardware, which supports only a single Global Mirror Master per storage system: A Start or Resume Global Mirror command was issued on an Global Mirror master 2107, with a different Global Mirror master that runs on this 2107, or a Start or Resume Global Mirror command was issued on an Global Mirror master 2107 and the specified parameters did not match the actual subordinate sequence number or the specified master sequence number did not match the master sequence number that is previously configured by a Start or Resume Global Mirror command.

x0FD2 A Pause or Terminate Global Mirror command specified a Global Mirror configuration that does not exist. The Pause or Terminate Global Mirror command was issued to a Logical Subsystem other than the one on which this session was initially started.

Explanation

A Pause or Terminate Global Mirror command specified a Global Mirror configuration that does not exist. The Pause or Terminate Global Mirror command was issued to a Logical Subsystem other than the one on which this session was initially started.

x0FD3 A Start or Resume Global Mirror command was received by a subordinate 2107 with already 32 Global Mirror masters that are configured for this subordinate 2107 or there would be more than 32 Masters created.

Explanation

A Start or Resume Global Mirror command was received by a subordinate 2107 with already 32 Global Mirror masters that are configured for this subordinate 2107 or there would be more than 32 Masters created.

x0FD4 A Start or Resume Global Mirror command was received by a subordinate 2107 and the specified master sequence number did not match the existing master sequence number for the specified session ID.

Explanation

A Start or Resume Global Mirror command was received by a subordinate 2107 and the specified master sequence number did not match the existing master sequence number for the specified session ID, or the specified session ID did not match the existing session ID for the specified master sequence number. Or, a Broadcast DSO Write command was received by a subordinate 2107 and the specified subordinate sequence number did not match the actual subordinate sequence number or the specified master sequence number did not match the master sequence number that is previously configured by a Start or Resume Global Mirror command.

x0FD5 An order or command was received in FICON Secure Volume Manager mode, which is not allowed.

Explanation

An order or command was received in FICON Secure Volume Manager mode, which is not allowed.

x0FD6 An Global Mirror Subordinate 2107 received a Broadcast DSO Write command while you process a previously issued Broadcast DSO Write command.

Explanation

An Global Mirror Subordinate 2107 received a Broadcast DSO Write command while you process a previously issued Broadcast DSO Write command.

x0FD7 A Start or Resume Global Mirror, Pause or Terminate Global Mirror, or Broadcast DSO Write command that is failed because one or more of its nonvolatile structures might not be updated or accessed due to failure or due to the 2107 being in single cluster mode.

Explanation

A Start or Resume Global Mirror, Pause or Terminate Global Mirror, or Broadcast DSO Write command that is failed because one or more of its nonvolatile structures might not be updated or accessed due to failure or due to the 2107 being in single cluster mode.

x0FD8 A Pause or Terminate Global Mirror failed because the termination might not complete without compromising the consistent copy of the data.

Explanation

A Pause or Terminate Global Mirror failed because the termination might not complete without compromising the consistent copy of the data.

x0FD9 Volume must be both a PPRC Primary and an XRC primary with the PPRC/XRC HyperSwap enabled bit set in the Establish Peer-to-Peer Remote Copy Pair order.

Explanation

Volume must be both a PPRC Primary and an XRC primary with the PPRC/XRC HyperSwap enabled bit set in the Establish Peer-to-Peer Remote Copy Pair order.

x0FDA The Suspend or Resume Control order with toggle and flag set cannot be sent to the secondary PPRC volume, or was rejected by the secondary controller for reasons other than the Peer-to-Peer Remote Copy secondary not being also an XRCn primary.

Explanation

The Suspend or Resume Control order with toggle and flag set cannot be sent to the secondary PPRC volume, or was rejected by the secondary controller for reasons other than the Peer-to-Peer Remote Copy secondary not being also an XRCn primary.

x0FDB The Suspend or Resume Control order with toggle and flag set was rejected due to no XRC establishment on the Peer-to-Peer Remote Copy secondary volume.

Explanation

The Suspend or Resume Control order with toggle and flag set was rejected due to no XRC establishment on the Peer-to-Peer Remote Copy secondary volume.

x00080028 The command or query that failed because no z/OS path was available to issue the command or query to the volume.

Explanation

To send commands or queries to volumes by using the z/OS Connection, an operational path from z/OS to the device must exist. When this command or query was issued, no operational paths from z/OS to the volume existed.

User response

Restore the path between z/OS and the device or devices. The following z/OS commands might assist you in determining why the path is no longer operational:
  • D M=DEV(ZOS_DEV_NUM) - This command displays the paths for a device and indicates whether the path is online and operational.
  • DS P, ZOS_DEV_NUM - This command displays the paths status for a device.

x00000f10 The request was issued to a volume that was not configured or the request requires at least one volume to be configured and no volumes are configured for this LSS.

Explanation

The request was issued to a volume that was not configured or the request requires at least one volume to be configured and no volumes are configured for this LSS.

x51000000 The command or query that is failed because the volume is boxed.

Explanation

To send commands or queries to volumes by using the z/OS Connection, the device must not be boxed. When this command or query was issued, the volume was boxed on z/OS.

User response

Vary the online path or paths between z/OS and the device or devices. Alternatively, you can vary the online device or devices. The following z/OS commands might assist you in determining why the volume is boxed and ensuring it is no longer boxed:
  • D U, DASD, ZOS_DEV_NUM, RANGE - This command displays the status of a device or a range of devices on z/OS.
  • D M=DEV(ZOS_DEV_NUM) - This command displays the paths for a device and whether the path is online and operational.
  • DS P, ZOS_DEV_NUM - This command displays the paths status for a device.
  • VARY ZOS_DEV_NUM, ONLINE - This command varies online a device to z/OS.
  • VARY PATH(ZOS_DEV_NUM, CHPD), online - This command varies online a path to a device on z/OS.

x51110000 The asynchronous operation is still in progress, and IDCAMS is still waiting for completion. For other system components (for example, SMS), refer to messages issued by those components with detailed actions that are taken as the result of this return code. This condition is detected by IOS.

Explanation

The asynchronous operation is still in progress, and IDCAMS is still waiting for completion. For other system components (for example, SMS), refer to messages issued by those components with detailed actions that are taken as the result of this return code. This condition is detected by IOS.

User response

Wait for the asynchronous operation to complete, and try the action again.

x11111111-11111111-11111111-11111111-11111111-11111111-11111111-11111111 While the specified task was running, a warm start or cluster failover occurred.

Explanation

While the specified task was running, a warm start or cluster failover occurred. This error condition is unique to ESS 800 devices.

User response

After the copy services server is operational, submit the task again.