Explanation
An operator entered a SETXCF MODIFY command to
modify a signalling path or a LOCALMSG parameter, but the command
was rejected by the system.
In the message text:
- dir
- The path direction specified for the rejected modify command.
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 that the inbound path definition was to be modified.
- PATHOUT
- Indicates that the outbound path definition was to be modified.
- PATH
- Indicates the path direction was not specified or could not be
determined.
- 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.
- classname
- The name of a transport class.
- minimum
- Minimum length of maxmsg.
- FOR pathname REJECTED: USE PATHOUT TO MODIFY
OUTBOUND PATH
- The request specified PATHIN to modify an outbound signalling
path. The path can be defined for signalling in only one direction.
- FOR pathname REJECTED: USE PATHIN TO MODIFY
INBOUND PATH
- The request specified PATHOUT to modify an inbound signalling
path. The path can be defined for signalling in only one direction.
- FOR pathname REJECTED: NOT IN USE AS OUTBOUND
PATH
- The request specified PATHOUT to modify an inbound signalling
path. The path can be defined for signalling in both directions simultaneously,
but is not currently defined as an outbound path.
- FOR pathname REJECTED: NOT IN USE AS INBOUND
PATH
- The request specified PATHIN to modify an outbound signalling
path. The path can be defined for signalling in both directions simultaneously,
but is not currently defined as an inbound path.
- FOR pathname REJECTED: PATH STOPPED
- The SETXCF MODIFY command was entered for a signalling path that
was being stopped.
- FOR pathname REJECTED: UNKNOWN DEVICE
- The SETXCF MODIFY command specified a device not in use by XCF.
- FOR pathname REJECTED: SYSTEM IS IN XCF-LOCAL
MODE
- The system on which the modify 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.
- FOR pathname REJECTED: SYSTEM IS IN MONOPLEX
MODE
- The system on which the modify 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.
- FOR pathname REJECTED: UNKNOWN STRUCTURE
- The SETXCF MODIFY command specified a structure not in use by
XCF.
- FOR pathname REJECTED: UNEXPECTED ERROR
- An unexpected error occurred. Diagnostic data is provided to help IBM® service personnel with problem
determination.
- FOR pathname REJECTED: UNKNOWN PATH
- The MODIFY command specified a path not in use by XCF.
- FOR pathname REJECTED: DIAG037=n
- Diagnostic data that is provided to assist IBM service personnel with problem determination.
- FOR pathname REJECTED: DIAG074=n
- Diagnostic data that is provided to assist IBM service personnel with problem determination.
- FOR pathname REJECTED: RC,RSN=n n
- Diagnostic data that is provided to assist IBM service personnel with problem determination.
- FOR pathname REJECTED: TRANSPORT CLASS classname NOT
DEFINED
- The operator entered a SETXCF MODIFY command to modify an outbound
signalling path, but the transport class name, classname,
is not defined to the system.
- FOR pathname REJECTED: MAXMSG MUST BE AT LEAST minimum
- The MAXMSG specified on the SETXCF MODIFY command was not large
enough for the 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 modify a signalling path in the indicated transport
class, the MAXMSG value must be greater than or equal to minimum.
- REJECTED: TRANSPORT CLASS classname NOT DEFINED
- The operator entered a SETXCF MODIFY command to modify an outbound
signalling path, but the transport class name, classname,
is not defined to the system.
- REJECTED: MAXMSG MUST BE AT LEAST minimum
- The MAXMSG specified on the MODIFY command was not large enough
for the transport class.
The MAXMSG value for any outbound signalling
path or LOCALMSG parameter 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 or LOCALMSG parameter is assigned.
To modify a signalling path or LOCALMSG parameter, the MAXMSG value
must be greater than or equal to minimum.
System action
The system ignores the modify command. Processing
continues.
Operator response
Depending on the message text, do one of the
following:
- USE PATHOUT TO MODIFY OUTBOUND PATH
- NOT IN USE AS INBOUND PATH
- Enter the SETXCF MODIFY,PATHOUT command to modify the outbound
path definition.
- USE PATHIN TO MODIFY INBOUND PATH
- NOT IN USE AS OUTBOUND PATH
- Enter the SETXCF MODIFY,PATHIN command to modify the inbound path
definition.
- UNKNOWN DEVICE
- UNKNOWN STRUCTURE
- UNKNOWN PATH
- If the signalling path was not correctly specified, enter a SETXCF
MODIFY 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 the DISPLAY XCF specifying the indicated signalling path
or LOCALMSG as appropriate to get detailed information concerning
the indicated object. Note that information will only be displayed
if the object is defined to XCF for signalling. Enter the SETXCF MODIFY
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 object is defined to XCF for signalling, as well as
any diagnostic data presented as part of this modify rejected message.
- TRANSPORT CLASS classname NOT DEFINED
- The transport class must be defined to XCF before any signalling
paths or LOCALMSG parameters can be assigned to 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 MODIFY command with a valid transport class name.
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 modify rejected message, any output from
the DISPLAY XCF command issued for the object, 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