IXC307I

Explanation
XCF successfully stopped a signalling path.
In
the message text: SETXCF STOP
An operator entered a SETXCF STOP path command.
STOP
The system initiated a stop path request in response to some event
or circumstance. System initiated stop requests do not cause paths
to become undefined to XCF for signalling, but are otherwise functionally
equivalent to SETXCF STOP path commands entered by an operator.
dir
The path direction specified for the stop request. An inbound
signalling path is used to receive signals from another system in
the sysplex. An outbound signalling path is used to send signals to
another system in the sysplex. PATHIN
Indicates the path was stopped for inbound signal traffic.
PATHOUT
Indicates the path was stopped for outbound signal traffic.
PATH
Indicates the path direction was not specified or could not be
determined. For system initiated requests, the existing XCF path definition
is used to determine the direction(s) in which to stop the path.

UNCOND=YES
UNCOND=YES was coded on the SETXCF command, indicating that the
stop was performed unconditionally.  An unconditional stop may have
abnormally terminated other tasks in the midst of processing requests
(such as a stop) for the indicated path.  An unconditional stop attempts
to force stop path processing to run to completion, and may not wait
for an orderly shutdown of the signalling path. For example, an unconditional
stop could prevent XCF from delivering a signal to its intended target.
pathname
The name of the signalling path. DEVICE dev
Indicates the CTC device with device number dev.
STRUCTURE strname
Indicates the XES list structure whose name is strname.
A list structure can contain one or more individual list signalling
paths.
STRUCTURE strname LIST num TO
COMMUNICATE WITH SYSTEM sysname
Indicates the list signalling path using list number num within
the XES list structure named strname to communicate
with the system named sysname.

RETRY LIMIT EXCEEDED
The retry count for the signalling path exceeded the retry limit.
The path is stopped because it is considered to be non-operational.
The problem can be: I/O errors occurred on the path.
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.

SYSPLEX PARTITIONING OF LOCAL SYSTEM
The path was stopped because the local system is no longer in
the sysplex.  If the local system was active in the sysplex, it enters
a wait-state upon completion of sysplex partitioning.  If the system
was attempting to IPL into a sysplex but never became active, all
paths are stopped before the operator is prompted by message IXC207A
to respecify a new COUPLExx parmlib member.
SYSPLEX PARTITIONING OF REMOTE SYSTEM
The system to which the path had last established signalling connectivity
is being removed from the sysplex. The initiator of the partitioning
request specifies whether the systems remaining in the sysplex are
to retain the signalling paths used to communicate with the removed
system. If the paths are not to be retained, this path becomes undefined
to XCF for signalling upon completion of the stop. To redefine the
path to XCF for signalling, the operator must enter a SETXCF START
path command. If the paths are to be retained after the system is
removed from the sysplex, this path remains defined to XCF for signalling.
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. However 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 signalling path failed. Message IXC305I explains
why the start request failed.
CONNECTED TO NON-XCF SIGNALLER
The other end of this signalling path is not under XCF control.
 Either the signalling path is not connected to a system in the sysplex,
or another application is trying to use the signalling path.  A signalling
path can only be used for communication between two systems active
in the same sysplex and both ends of the path must be under XCF's
exclusive control in order to ensure correct operation of the signalling
service.
NON-XCF SIGNALLER USING PATH
A non-XCF application tried to use this system's signalling path.
 Paths used by XCF must be dedicated exclusively to XCF in order to
ensure correct operation of the signalling service.
HALT I/O FAILED
The system tried to stop all I/O through this path, but the request
failed. For a CTC signalling path, The CTC device is probably in a
permanent error state.
PURGE I/O FAILED
An attempt to remove all I/O queued for the signalling path failed.
CONTROL OPERATION FAILED
XCF performs various to read and write operations to manage use
of a list structure for signalling. One of these control operations
failed.
INTERNAL ERROR
An XCF internal error occurred.
CONNECT TOKEN NO LONGER VALID
The connect token used when invoking XES services to access the
list structure is no longer valid. The connect token is returned by
the IXLCONN service.
LOST CONNECTIVITY TO STRUCTURE
This system lost connectivity to the coupling facility that contains
the structure.
STRUCTURE FAILURE
Use of the list structure for signalling is stopped due to a structure
failure.
PROPAGATING STOP OF STRUCTURE
A stop request is in progress for a list structure. All the associated
list paths must be stopped as well.
OTHER SYSTEM STOPPING ITS SIDE OF PATH
The other system to which the signalling path is connected is
stopping its side of the path. Since the path is no longer needed,
this system also stops its side of the path. For example, if a system
stops using a list structure for outbound signal traffic, all the
systems using the structure for inbound signal traffic can stop their
inbound list paths.
NO LIST AVAILABLE FOR USE
A list path no longer has a list allocated within the list structure
for it to use.  For example, a rebuilt structure may not have a list
for the list path to use, whereas the original structure did.
REBUILD FAILED, UNABLE TO USE ORIGINAL
A structure rebuild was initiated.  The rebuild attempt failed
and this system is unable to use the original list structure.
NOT DEFINED AS PATHOUT OR PATHIN
The list structure is defined for neither outbound signal traffic
nor inbound signal traffic. XCF disconnects from the structure.
UNABLE TO START LIST MONITORING
XCF was unable to start monitoring a list for from empty to non-empty.
The signalling service cannot deliver signals without the ability
to monitor list transitions. Depending on the list involved, failure
to establish monitoring may impact a particular list path or use of
the whole structure.
UNABLE TO USE REBUILT STRUCTURE
The list structure has been rebuilt, but this system cannot use
the rebuilt structure. Although this system may lose signalling capacity
by stopping its use of the list structure, it does not lose signalling
connectivity. So the other systems in the sysplex are permitted to
continue on with the rebuilt structure, and this system disconnects
from the structure.
UNABLE TO START REBUILD
The list structure is not usable.  An attempt was made to rebuild
the structure, but the rebuild could not be started.
NO SIGNALLING CONNECTIVITY
A signalling path in the midst of stop processing was unconditionally
stopped due to a lack of signalling connectivity.  The unconditional
stop forces stop processing to complete so that the path can be started
again.  It is hoped that the path will re-establish signalling connectivity
after it is started. Such an unconditional stop is performed only
if the path would remain defined to XCF upon completion of the stop
and only if the path is connected to a system running MVS/ESA SP510
(or later).
STOP STRUCTURE PROCESSING
A stop request is in progress for a list structure, so all the
associated list signalling paths must be stopped.  An unconditional
stop request was already initiated for the list path.  To ensure the
stop structure processing completes, a new unconditional stop request
is initiated for the list path.
CONNECTOR HANG RESOLUTION
A structure-related process associated with this list structure
appears to be hung because of failure to receive a connector response.
 The system has stopped signaling paths through the structure to cause
XCF to disconnect and thereby relieve the hang.
REASON UNKNOWN
XCF cannot determine why the signalling path was stopped.
DIAG039: n
Diagnostic data provided to assist IBM® service
personnel with problem determination.
DIAG040: n
Diagnostic data provided to assist IBM service
personnel with problem determination.

System action
The signalling path is not used for delivering
signals. For an operator initiated stop command, the signalling path
is no longer defined to XCF in the indicated direction(s). For a system
initiated stop request, the signalling path remains defined to XCF
in an INOPERATIVE state.  Since a list signalling path is implicitly
defined to XCF by virtue of how other systems use the list structure
for signalling, it is placed in an INOPERATIVE state only to highlight
the failure of a path that should be in use.  If the list path is
stopped as the result of normal processing, it becomes undefined.
If
the path remains defined to XCF for signalling the system may automatically
start the path again as a result of various events or circumstances.
This applies to list paths that are implicitly defined as well.

Operator response
Depending on the message text, do one of the
following: SUBCHANNEL NOT OPERATIONAL FOR RESUME
HALT I/O FAILED
PURGE I/O FAILED
Contact hardware support.
OTHER SIDE SAME DIRECTION
Correct the signalling path that is going in the wrong direction
as follows: If the path is not defined to XCF, enter a SETXCF START path command
to start the path in the correct direction.
To correct a signalling path that is still defined to XCF, enter
a SETXCF STOP path command to stop the path. Then enter a a SETXCF
START path command to start the path in the correct direction.

 If the path was stopped due to a failure, enter
a SETXCF START path command to try starting the path again. If the
problem persists, notify the system programmer.

System programmer response
For each of the systems that were
to use the signalling path: Make sure that the signalling path is correctly defined to XCF.
 The path was defined either in the COUPLExx parmlib member used to
initialize XCF, or with a SETXCF START path operator command.
Make sure that the correct COUPLExx parmlib member was specified.
Make sure that the path is being used only by XCF.
Examine the logrec error records for I/O errors related to this
path.
Examine the system log for other messages related to this path.
Ask the operator to enter DISPLAY XCF path commands to obtain
detailed status information about the signalling path.

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 XCF
component trace data, any logrec error records, and the system logs.
Provide any dump taken as the result of an internal XCF error.

Source
Cross System Coupling Facility (SCXCF)

Module
IXCT1FSP, IXCT1FSS, IXCT1PCC

Routing code
1,2

Descriptor code
5