Explanation
The request to stop an XCF signalling path was
rejected by the system.
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 rejected 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 to be stopped for inbound signal traffic.
- PATHOUT
- Indicates the path was to be 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
was to be used to determine the direction(s) in which to stop 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.
- USE PATHOUT TO STOP OUTBOUND PATH
- The request specified PATHIN to stop an outbound signalling path.
The path can be defined for signalling in only one direction.
- USE PATHIN TO STOP INBOUND PATH
- The request specified PATHOUT to stop an inbound signalling path.
The path can be defined for signalling in only one direction.
- NOT IN USE AS OUTBOUND PATH
- The request specified PATHOUT to stop an inbound signalling path.
The path can be defined for signalling in both directions simultaneously,
but is not currently defined as an outbound path.
- NOT IN USE AS INBOUND PATH
- The request specified PATHIN to stop an outbound signalling path.
The path can be defined for signalling in both directions simultaneously,
but is not currently defined as an inbound path.
- LAST PATH TO SYSTEM
- The system will not process a SETXCF STOP command to stop the
last operational signalling path to a system, because it would cause
a loss of signalling connectivity.
- STOP ALREADY IN PROGRESS
- A stop path request for the indicated direction has already been
accepted. The request is not yet complete.
- FIRST USE STOP WITH UNCOND=NO
- The request specified UNCOND=YES, which the system does not accept
unless there is an outstanding stop request for the signalling path.
- UNKNOWN DEVICE
- The request specified a device not defined to XCF.
- SYSTEM IS IN XCF-LOCAL MODE
- The system on which the stop command was entered is running in
XCF-local mode. A system in XCF-local mode is restricted to a single
system sysplex, and cannot use XCF signalling paths for intersystem
communication.
- SYSTEM IS IN MONOPLEX MODE
- The system on which the stop command was entered is running in
MONOPLEX mode. A system in MONOPLEX mode is restricted to a single
system sysplex, and cannot use XCF signalling paths for intersystem
communication.
- UNKNOWN STRUCTURE
- The stop request specified a structure not in use by XCF.
- UNKNOWN PATH
- The stop request specified a path not in use by XCF.
- UNEXPECTED ERROR
- An unexpected error occurred. Diagnostic data is provided to help IBM® service personnel with problem
determination.
- 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.
System action
The system ignores the stop path request. Processing
continues.
Operator response
Depending on the message text, do one of the
following:
- USE PATHOUT TO STOP OUTBOUND PATH
- NOT IN USE AS INBOUND PATH
- If the path should be defined for inbound use, no action is needed.
If the path should be stopped for outbound use, enter a SETXCF STOP,PATHOUT
command.
- USE PATHIN TO STOP INBOUND PATH
- NOT IN USE AS OUTBOUND PATH
- If the path should be defined for outbound use, no action is needed.
If the path should be stopped for inbound use, enter a SETXCF STOP,PATHIN
command.
- FIRST USE STOP WITH UNCOND=NO
- Enter SETXCF STOP command without the UNCOND=YES specification
to stop the signalling path. One can specify UNCOND=NO explicitly
or omit the UNCOND specification since UNCOND=NO is the default.
- LAST PATH TO SYSTEM
- To remove the system from the sysplex, enter the VARY command.
If the system is to remain in the sysplex, start additional signalling
paths before stopping this one. Enter a DISPLAY XCF path command for
the signalling path to determine the system to which the path is connected.
- UNKNOWN DEVICE
- UNKNOWN STRUCTURE
- UNKNOWN PATH
- If the signalling path was correctly specified, it has already
been stopped and is no longer defined to XCF. No further action is
needed.
If the signalling path was not correctly specified, enter
a SETXCF STOP path command for the correct signalling path. Enter
the DISPLAY XCF,PATHIN command to list the signalling paths defined
to XCF for inbound use. Enter the DISPLAY XCF,PATHOUT command to list
the signalling paths defined to XCF for outbound use.
- UNEXPECTED ERROR
- Enter a DISPLAY XCF path command to obtain detailed information
for the signalling path. Record the display output for the path along
with any diagnostic data contained in this message in case the system
programmer must contact IBM service
personnel for problem determination. Then try entering the SETXCF
STOP path command again.
System programmer response
Examine the listed operator responses
for an appropriate action.
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 stop 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
Routing code
Descriptor code