System definition mismatch: The requested function is
not supported by the receiver, or there is a mismatch between the
sending and receiving system definitions.
Bytes 2 and 3 following the sense code contain sense-code-specific
information.
- 0000
- No specific code applies.
- 0001
- The BFCLEANUP specifies that it is for an independent LU, but
the LU specified is not an independent LU. This also could be caused
by a resource mismatch.
- 0002
- The target LU is not in the same subarea as the Type 4 node.
- 0003
- The function is not supported by the target resource.
- 0004
- SLU name not valid: The network ID (if present) for the NS SLU
name field is not equal to the network ID of the Type 4 node, or the
SLU name is not equal to the LU name field in the LUB.
- 0005
- The LU address specified in the FNA is not associated with the
PU target address specified in the FNA.
- 0006
- The SSCP has no predefinition for an LU and does not support dynamic
resource definition.
VTAM® Information: When VTAM receives this sense code for
a session initiation, it continues searching through the adjacent
SSCP table until the destination LU is found or routing is exhausted.
- 0007
- The receiving SSCP has a different system-defined name for the
SSCP(DLU) than the SSCP(DLU) name in the session initiation request.
VTAM hint: In subarea,
a possible cause of this error is that the CDRM definition statement
in the OLU host for the DLU does not match what the DLU has coded
for SSCPNAME in the VTAM start
options.
- 0008
- In a gateway with three gateway SSCPs, a gateway SSCP on the OLU
side of the gateway was specified as having predesignated control
in the CDINIT. In this configuration, only the middle gateway SSCP
may have predesignated control.
VTAM Information: When VTAM receives this sense code for
a session initiation, it continues searching through the adjacent
SSCP table until the destination LU is found or routing is exhausted.
- 0009
- In a gateway with multiple gateway SSCPs, the gateway node assumes
that one gateway is coded with GWCTL=ONLY. As a result, the gateway
node receives gateway-control RUs from a different SSCP than the one
it expects.
VTAM Information: When VTAM receives this sense code for
a session initiation, it continues searching through the adjacent
SSCP table until the destination LU is found or routing is exhausted.
VTAM hint: A possible cause
of this error is that the GWPATH definition specifies the wrong NCP
name.
- 000A
- The PU of an independent PLU named in BFINIT does not have the
same element address as the one in the ALS field of BFINIT.
- 000B
- An SSCP has detected a specification of gateway responsibility
in the CDINIT request that is not consistent with its own definition.
For example, an SSCP that has predesignated responsibility to control
a gateway node specified in the CDINIT request sends this sense data
when it receives the CDINIT from a session partner and the CDINIT
indicates that the session partner also has predesignated responsibility
for the gateway node; in this situation, a mismatch exists in the
responsibilities of the SSCPs, because both cannot simultaneously
have predesignated responsibility for the gateway node.
VTAM Information: When VTAM receives this sense code for
a session initiation, it continues searching through the adjacent
SSCP table until the destination LU is found or routing is exhausted.
- 000C
- The receiver is unable to interpret the DLU name.
- 000D
- Resource type not defined in receiver.
- 000F
- A gateway node has received route data for a cross-network session
in a form that it does not support.
- 0010
- An adjacent SSCP has the same SSCP name as the SSCP that owns
the DLU but a different network identifier than the DLU.
- 0011
- The subsystem LU received CINIT with an appended LU definition
(X'2F') control vector, but cannot process that control vector.
- 0012
- The receiving SSCP has a different system-defined name for the
SSCP(OLU) than the SSCP(OLU) name in the session initiation request.
- 0013
- The session request (CDINIT) has routed back to the SSCP(OLU)
or an SSCP on the session setup path has the same name as the SSCP(OLU).
- 0014
- The MOSS automatic IPL/dump switches are not set properly.
- 0015
- The OLU is represented using a dynamically defined resource but
the ALS selected to provide its services does not permit dynamic definitions.
The condition is detected when a session initiation request is received
for an independent LU and no predefinition is found for the OLU resource.
The session initiation is rejected.
VTAM hint: This sense code can be received
when an unintended DYNLU value has been assigned to the PU that represents
a link to an adjacent node. Only one DYNLU value can be associated
with an adjacent node; the source of that value can be confusing.
The DYNLU value is associated with an adjacent node when the first
link to that adjacent node is activated. When the DYNLU value is
associated with the adjacent node, that value is propagated to all
links to that adjacent node when those links are activated. To determine
the source of the DYNLU value for an adjacent node, search the message
log prior to the receipt of this sense code for the unsolicited message
IST2180I that contains the CP name of the adjacent node. See message IST2180I in z/OS Communications Server: SNA Messages for an explanation of this message. See the DYNLU combinations table in z/OS Communications Server: SNA Resource Definition
Reference for more information about determining the
source of the DYNLU value assigned to an adjacent CP and attached
resources.
- 0016
- The DLU is represented using a dynamically defined resource but
the ALS selected to provide its services does not permit dynamic definitions.
The condition is detected when a session initiation request is being
processed for an independent destination LU and no predefinition is
found for the DLU resource. The session initiation request is rejected.
VTAM hint: This
sense code can be received when an unintended DYNLU value has been
assigned to the PU that represents a link to an adjacent node. Only
one DYNLU value can be associated with an adjacent node; the source
of that value can be confusing. The DYNLU value is associated with
an adjacent node when the first link to that adjacent node is activated.
When the DYNLU value is associated with the adjacent node, that value
is propagated to all links to that adjacent node when those links
are activated. To determine the source of the DYNLU value for an
adjacent node, search the message log prior to the receipt of this
sense code for the unsolicited message IST2180I that contains the
CP name of the adjacent node. See message IST2180I in z/OS Communications Server: SNA Messages for an explanation of this message. See the DYNLU combinations table in z/OS Communications Server: SNA Resource Definition
Reference for more information about determining the
source of the DYNLU value assigned to an adjacent CP and attached
resources.
- 0017
- The request was received for an independent LU over a specific
ALS but that ALS is not defined to provide services for the subject
LU. The condition is detected when a session initiation request is
received and the ALS for which the request was received was not predefined
to provide service for that independent LU. The session initiation
request is rejected.
- 0018
- Session Initiation Status Not Supported: A session initiation
request was received that contained a session initiation status field
that was not valid for the receiving node.
- 0019
- The SSCP has received a CONTACTED or REQCONT containing an XID3
carrying an unrecognized CP name; the SSCP supports only predefined
CP names.
- 001A
- The source or destination service access point address (SSAP or
DSAP) in the logical link control protocol data unit of the XID information
field for a token-ring LAN is unknown.