Explanation
In the message,
text is one
of the following:
- REASON UNKNOWN
- OPERATOR COMMAND
- RETRY LIMIT EXCEEDED
- SYSPLEX PARTITIONING OF LOCAL SYSTEM
- SYSPLEX PARTITIONING OF REMOTE SYSTEM
- OTHER SIDE IS SAME DIRECTION
- SUBCHANNEL NOT OPERATIONAL FOR RESUME
- START REQUEST FAILED
- CONNECTED TO NON-XCF SIGNALLER
- NON-XCF SIGNALLER USING PATH
- HALT I/O FAILED
- PURGE I/O FAILED
Cross-system coupling facility (XCF) stopped a signalling
path. Unless the operator initiated the stop, the signalling path
remains defined to XCF.
In the message text:
- direction
- The direction of the signalling path that stopped. direction is
one of the following:
- PATHIN for an inbound signalling path.
- PATHOUT for an outbound signalling path.
- devn
- The device number for the signalling path that stopped.
- REASON UNKNOWN
- XCF cannot determine why the signalling path was stopped.
- OPERATOR COMMAND
- The operator entered a SETXCF STOP command. The device is no longer
defined to XCF.
- RETRY LIMIT EXCEEDED
- The retry count for the signalling path has exceeded the retry
limit. The device might still be usable. The problem can be:
- An I/O error occurred on the device.
- An incorrect COUPLExx parmlib member was specified.
- The specified COUPLExx parmlib member had signalling path definition
errors. For instance, the retry limit can be exceeded if both sides
of a signalling path were started in the same direction. See the explanation
for the message text OTHER SIDE IS SAME DIRECTION.
- The IPL of a system into a sysplex caused an ESCON® CTC device to appear non-operational.
- SYSPLEX PARTITIONING OF LOCAL SYSTEM
- The local system is no longer in the sysplex, so XCF stopped the
signalling path connected to it. If the operator used either the VARY
XCF command with RETAIN=NO or the SETXCF STOP command, the definition
of the signalling path is deleted from XCF.
- SYSPLEX PARTITIONING OF REMOTE SYSTEM
- The remote system is no longer in the sysplex, so XCF stopped
the signalling path connected to it. If the operator used either the
VARY XCF command with RETAIN=NO or the SETXCF STOP command, the definition
of the signalling path is deleted from XCF.
- OTHER SIDE IS SAME DIRECTION
- XCF tried to establish signalling connectivity between two systems,
but the signalling path was defined in the same direction on both
systems. A signalling path must have an outbound side and an inbound
side. If both sides are defined in the same directions, messages cannot
travel between the two systems involved.
Either of the two systems
involved can detect the problem; the message appears only on one system.
No response or acknowledgment is provided about this condition to
the other system involved.
- SUBCHANNEL NOT OPERATIONAL FOR RESUME
- The subchannel is not operational for one of the following reasons:
- No subchannel is provided.
- The subchannel did not have a valid device number assigned.
- The subchannel is not enabled.
- START REQUEST FAILED
- A request to start a device for use as a signalling path failed
because the device is either not suitable or not available. See message
IXC456I for an explanation of the problem.
- CONNECTED TO NON-XCF SIGNALLER
- The device on the other end of this signalling path is not defined
to XCF. Either this signalling path is not connected to a system in
the sysplex, or another application is trying to use the signalling
path. This signalling path can only be used for communication between
two systems in the sysplex.
This message can also be issued in
a circumstance where XCF is using the link. If an ESCON CTC is defined to the hardware as a BCTC
in the IOCDS, but defined to software as an SCTC, XCF will attempt
to use the CTC. The protocol understood by the hardware for the CTC
is for BCTC; therefore, the first system that tries to connect shows
status "LINKING". However, when the second system attempts to connect,
the system issues message IXC458I with the additional text CONNECTED
TO NON-XCF SIGNALLER.
- NON-XCF SIGNALLER USING PATH
- An non-XCF application tried to use this system's signalling path.
Devices used by XCF must be dedicated exclusively to XCF.
- HALT I/O FAILED
- The system tried to stop all I/O through this device, but the
request failed. The device is probably in a permanent error state.
If the device is an ESCON CTC,
IPLing another system into the sysplex might have caused the device
to stop.
- PURGE I/O FAILED
- An attempt to remove all I/O queued to this device failed.
System action
XCF stops using this device as a signalling path.
The device is left unallocated and online. XCF writes a component
trace record for the problem.
If the stop was not initiated
by the operator, the device remains defined to XCF, and is in an inoperative
state.
Note: Depending on the kind of failure, XCF may be able
to automatically restart the device.
Operator response
Depending on the message text, do one of the
following:
- SUBCHANNEL NOT OPERATIONAL FOR RESUME
- HALT I/O FAILED
- Contact hardware support.
- PURGE I/O FAILED
- Contact software support.
- OTHER SIDE SAME DIRECTION
- The direction of the signalling path direction is
wrong. Correct the error as follows:
- Enter a SETXCF STOP direction to delete the
definition of the incorrect path.
- Enter SETXCF START direction with the correct
direction.
- For other message text, notify the system programmer.
- Manually restart the path.
System programmer response
For both systems involved, do the
following:
- Make sure that the correct device number was specified.
- Make sure that the signalling path definitions in the COUPLExx
parmlib member are correct.
- Make sure that the correct COUPLExx parmlib member was specified.
- Make sure that the device is being used only by XCF.
- Look in the SYS1.LOGREC error records for I/O errors on the device.
- Ask the operator to enter DISPLAY XCF,PATHOUT,DEVICE=ALL or the
DISPLAY XCF,PATHIN,DEVICE=ALL commands on the active systems for information
on devices.
If the problem persists, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM® Support Center. Provide the
XCF component trace data, the SYS1.LOGREC error record, and the GTF
trace data for the device that has failed.
Source
Cross-system coupling facility (XCF)
Module
Routing code
Descriptor code