Explanation
The request to start an XCF signalling path was
rejected by the system.
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 rejected 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 to be started for inbound signal traffic.
- PATHOUT
- Indicates the path was to be 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 to be 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. The list number
is zero if the path was not yet assigned a list within the structure,
or if the initiator of the request could not determine which list
was assigned for the path.
- classnm
- The name of the transport class.
- minimum
- The minimum value for the MAXMSG specification.
- PATH ALREADY STARTED AS OUTBOUND
- The path is already defined to XCF for signalling in the outbound
direction.
If the START command specified PATHOUT, the indicated
path was already started for outbound signal traffic. In the case
of a list structure, there was no need to start or restart any list
paths.
If the START command specified PATHIN, the signalling
path cannot be used in different directions by the same system.
- PATH ALREADY STARTED AS INBOUND
- The path is already defined to XCF for signalling in the inbound
direction.
If the START command specified PATHIN, the indicated
path was already started for inbound signal traffic. In the case of
a list structure, there was no need to start or restart any list paths.
If
the START command specified PATHOUT, the signalling path cannot be
used in different directions by the same system.
- PATH START IN PROGRESS
- The path is already defined to XCF for signalling in the requested
direction. The path is in the midst of start processing.
- SYSTEM IS IN XCF-LOCAL MODE
- The system on which the START command was entered is running in
XCF-local mode. A system in XCF-local mode is restricted to a single
system sysplex, and has no need to use XCF signalling paths for intersystem
communication.
- PATH STOP IN PROGRESS
- The path is already defined to XCF for signalling in the requested
direction. The path is in the midst of stop processing. The signalling
path cannot be started until stop processing completes.
- PATH IS RUNNING
- The path is already defined to XCF for signalling in the requested
direction. The path is either in the midst of attempting to establish
signalling connectivity, or has already done so.
- SYSTEM IS IN MONOPLEX MODE
- The system where the start command was entered is running in MONOPLEX
mode. A system in MONOPLEX mode is restricted to a single system sysplex,
and has no need to use XCF signalling paths for intersystem communication.
- UNEXPECTED ERROR
- An unexpected error occurred. Diagnostic data is provided to help IBM® service personnel with problem
determination.
- NOT DEFINED TO XCF
- A system initiated start request was made for a path that is not
currently defined to XCF for signalling. A system initiated start
request is not permitted to define a new path to XCF for signalling.
Paths are defined for signalling via the COUPLExx parmlib member or
as a result of a SETXCF START path operator command.
- IGNORING EXPECTED EVENT
- An event occurred that caused the system to initiate a start path
request. However, this event was generated as a result of normal processing
performed for the signalling path. XCF rejects the start request initiated
as a result of this expected event.
- INTERVENTION REQUIRED
- The signalling path is currently inoperative. XCF will automatically
start the signalling path once it receives notification that the circumstances
that caused the path to be placed in the inoperative state are resolved.
This start request is rejected because it was not made as a result
of such a resolution. For example, a start request initiated to resolve
a loss of signalling connectivity would be rejected for a CTC signalling
path placed in an inoperative state because the device is not online.
- STRUCTURE NOT DEFINED FOR PATHOUT
- The start of the outbound list path is rejected because the indicated
XES list structure is no longer defined to XCF for outbound use. Between
the time that the start list path request was created and the time
it was processed, the associated list structure was stopped in the
outbound direction.
- STRUCTURE NOT DEFINED FOR PATHIN
- The start of the inbound list path is rejected because the indicated
XES list structure is no longer defined to XCF for inbound use. Between
the time that the start list path request was created and the time
it was processed, the associated list structure was stopped in the
inbound direction.
- STOP PATHOUT FOR STRUCTURE IN PROGRESS
- The start of the outbound list path is rejected because the indicated
XES list structure is in the midst of being stopped for outbound use.
Between the time that the start list path request was created and
the time it was processed, the associated list structure was stopped
in the outbound direction.
- STOP PATHIN FOR STRUCTURE IN PROGRESS
- The start of the inbound list path is rejected because the indicated
XES list structure is in the midst of being stopped for inbound use.
Between the time that the start list path request was created and
the time it was processed, the associated list structure was stopped
in the inbound direction.
- STRUCTURE INOPERATIVE FOR PATHOUT
- The start of the outbound list path is rejected because the indicated
XES list structure has been stopped in the outbound direction. Between
the time that the start list path request was created and the time
it was processed, the associated list structure was stopped in the
outbound direction.
- STRUCTURE INOPERATIVE FOR PATHIN
- The start of the inbound list path is rejected because the indicated
XES list structure has been stopped in the inbound direction. Between
the time that the start list path request was created and the time
it was processed, the associated list structure was stopped in the
inbound direction.
- STRUCTURE NAME MUST BEGIN WITH LETTERS IXC
- The start request for the list structure is rejected because the
name of the structure does not begin with the characters 'IXC'. Any
list structure to be used by XCF for signalling must have a name that
begins with the letters IXC. This convention is intended to help
prevent the XCF signalling service from connecting to a XES structure
used by some other application as a result of a typographical error
on a start request..
- DIAG037=n
- Diagnostic data that is provided to assist IBM service personnel with problem determination.
- DIAG074=n
- Diagnostic data that is provided to assist IBM service personnel with problem determination.
- RC,RSN=n n
- Diagnostic data that is provided to assist IBM service personnel with problem determination.
- TRANSPORT CLASS classnm NOT DEFINED
- The operator entered a start command to start an outbound signalling
path, but the transport class name, classname,
is not defined to the system.
- MAXMSG MUST BE AT LEAST minimum
- The MAXMSG value specified on the start command was not large
enough for messages in the indicated transport class.
The MAXMSG
value for any outbound signalling path must provide enough message
buffer space for at least one message as long as the class length
for the transport class to which the signalling path is assigned.
If the CLASS keyword was not explicitly coded, the signalling path
was assigned to the default transport class. To start a signalling
path in the indicated transport class, the MAXMSG value must be greater
than or equal to minimum.
System action
The system ignores the start path request. The
requested path does not become defined to XCF for signalling. Processing
continues.
A system initiated start request for a path that
is already defined to XCF may be preserved for future processing even
though the start request is initially rejected. For example, a signalling
path could be in the midst of stop processing as a result of some
hardware failure. If the hardware failure was resolved before completion
of stop path processing, a system initiated start path request would
be rejected due to 'PATH STOP IN PROGRESS'. However, the start path
request is preserved and reissued upon completion of stop path processing
(provided that the path remains defined to XCF for signalling).
Operator response
Depending on the message text, do one of the
following:
- PATH ALREADY STARTED AS OUTBOUND
- If the signalling path should be outbound, no action is needed.
If
PATHIN was specified on the START command, the path cannot be used
in different directions by the same system. If the signalling path
should be used exclusively for inbound signal traffic, enter a SETXCF
STOP,PATHOUT command to stop the signalling path. After the stop completes
successfully, enter a SETXCF START,PATHIN command to start the signalling
path in the inbound direction.
- PATH ALREADY STARTED AS INBOUND
- If the signalling path should be inbound, no action is needed.
If
PATHOUT was specified on the START command, the path cannot be used
in different directions by the same system. If the signalling path
should be used exclusively for outbound signal traffic, enter a SETXCF
STOP,PATHIN command to stop the signalling path. After the stop completes
successfully, enter a SETXCF START,PATHOUT command to start the signalling
path in the outbound direction.
- PATH STOP IN PROGRESS
- Enter the SETXCF START path command after stop processing for
the path has completed. Either message IXC307I or message IXC308I
is issued when the stop path request is complete (although the message
may appear only in the system log). Enter a DISPLAY XCF,dir command
specifying the indicated path to determine the state of the signalling
path. If message IXC356I indicates that the status of the signalling
path is INOPERATIVE, or if the path is not found, stop processing
completed.
- UNEXPECTED ERROR
- Enter the DISPLAY XCF,dir specifying the indicated
signalling path to get detailed information concerning the indicated
path. Note that information will only be displayed if the path is
defined to XCF for signalling. Enter the SETXCF START command again.
If the command continues to be rejected with this response, inform
the system programmer. Provide the result of the DISPLAY XCF command
if the path was defined to XCF for signalling, as well as any diagnostic
data presented as part of this start rejected message.
- STRUCTURE NAME MUST BEGIN WITH LETTERS IXC
- Enter the SETXCF START,STRUCTURE command specifying a structure
name to be used by the XCF signalling service. Any structure name
defined by the system programmer for signalling must begin with the
characters IXC.
- TRANSPORT CLASS classname NOT DEFINED
- The transport class must be defined to XCF before any signalling
paths can be started in that class. Enter the DISPLAY XCF,CLASSDEF
command to obtain a list of the transport classes currently defined
to the system. If needed, use the SETXCF START,CLASSDEF command to
define the transport class. Then enter the SETXCF START,PATHOUT command
with a valid transport class name.
- MAXMSG MUST BE AT LEAST minimum
- There is a mismatch between the MAXMSG value specified for the
signalling path and the class length defined for the transport class
to which the path was to be assigned. If a transport class was not
specified, the transport class named DEFAULT was assumed. Either the
MAXMSG value should be increased, the class length for the transport
class should be decreased, or the path should be assigned to a different
transport class. Consult the system programmer as needed to determine
which action is appropriate.
If the MAXMSG value should be increased,
enter the SETXCF START,PATHOUT command with a MAXMSG value that is
greater than or equal to minimum. Note that the
MAXMSG value chosen by the system programmer usually exceeds the indicated minimum value
in order to ensure reasonable performance for signal delivery. If
the transport class definition should be changed, enter a SETXCF MODIFY,CLASSDEF
command to change the class length of the transport class. If the
path should be assigned to a different transport class, enter the
SETXCF START,PATHOUT command with the appropriate transport class
specified.
For any other
text, no action
is needed.
System programmer response
Examine the listed operator responses
for an appropriate action.
Ensure that the path is defined to
the XCF signalling service correctly. Verify that the direction and
the MAXMSG value are correctly specified. For an outbound path, verify
that the transport class is correctly specified and that the transport
class definition is consistent with the path definition.
In
the case of an UNEXPECTED ERROR, search problem
reporting data bases for a fix for the problem. If no fix exists,
contact the IBM Support Center.
Supply any diagnostic data presented as part of the start rejected
message, any output from the DISPLAY XCF command issued for the signalling
path, and the XCF component trace table. The trace table must be obtained
within 30 seconds of completion of the command if XCF detail tracing
is enabled, and within a few minutes if just XCF default tracing is
in effect. Default tracing is sufficient to resolve this problem.
Source
Cross System Coupling Facility (SCXCF)
Module
IXCT1FSR, IXCT1FSS, IXCT1MOD
Routing code
Descriptor code