Explanation
The signalling path was successfully started. This
means that the signalling path appears to be suitable for use. It
does not mean that the signalling path is engaged in signal delivery.
In
the message text:
- SETXCF START
- An operator entered a SETXCF START path command.
- START
- The system initiated a start path request in response to some
event or circumstance. System initiated start requests do not cause
paths to become defined to XCF for signalling, but are otherwise functionally
equivalent to SETXCF START path commands entered by an operator.
- dir
- The path direction specified for the start 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 started for inbound signal traffic.
- PATHOUT
- Indicates the path was started 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
was used to determine the direction(s) in which to start the path.
- 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.
sysname might
contain a value of nnssssss where nn is
a system number and ssssss is a system sequence
number that is assigned by XCF to system sysname.
If the start path request is being initiated when system sysname is
IPLing, it is possible that system sysname is currently
known to other systems in the sysplex by the system number and system
sequence number assigned by XCF during system initialization. When
the start path request completes and signalling connectivity is established
with system sysname, message IXC466I is written
to the system log and contains the actual name of system sysname.
- PARMLIB SPECIFICATION
- The signalling path was started because it was defined in the
COUPLExx parmlib member used to initialize XCF when the system IPLed.
- DEVICE CAME ONLINE
- The signalling path was started because the device was varied
online.
- DEVICE BECAME AVAILABLE TO MVS™
- The signalling path was started because the device became available
to the system. For example, a logical path to the device may have
been established, or the device may have become connected to a subchannel.
- DEFERRED UNTIL STOP COMPLETED
- The path was stopped before start processing could complete.
The system automatically starts the path again upon successful completion
of stop processing, provided the path remains defined to XCF for signalling
and the circumstances that caused the stop are resolved.
- PATH TO DEVICE CAME ONLINE
- The signalling path was started because a channel path to the
device was varied online.
- NEEDED SIGNALLING CONNECTIVITY
- The system lost signalling connectivity with some other system
in the sysplex. In an attempt to re-establish signalling connectivity,
the path is started.
- SYSTEM STARTED TO USE STRUCTURE
- This system detected that system sysname intends
to use the structure for signalling in the opposite direction. The
list path was started in order to establish signalling connectivity
via the list structure.
- SYSTEM SIGNALLED USE OF STRUCTURE
- This system received a signal from system sysname requesting
that signalling path(s) be started through list structure strname.
- STRUCTURE NOW AVAILABLE
- Event code 35 was presented by the Event Notification Facility
(ENF). Structure strname is available for use.
- COUPLING FACILITY RESOURCES AVAILABLE
- Event code 35 was presented by the Event Notification Facility
(ENF). New coupling facility resources are available to this system.
- DIAG037: n
- Diagnostic data provided to assist IBM® service
personnel with problem determination.
System action
The system initiates restart processing for the
signalling path.
For a CTC signalling path or a list signalling
path, restart processing attempts to establish signalling connectivity
via the path. Message IXC466 is written to the system log when the
path establishes signalling connectivity and becomes capable of transferring
signals.
For a list structure, restart processing determines
which systems are using the structure for signalling and starts or
stops list signalling paths as needed.
Operator response
None required. To determine the status of
the path, enter a DISPLAY XCF path command for the indicated path.
System programmer response
If the signalling path was not defined
to XCF at IPL time, update the COUPLExx parmlib member(s) so that
this path is defined to XCF when the system next IPLs.
Source
Cross System Coupling Facility (SCXCF)
Module
Routing code
Descriptor code