- 8001
- Intermediate Node Failure: Machine or program check in a node providing intermediate
routing function. A response may or may not be possible.
- 8002
- Link Failure: Data link failure.
- 8003
- NAU Inoperative: The NAU is unable to process requests or responses; for example, the
NAU has been disrupted by an abnormal termination.
Bytes 2 and 3 following the sense
code contain sense code specific information. Settings allowed are:
- 0000
- No specific code applies.
- 0001
- Hierarchical Reset: The identified LU-LU session is being deactivated; an
ACTLU/ACTPU(Cold) or DACTLU/DACTPU was received, or the PU has failed.
- 0003
- Unrecoverable LU Failure: The identified LU-LU session had to be deactivated because of
an abnormal termination of the PLU or SLU; recovery from the failure was not possible.
- 0004
- Recoverable LU Failure: The identified LU-LU session had to be deactivated because of an
abnormal termination of one of the LUs of the session; recovery from the failure may be
possible.
- 0005
- Hierarchical Reset: Backup session reset resulted from a hierarchical reset.
- 8004
- Unrecognized Destination: A node in the path has no routing information for the
destination specified either by the SLU name in a BIND request or by the TH.
Bytes 2
and 3 following the sense code contain sense code specific information. Settings allowed
are:
- 0000
- No specific code applies.
- 0001
- A request was received by a gateway function that could not be rerouted because of
invalid or incomplete routing information.
- 8005
- No Session: No half-session is active in the receiving end node for the indicated
origination-destination pair, or no boundary function session connector is active for the
origin-destination pair in a node providing the boundary function. A session activation
request is needed.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
- 0000
- No specific code applies.
- 0001
- The receiver received a request other than session control request when no LU-LU session
was active.
- 0002
- The receiver received a request other than session control request when no LU-SSCP
session was active.
- 0003
- The receiver received a session control request other than BIND/UNBIND when no LU-LU
session was active.
- 0004
- The receiver received an UNBIND when no LU-LU session was active.
- 0005
- The receiver received a session control request other than ACTLU/DACTLU for the LU-SSCP
session when no LU-SSCP session was active.
- 0006
- The receiver received DACTLU when no LU-SSCP session was active.
- 0007
- Session Not Activated: A BIND was received for a dependent LU that has not received an
ACTLU to activate the SSCP-LU session.
- 8006
- Invalid FID: Invalid FID for the receiving node.
- 8007
- Segmenting Error: First BIU segment had less than 10 bytes; or Mapping field sequencing
error, such as first, last, middle; or segmenting not supported and Mapping field not set
to BBIU, EBIU; or (in APPN) an expedited request or response was received segmented (see
Note 2 located at the end of this section).
Bytes 2 and 3 following the sense code
contain sense code specific information. Settings allowed are:
- 0000
- No specific code applies.
- 0001
- The node does not support receipt of segments, and a Mapping field value other than
BBIU, EBIU was received. Sent in UNBIND.
- 0002
- Interleaved BIND Segments Not Allowed: A BIND receiver that is in the middle of
receiving segments of one BIND receives a segment from a different BIND; the receiver
rejects both BINDs and disconnects the link.
- 8008
- PU Not Active: The SSCP-PU secondary half-session in the receiving node has not been
activated and the request was not ACTPU for this half-session; for example, the request
was ACTLU from an SSCP that does not have an active SSCP-PU session with the PU associated
with the addressed LU.
Bytes 2 and 3 following the sense code contain sense code
specific information. Settings allowed are:
- 0000
- No specific code applies.
- 0001
- A physical unit name was specified for an independent LU session stage. The specified PU
name is either unknown or in an invalid state.
- 0002
- NO ALS is defined for use by the origin independent LU. An implementation-defined
automatic logon (autolog) request was specified for the subject resource, but, when the
session establishment was attempted, no ALS was found to be associated with the subject
resource.
- 8009
- LU Not Active: The destination address specifies an LU for which the SSCP-LU secondary
half-session has not been activated and the request was not ACTLU.
- 800A
- Too-Long PIU: Transmission was truncated by a receiving node because the PIU exceeded a
maximum length or sufficient buffering was not available.
Bytes 2 and 3 following the
sense code contain sense code specific information. Settings allowed are:
- 0000
- No specific code applies.
- 0001
- A received PIU exceeded 255 buffers.
- 0002
- The node signaling this error on an EXR is including additional information in an EXR
extension.
- 800B
- Incomplete TH: Transmission received was shorter than a TH (see Note 1 located at the
end of this section).
- 800C
- DCF Error: Data Count field inconsistent with transmission length.
- 800D
- Lost Contact: Contact with the link station for which the transmission was intended has
been lost, but the link has not failed. If the difference between link failure and loss of
contact is not detectable, link failure (X'8002') is sent.
- 800E
- Unrecognized Origin: The origin address specified in the TH was not recognized.
- 800F
- Invalid Address Combination.
Bytes 2 and 3 following the sense code contain sense
code specific information. Settings allowed are:
- 0000
- The (DAF', OAF') (FID2) combination or the LSID (FID3) specified an invalid type of
session, for example, a PU-LU combination.
- 0001
- The FID2 ODAI setting in a received BIND is incorrect; the BIND is rejected.
- 8010
- Segmented RU Length Error: An RU was found to exceed a maximum length, or required
buffer allocation that might cause future buffer depletion.
- 8011
- ER Inoperative or Undefined: A PIU was received from a subarea node that does not
support ER and VR protocols, and the explicit route to the destination is inoperative or
undefined.
- 8012
- Subarea PU Not Active or Invalid Virtual Route: A session-activation request for a
peripheral PU or LU cannot be satisfied because there is no active SSCP-PU session for the
subarea node providing boundary function support, or the virtual route for the specified
SSCP-PU (type 1 or type 2 nodes) or SSCP-LU session is not the same as that used for the
SSCP-PU session of the type 1 or type 2 node's PU or the LU's subarea PU.
- 8013
- Route Not Available: No route is available to connect the specified OSA and DSA for the
specified COS.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
Byte 2 indicates the environment in which the failure was detected:
- 00
- Single network
- 01
- Interconnected network: Failure was detected at a node in a subnetwork other than that
of the NAU sending the activation request.
Byte 3 indicates the reason for the failure:
- 00
- No Specific Code Applies: This means an error occurred, but none of the conditions
listed below applies.
- 01
- No Mapping Specified: A session-activation request cannot be satisfied because for each
VR in the VR identifier list for the session, no VR to ER mapping is specified.
- 02
- No Explicit Routes Defined: A session-activation request cannot be satisfied because
each VR in the VR identifier list for the session maps to a corresponding ER that is not
defined.
- 03
- No VR Resource Available: A session-activation request cannot be satisfied because each
VR specified in the VR identifier list for the session requires a node resource that is
not available.
- 04
- No Explicit Routes Operative: A session-activation request cannot be satisfied because
no underlying ER is operative for any VR specified in the VR identifier list for the
session.
- 05
- No Explicit Route Can Be Activated: A session-activation request cannot be satisfied
because no VR specified in the VR identifier list for the session mapped to a defined and
operative ER that could be activated.
- 06
- No Virtual Route Can Be Activated: A session-activation request cannot be satisfied
because no VR specified in the VR identifier list for the session can be activated by the
PU, though for at least one VR an underlying ER is defined, operative, and activated.
- 07
- No Virtual Route Identifier List Available: A session-activation request cannot be
satisfied because a VR identifier list is not available.
Note: If none of the virtual routes specified in the VR identifier list for the
session is active or can be activated, the reported reason is set based on a hierarchy of
failure events. The "highest" of the failures that occurred within the set of
virtual routes is returned on the response. For example, if the VR manager receives a
negative response to an NC_ACTVR request for a VR specified in the VR identifier list and
for all other VRs in the list no VR to ER mapping is specified, then reason X'06' is
reported. The hierarchy of the failure reasons is in ascending numeric order, that is,
reason X'02' is higher than reason X'01'.
- 8014
- No Path Exists to the Destination Node: Route selection services in the CP has
determined from the topology database that no path exists to the destination node.
Bytes
2 and 3 following the sense code contain sense code specific information. Settings allowed
are:
- 0000
- No specific code applies.
- 0001
- No route to the destination node exists for the specified class of service.
* 0002 - Invalid APPN COS name received.
- 0003
- The topology database indicates that the destination node is not available at this time;
the node either has inconsistent data or is quiescing.
- 0004
- The topology database indicates that the endpoint resources are depleted; the node is
out of either half-session control blocks or message buffers.
- 0005
- The length of the generated RSCV exceeds the maximum allowed.
- 0006
- No path using only HPR TGs exists to the destination node.
- 0007
- A BIND RSCV specifies only an interchange TG.
- 0008
- The local node calculated an RSCV specifying a boundary node that it does not own.
- 8015
- Path Not Available.
Bytes 2 and 3 following the sense code contain sense code
specific information. Settings allowed are:
- 0000
- No specific code applies.
- 8017
- PIU from Adjacent Pre-ER-VR Subarea Node Rejected: A PIU that requires intermediate
path-control routing was received by a subarea node from an adjacent subarea node that
does not support ER-VR protocols, but the receiving subarea node does not support
intermediate path-control routing for adjacent subarea nodes that do not support ER-VR
protocols.
- 8018
- Management Services component is unable to find or recognize the name of the application
transaction program specified in the request.
Bytes 2 and 3 following the sense code
contain sense code specific information. Settings allowed are:
- 0000
- No specific code applies.
- 0001
- The application transaction program specified in the request is not recognized by PUMS.
- 0002
- The Cascaded Resource Name List is unrecognized.
- 0003
- The Destination Application Name is unrecognized.
- 0004
- The Destination Instance Identifier is unrecognized.
- 8019
- Routing Exception: A node is unable to perform the required routing function for a
request.
Bytes 2 and 3 following the sense code contain sense code specific
information. Settings allowed are:
- 0000
- No specific code applies.
- 0001
- Unknown Routing Group Name.
- 0002
- Unknown Routing Group Name, Routing Element Name combination.
- 0003
- Reserved
- 0004
- No connection is available for level of service required. When this SNA report code is
used in an SNA condition report, it is accompanied by a supplemental report containing the
service parameter triplet (or combination of triplets) for which a connection could not be
found.
- 0005
- The Routing and Targeting Instructions GDS variable is required but is not present.
- 000C
- Upon receiving a Locate request for a DLUS-served dependent LU, the DLUS node has
determined that at least one intersubnetwork TG on the path between the DLUS and the PLU
was not between two extended border nodes.
- 801A
- Confirmation of Forwarding
- 0001
- The identified request has been successfully forwarded by the reporting node. When this
SNA report code is used within an SNA condition report, the reported-on destination list
identifies the list of destinations to which the request has been forwarded.
- 801B
- Confirmation of Acceptance
- 0001
- The identified request has been successfully received by the intended destination(s) at
the reporting node. When this SNA report code is used within an SNA condition report, the
reported on destination list identifies the list of destinations for which the request has
been accepted.
- 801C
- Hop Count Exhausted
- 0001
- The request has been forwarded by an excessive number of nodes (e.g., the count has been
decremented at each node and has reached 0) and, therefore, the request could not be
delivered to one or more destinations. Typically, this exception indicates that one or
more nodes have incorrectly routed or directed the request. The exception may also
indicate that the routing/directing count was not appropriately initiated according to
network size.
- 801E
- Invalid Switching Mode: The Switching Mode field received in a network header was
invalid or not supported by the receiving node.
- 801F
- Invalid Link Header: The link header in the received frame was not valid for the current
state of the receiver.
Bytes 2 and 3 following the sense code contain sense code
specific information. Settings allowed are:
- 0000
- No specific code applies.
- 0001
- A frame in the supervisory or information format was received over a TG configured for
no error recovery.
- 8020
- Session Reset: The LU-LU session identified in the UNBIND is being deactivated because
of a reset condition.
Bytes 2 and 3 following the sense code contain sense code
specific information. Settings allowed are:
- 0000
- No specific code applies.
- 0001
- Virtual Route Inoperative: The virtual route used by the LU-LU session has become
inoperative, thus forcing the deactivation of the identifed LU-LU session.
- 0002
- Hierarchical Reset of Both XRF-active and XRF-backup Sessions: The XRF-backup session
has failed; therefore, both the XRF-active and XRF-backup session are being reset.
- 0003
- Virtual Route Deactivated: The identified LU-LU session had to be deactivated because of
a forced deactivation of the virtual route being used by the LU-LU session.
- 0004
- Route Extension Failure: The route extension used by the LU-LU session has become
inoperative, thus forcing the deactivation of the identified LU-LU session.
- 0005
- Route Extension Failure: The route extension used by the XRF-backup LU-LU session has
become inoperative, thus forcing the deactivation of the identified XRF-backup LU-LU
session.
- 0006
- Virtual Route Inoperative: The virtual route used by the LU-LU session has become
inoperative, thus forcing the deactivation via VR-INOP of the identifed XRF-backup LU-LU
session.
- 0007
- Third-Party Termination: The network operator caused the forced or cleanup termination
of the LU-LU session.
- 0008
- BFTERM has been received with no indication of the cause of the reset.
- 0009
- Termination was requested by the dependent SLU with a TERMINATE SELF or character-coded
logoff.
- 000A
- The identified LU-LU session had to be deactivated because its underlying RTP connection
has become inoperative.
- 000B
- The identified LU-LU session had to be deactivated because its underlying RTP connection
was deactivated.
- 8021
- Path Switch Failure: The attempt to switch the path traversed by an RTP connection has
failed.
Bytes 2 and 3 following the sense code contain sense code specific information.
Settings allowed are:
- 0000
- No specific code applies.
- 0001
- The original path of the RTP connection is inoperative. Because the path switch failed,
all sessions using the RTP connection will be terminated.
- 0002
- The original path of the RTP connection is still operative. The RTP connection will
continue operation over the original path.