Explanation
The XRC function encountered an I/O error. The
message text provides the following information:
- device_number – The device number to
which the I/O is directed. If the device is associated with a utility
volume, the error can be a storage control error.
- serial_number – The volume serial number,
if available, of the device that encountered the I/O error.
- failing_CCW_command_code – The channel
command word (CCW) code that encounters the I/O error.
- failing_CCW_position – The position in
the channel program chain on which the error occurs. If the error
occurs at the first CCW in the chain (a Define Extent), the path to
the storage control or device can have been dropped. This can indicate
an operations error because of the storage path being removed.
- CCW data_area – The parameter list data
area of the failing CCW.
- full_error_description – A brief description
of the cause of the I/O error based on the sense data. The descriptions
are as follows:
- STORAGE_CONTROL_SESSION_NUMBER_ NOT_ACTIVE – This indicates
a dropped XRC session resulting from an error that ended the storage
control session. The error can occur when the update-handling capability
of XRC is exceeded by the update rate to the storage control. In this
case, examine the number and configuration of volumes managed by XRC
to determine the cause of the high update rate to the storage control.
If this error persists, the XRC environment can require reconfiguration.
This error can also occur if the timeout interval has expired.
- STORAGE_CONTROL_SESSION_NUMBER_ NOT_ACTIVE_ON_PATH_xx –
This indicates that the path group ID used by XRC in sending requests
to a storage control is physically unavailable. xx indicates
the channel path ID associated with the path group ID that is physically
unavailable. Ensure that device_number is online
(or at least one other device associated with this channel path),
and then vary the channel path xx offline and then
vary the channel path back online. This will make available the path
group ID needed by XRC. Issue the MVS™ MODIFY
command of PATHS to list the channel paths currently associated with
the device number device_number.
- NONVOLATILE_STORAGE_NOT_AVAILABLE – This indicates that
nonvolatile storage has been altered. Issue the DEVSERV MVS operator command to determine the status
of nonvolatile storage. Do not disable nonvolatile storage for storage
controls that have an active XRC session. Correct the problem by re-enabling
nonvolatile storage and issuing the XADDPAIR command to add the volume
or volumes behind the affected storage control to the XRC session.
- CACHE_NOT_AVAILABLE – This indicates that cache has been
disabled. Issue the DEVSERV MVS operator
command to determine the status of cache storage. Cache storage should
not be disabled for storage controls that have an active XRC session.
Correct the problem by re-enabling cache for the storage control and
issuing the XADDPAIR command to add the volume or volumes behind the
affected storage control to the XRC session.
- TOO_MANY_STORAGE_CONTROL_SESSION_ NUMBERS – This indicates
that either the maximum number of XRC sessions on the storage control
(from multiple MVS hosts) has
been exceeded or that the maximum number of concurrent copy and remote
copy sessions on the storage control has been exceeded. The LISTSESS
diagnostic command can be used to determine which sessions are active
on a storage control. See z/OS DFSMS Advanced Copy Services for
a description of the LISTSESS command. Reduce the number of active
sessions on the affected storage control and issue the XADDPAIR command
to add the volume or volumes behind the affected storage control to
the XRC session.
- DEVICE_NOT_PART_OF_ANY_XRC_SESSION – This indicates a dropped
XRC session resulting from an operations error that produced a reset
notification. This error can also indicate that an error has occurred
in the storage control cache or that the cache is disabled, causing
any knowledge of this device as part of an XRC session to be lost.
Issue the DEVSERV MVS operator
command to determine the status of cache storage. Correct the problem
by re-enabling cache for the storage control and issuing the XADDPAIR
command to add the volume or volumes behind the affected storage control
to the XRC session.
- PATH_GROUP_NOT_ESTABLISHED – This indicates a dropped XRC
session resulting from an operations error that produced a reset notification.
This error can also indicate that an error has occurred in the storage
control cache or that the cache is disabled, causing any knowledge
of this device as part of an XRC session to be lost. Issue the DEVSERV MVS operator command to determine
the status of cache storage. Correct the problem by re-enabling cache
for the storage control and issuing the XADDPAIR command to add the
volume or volumes behind the affected storage control to the XRC session.
- XRC_SESSION_ALREADY_ ACTIVE _FOR_DEVICE – This indicates
that another MVS system already
has an active XRC session on the specified device, or that the device
is active in a session that has been suspended. Only one XRC session
can be active per device.
- XRC_SESSION/DEVICE_SUSPENDED – This indicates that an XRC
session or device is suspended on an ESS storage control unit. The
error can occur on a session level when the update-handling capability
of XRC is exceeded by the update rate to the storage control. Examine
the number and configuration of volumes managed by XRC to determine
the cause of the high update rate to the storage control. If this
error persists, the XRC environment can require reconfiguration. This
error can also occur if the timeout interval has expired. This error
message can occur by command, at device or volume level.
- INVALID_COMMAND – This is due to issuing an XRC command
to a storage control that does not have XRC capability.
- INVALID_COMMAND_SEQUENCE – This is either due to an internal
error or because an XRC command has been issued to a storage control
that does not have XRC capability.
- CCW_COUNT_LESS_THAN_REQUIRED – This is due to an internal
error.
- INVALID_PARAMETER – This is either due to an internal error
or because an XRC command has been issued to a storage control that
does not have XRC capability.
- STORAGE_CONTROL_SESSION_NUMBER_ ZERO_OR_ALREADY_USED – This
is due to an internal error.
- STORAGE_CONTROL_CACHE_ALREADY_ BEING_READ – This is due
to an internal error.
System action
The XRC action taken is based upon the ERRORLEVEL
specified on the XSTART command, as follows:
- If ERRORLEVEL(SESSION) is specified, XRC suspends all active volumes
on any I/O error. Correct the error and restart the XRC session. The
session is suspended only if the volume is in a duplex state at the
time of the error. Errors before a volume reaching duplex state do
not affect the session.
- If ERRORLEVEL(VOLUME) is specified, the scope of the error determines
the action taken. If the error occurs for a single primary or secondary
volume, only the affected volume pair is removed from the session.
If the error impacts a storage control, all volume pairs using that
storage control are removed from the session. Certain errors have
the potential to end the XRC session.
- If ERRORLEVEL(group_name) is specified, XRC
suspends all volumes that belong to the specified group. Correct the
error and add the volume pairs back into the session.
System programmer response
If the problem is an environmental
or hardware error, then correct the error and restart the session
or volumes. If the problem persists, search the problem reporting
databases for a solution. If no solution exists, contact the IBM® Support Center. Provide the
system log and SVC dumps of the ANTAS000 and any ANTASnnn address
spaces that are active. To determine which address spaces
are active, enter the console command DISPLAY A,ANTAS*. In addition,
provide any SYS1.LOGREC information indicating the I/O error encountered.
For some errors, a GTF trace can be required to determine the cause
of the problem.
Source
Extended remote copy (XRC).