"SNA Formats 08" via IBM BookManager BookServer

Request Reject (Category Code = X'08')

This category indicates that the request was delivered to the intended component and was understood and supported, but not executed.

Category and modifier (in hexadecimal):

0801

Resource Not Available: The LU, PU, link station, or link specified in an RU is not available.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Independent LU Does Not Receive ACTLU: An ACTLU has been sent by the SSCP to an independent LU (sent by BF).
0002: Reserved Resources Requested for Sessions Exceed Allowable Maximum: The resource reservation request in RNAA exceeds the maximum allowed by system definition. The address was not assigned and no change was made to the current reservation of resources for the LU.
0003: Name aliasing cannot be performed because the name alias function is not available.
0004: A switched connection currently exists for the link being activated, and the SSCP or the subarea PU does not support the protocols necessary to allow take-over of such a link.
0005: A SETCV has been received for a resource that is still represented in the pool of available control blocks.
0006: The line is not associated with a line adapter, or is associated with a line adapter that is not valid for the usage tier specified in the receiving node's system definition.
0007: The line is associated with a line adapter that is not installed or not attached to a communications processor.
0008: The line is associated with a line adapter that is inoperative.
0009: The LU is not available because it is not ready to accept sessions.
000A: The PLU is not available because it is being taken down, and is therefore not accepting new sessions. The initiation request should not be retried.
000B: The PLU is not available because it is unable to comply with the PLU-SLU role specification.
000C: The SLU is not available because it is unable to comply with the PLU-SLU role specification.
000D: The LU is not available because its SSCP is in the process of being taken down, and is therefore not allowing new sessions to be started. The initiation request should not be retried.
000E: The LU is not available because an intermediate gateway SSCP is in the process of being taken down, and is therefore not allowing new sessions to be started.
000F: The SLU is not available because it is being taken down, and is therefore not accepting new sessions. The initiation request should not be retried.
0010: Switched subarea connection cannot be established because no switched subarea links have been defined.
0011: Switched subarea connection to another network cannot be established because no switched subarea links have been defined within the gateway PU.
0012: An APPN connection cannot be established because this node has no available integers to represent a new TG.
0013: A switched connection cannot be established because no short-hold mode capable link is defined.
0014: A switched connection cannot be established. Call Request Verification was requested, but is not supported for this configuration. This condition will result from conflicting system definition.
0015: The link connection is unavailable as a result of a hardware failure within the line adapter.
0016: A link resource is not available as a result of maintenance occurring on the supporting hardware.
0017: A link resource is not available because a mismatch exists within the microcode of the supporting hardware.
0018: Activation of the channel link failed because the supporting hardware is undergoing error recovery.
0019: Activation of the channel link failed because the supporting hardware is undergoing concurrent maintenance.
001A-001E: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
001F: A link connection is associated with a protocol that is inoperative.
0020: A link resource is not available because of a mismatch between current operational parameters and the values specified at system generation.
0021: Resource Not Available: The link is associated with a connectivity subsystem that is not installed, not powered on, not initialized, or not operational.
0022: FRTE logical link activation failure caused by DLCI being not present. An ACTLINK was received for a FRTE resource but the last status message from the adjacent frame-relay node did not contain the DLCI.
0024: Link-level 2 test initiation failure caused by DLCI being inactive. An initiate link-level 2 test was received for a FRTE resource but the last status message from the adjacent frame-relay node indicated that the DLCI was inactive.
0025: Remote load failure caused by DLCI being inactive. An IPLINIT was received for a FRTE resource but the last status message from the adjacent frame-relay node indicated that the DLCI was inactive.
0026: The PU is not available because the connection between the dependent LU server and the dependent LU requester could not be established.
0027: A switched connection cannot be established because no switched link has been defined.
0028: REQDACTPU was received for a PU that is known but whose SSCP-PU session is currently inactive.
| 002A: An ACTLINK has been received for a resource that is
| still represented in the pool of available control
| blocks.
4001-4002: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.

0802

Intervention Required: Forms or cards are required at an output device, or a device is temporarily in local mode, or other conditions require intervention.

0803

Missing Password: The required password was not supplied.

0804

Invalid Password: Password was not valid.

0805

Session Limit Exceeded: The requested session cannot be activated, as one of the NAUs is at its session limit, for example, the LU-LU session limit or the (LU, mode) session limit, or an intermediate session routing (ISR) component in the path has reached its maximum active intermediate session count. This sense code applies to ACTCDRM, INIT, BIND, and CINIT requests.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: If accepted, the BIND request would prevent either the receiving LU or the sending LU from activating the number of contention winner sessions to the partner LU that were agreed upon during a change-number-of-sessions procedure.
0002: If accepted, the BIND request would cause the XRF-backup session limit to be exceeded.
0003: If accepted, the BIND request would cause the XRF-active session limit to be exceeded.
Note: The session limit for XRF-active sessions is 1. An XRF-active BIND is valid only if there are no XRF-active or XRF-backup sessions with the receiving SLU.
0005: The intermediate session router is unable to create a session connector control block. The pool of session connectors is saturated with active sessions and with pending-active sessions for which the Queue bit was set in the BIND; the BIND should not be retried.
0006: The intermediate session router is unable to create a session connector control block. The pool of session connectors is saturated with active sessions and with pending-active sessions for which the Queue bit was not set in the BIND; the BIND should be retried.
0008: For a dependent LU, if accepted, the BIND request would cause the session limit to be exceeded.
0009: If accepted, the request would cause the PLU session limit to be exceeded.
000A: If accepted, the request would cause the SLU session limit to be exceeded.
000B: The request was rejected because a session already exists between the same LU pair, and at least one of the LUs does not support parallel sessions.
000C: An LU-LU session was not established because a session already exists between the SLU and the session-controller PLU.
000D: The ISR component was unable to create a session connector because it had reached its maximum active intermediate session count. The BIND is rejected.

0806

Resource Unknown: For example, the request contained a name or address not identifying a PU, LU, SSCP, link, or link station known to the receiver or the sender.

Note: In an interconnected network environment, this sense code may be set by an SSCP in whose subnetwork and domain the LU was expected to reside; it is not set by an SSCP that is only an intermediary on the session-setup path. A gateway SSCP examines the Resource Identifier control vector in a session setup request (for example, CDINIT), to determine whether the LU is in the SSCP's subnetwork and domain.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The resources identified in an SNA Address List (X'04') MS common subvector are unknown to the PU receiving the request.
Note: When this sense data flows in a -RSP(NMVT), the referenced X'04' subvector is the one that was present in the corresponding request NMVT. When this sense data flows in a Sense Data (X'7D') MS common subvector, the referenced X'04' subvector is present with the X'7D' subvector in the same major vector.
0002: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
* 0005: The physical unit is currently in the physical unit
* dynamic reconfiguration pool.
0006: For a dynamic reconfiguration DELETE, MOVE, or REPLACE operation, the resource to be dynamically reconfigured could not be found.
0007: The LU address in bytes 8-9 of RNAA type X'4' is already in the free pool.
0008: For a dynamic reconfiguration DELETE, MOVE, or REPLACE operation, the NAU name in RNAA does not correspond to the resource identified by the element address in the RNAA.
0009: Reserved
000A: The configuration identifier specified in a management services command is not recognized by the DLC manager at the receiving node.
0011: An unknown OLU name was specified in the request.
0012: An unknown DLU name was specified in the request.
0013: An unknown SLU name was specified in the request.
0014: An unknown PLU name was specified in the request.
0015: An unknown OLU address was specified in the request.
0016: An unknown DLU address was specified in the request.
0017: An unknown SLU address was specified in the request.
0018: An unknown PLU address was specified in the request.
0021: The session-initiation request specified that the receiving SSCP is the SSCP having the DLU in its domain, but the DLU is unknown to the receiving SSCP.
0022: The originator of the request is unknown to the receiver.
0023: The destination of the request or response is unknown to the sender.
0024: An unknown LU1 name was specified in the request.
0025: An unknown LU2 name was specified in the request.
0026: The SSCP does not have a session with the boundary function PU of an independent LU.
0027: The PU associated with a switched SLU is unknown. Session setup processing for the switched SLU cannot proceed.
0028: NAU1 network address is unknown.
0029: NAU2 network address is unknown.
002A: The NAU name in the CONTACT or ACTLU does not correspond to the resource at the target address.
002B: The TG being activated is unknown.
002C: The identification supplied by the adjacent node in its XID3 differed from the identification that the receiving node was configured to expect.
002D,002E: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
002F: The destination resource was not found on this node during a session activation attempt.
0030: The adjacent node was not identified during CP-CP session activation or deactivation.
0031: Upon receiving a route request from another component in the node, TRS has been unable to locate in its topology database the destination network node or any network node specified in the TG vectors for the destination end node; the request is rejected.
0032: A SETCV defining an intra-FRSE PCV segment subport set was received containing an element address unknown to the receiver.
0033: A network resource needed for session establishment has become unavailable resulting in the termination of the pending session establishment procedure.
0034: REQDACTPU was received for an unknown PU.
0035: The local node has received an unknown adjacent CP name in a request to activate or deactivate a CP-CP session.
0036: No SSCP-SSCP session exists between the VRTG endpoints.

0807

Resource Not Available--LUSTAT Forthcoming: A subsidiary device will be unavailable for an indeterminate period of time. LUSTAT will be sent when the device becomes available.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.

0808

Invalid Contents ID: The contents ID contained on the ACTCDRM request was found to be invalid.

0809

Mode Inconsistency: The requested function cannot be performed in the present 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-000D: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
000E: The resource to be dynamically reconfigured (DRed) was defined at system-definition time and is defined as not DR-deletable.
000F: An RNAA received from an SSCP is rejected because it specifies a resource (adjacent link station or LU) that currently has an address assigned as a result of another SSCP's RNAA; or an ACTLU, FNA, or SETCV received from an SSCP is rejected because it specifies a resource address that is not assigned to an existing resource or is assigned as a result of another SSCP's RNAA.
0010-0013: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0014: ANS mismatch discovered.
0015: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0016: The PU type on SETCV does not match the actual PU type.
0017,0018: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0019: A SETCV was received containing a value for the SDLC BTU send limit that conflicts with the previous value received.
001A,001B: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
001C: The RNAA request contains a network ID that is not known to the gateway PU.
001D: An address pair session key in a Network-Qualified Address Pair (X'15') control vector is not known to the gateway PU.
001E: A gateway PU received an RNAA request for a cross-network session and all possible address transforms for the named resource are allocated.
001F: Retired
0020: The gateway node receiving an RNAA request cannot support another session between the named resource pair.
0021-0023: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0024: A PU received an ACTPU request with the SSCP-PU Session Capabilities control vector (X'0B') indicating that the sending SSCP does not support ENA, but the PU does not know the SSCP's maximum subarea address value.
0025: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0026: A SETCV was received containing an SDLC BTU send limit of 0.
0027: A request for a function was received by a component but the function was not enabled or activated.
0028: Cleanup termination of an LU-LU session has been converted to a forced termination by the LU. The SSCP must wait for session ended signals before deleting its session awareness records of the session.
0029: Second-level application state change has occurred. An application program served by an MS application program has changed the state of a node that may result in the rejection or failure of a current request or of a future request that would have previously been honored.
002A: The route setup procedure identified in a session services request was not in the expected state.
* 0030: An FNA was received for an LU that has an active
* LU-LU session.
0031: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0032: A BFSESSINFO was received when the subject LU was not pending BFSESSINFO; the reported sessions will be terminated, and the associated network addresses will be freed. This sense data is also included in the BFCLEANUP when the sessions are terminated.
0033: A BIND with the same LFSID used for an existing pending-reset session has been received by a boundary function from a peripheral PLU.
0034: A termination request has been received for a resource that has been taken over by an SSCP. The termination type is not strong enough to apply to the resources. The termination type needs to be Forced or Cleanup.
0035: An other-domain resource that was expected to be active is inactive.
0036: The short-hold mode logical connection selected does not exist.
0037: A non-short-hold mode connection was attempted on a port that is dedicated to short-hold mode operation.
0038: There is an inconsistency of mode between the XID sender and receiver. The XID receiver is operating in short-hold mode. Examples include inconsistent settings of the Short-Hold indicator (SHI) and the Short-Hold Status indicator (SHSI).
0039: CP capabilities exchange protocol error: CP Capabilities (X'12C1') GDS variable request sent indicating conversation complete or without change direction (i.e., CEB or �CD) or CP Capabilities reply sent indicating conversation not yet complete (i.e., �CEB).
003A: A null XID was received when an XID3 with its Exchange State indicators set to "prenegotiation," "negotiation proceeding,"or "Exchange State indicators not supported" was expected.
003B: A null XID was received when a nonactivation XID3 was expected.
003C: An XID3 with the Exchange State indicators set to "prenegotiation"was received when either of the values "negotiation proceeding" or "Exchange State indicators not supported" was expected.
003D: A nonactivation XID3 was received when a null XID or link-activation XID3 was expected.
003E: A link activation XID3 was received when a null XID or nonactivation XID3 was expected.
003F: The node with a secondary link station attempted to initiate a nonactivation exchange when secondary-initiated nonactivation exchanges are not supported on the connection.
0040: A mode-setting command was received and was either not expected or invalid for the receiving node; e.g., SNRME was received when SNRM was expected.
0041: An XID3 with the Exchange State indicators specifying a negotiation-proceeding exchange was received when an XID3 indicating a prenegotiation exchange was expected. If prenegotiation XID3s are used in a link activation XID exchange, each node must send and receive one.
0042: On an ABM TG on which secondary-initiated nonactivation XID exchanges are supported, the adjacent link station has initiated a nonactivation exchange by sending a nonactivation XID3 in which the ABM Nonactivation XID Exchange Initiator indicator specifies that the sending node is not initiating a nonactivation exchange. On such TGs, the initiator of a nonactivation exchange always explicitly indicates that it is initiating a nonactivation exchange.
0045: An XID3 indicating that the sender supports the Exchange State indicators was received when the sender had previously indicated that it does not support this field in XID3.
0046: An XID3 indicating that the sender does not support the Exchange State indicators was received when the sender had previously indicated that it does support this field in XID3.
0047: An XID has been received after receipt of a mode-setting command but before the completion of the mode-setting sequence, i.e., before RR, RNR, or an I-frame with the Poll bit set has been sent by the node with the primary link station after it has received UA in response to its mode-setting command.
0048: A node with an NRM primary link station has received an XID3 when it has no outstanding commands. NRM secondary link stations send XIDs only in response to XID commands.
0049: The XID3 received from the adjacent node had an XID Negotiation Error (X'22') control vector appended. The XID exchange will therefore terminate unsuccessfully.
004A: The request cannot be accepted because DR (dynamic reconfiguration) is in process for the target resource.
004B-004D: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
004E: A node with a secondary NRM link station has attempted to initiate a nonactivation XID exchange with an XID3. Nodes with secondary NRM link stations may solicit a nonactivation XID3 exchange only by means of sending a null XID at a response opportunity.
0050: An UNBIND request was received on behalf of a resource for which a previous UNBIND is in progress. The second UNBIND does not indicate an override of the first, and is therefore a duplicate request.
0051,0052: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
* 0053: An activation request was received for an SSCP whose
* subarea address is already associated with another
* SSCP name.
0054: The adjacent node is not the node type that the receiving node was configured to expect. The received negotiation-proceeding XID3 indicated that the adjacent node is an end node while this node expected the adjacent node to be a network node, or vice versa.
0055: The adjacent node is attempting to establish a connection through a connection network but the virtual routing node CP named in the TG Descriptor (X'46') control vector appended on the received negotiation-proceeding XID3 is not valid.
0057: The received NOTIFY type is not supported in the current state of the receiver.
0058: An intra-FRSE PVC segment subport received an RNAA(Assignment Type X'5') with a DLC Header Link Station Address field containing a value outside the valid range. The RNAA is rejected.
0059: An intra-FRSE PVC segment subport received an RNAA with a control vector X'43' specifying discontinue link-level contact if an auto network shutdown procedure is initiated. The RNAA is rejected.
| 005A: RNAA was received to add an intra-FRSE PVC segment
| subport to a hierarchical physical resource that is
| not active.
0060: An intra-FRSE PVC segment subport received an RNAA with a control vector X'43' specifying that modem test support is permitted. The RNAA is rejected.
0061: An intra-FRSE PVC segment subport received an RNAA with a control vector X'43' Frame send control value field containing a value outside the valid range. The RNAA is rejected.
0062: An intra-FRSE PVC segment subport received an RNAA with a control vector X'43' Node Type Identifier field specifying a node type other than T1. The RNAA is rejected.
0063: An intra-FRSE PVC segment subport received an RNAA with a control vector X'43' specifying that null XID polling for the secondary station should be used. The RNAA is rejected.
0064: A SETCV defining an intra-FRSE PVC segment subport set was received that contained an element address in the DR pool.
0065: A SETCV defining an intra-FRSE PVC segment subport set was received from an SSCP that did not originally add all the subarea element addresses listed in the SETCV to the DR pool.
0066: An ACTTRACE was received for a link connection trace while a trace for a logical link using that link connection was active, or ACTTRACE was received for a logical link trace while a trace for its underlying physical link connection was active.
0067: An intra-FRSE PVC segment subport received an RNAA5 containing a DLC Header Link Station Address that is being used by an existing Frame Relay Terminating Equipment subport.
0068: An XID was received with a Networking Capabilities indicator (specifying whether the sender is an APPN network node) that is inconsistent with the receiver's definition for the connection. The connection is rejected.
0069: An XID was received with CP Services and CP-CP Session Support indicators that are inconsistent with the receiver's definition for the connection. The connection is rejected.
| 006A: A node type mismatch exists between the two SSCPs
| setting up a VRTG. An SSCP learns when the VRTG is
| established that the partner SSCP's APPN node type
| (NN or EN) is different from the type locally
| defined for that partner SSCP.
| 006B: The IP address specified in an RNAA(Type=X'05') for
| a new Internet Protocol (IP) PU is a duplicate of an
| existing IP address.

080A

Permission Rejected: The receiver has denied an implicit or explicit request of the sender.

When sent in response to BIND, it implies either that the secondary LU will not notify the SSCP when a BIND can be accepted, or that the SSCP does not recognize the NOTIFY vector key X'0C'. (See the X'0845' sense code for a contrasting response.)

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: An SSCP has denied permission to establish a session through its resources; the receiving SSCP should not attempt to reroute the request to another SSCP.
0002: An SSCP has denied permission to establish a session through its resources; the receiving SSCP should attempt to reroute the request to another SSCP.
0005: An SSCP has denied permission to continue session setup. A DLU name was presented to an alias selection function (authorization application) that rejected it. The receiving SSCP should not attempt to reroute the request to another SSCP.
0006: An SSCP has denied permission to continue session setup. A DLU name was presented to an alias selection function (authorization application) that rejected it. The receiving SSCP should attempt to reroute the request to another SSCP.
0007: An activation request was received for a resource that has a NETID different from that of the requesting SSCP, and the requesting SSCP indicated previously that it does not support this configuration.
0008: The request specified in the Request Change Control MS major vector was rejected because it did not originate from a valid focal point.
0009: The request specified in the Request Change Control MS major vector was rejected because the ability to support it has been disabled at the receiver.
000A: The request was rejected because it would prohibit compliance with the status-reporting requirements specified in the Reporting Level MS Common subvector.
000B: The request was rejected because the second-level application, though recognized, operates under the control of a program other than that which has received and is to forward the request to that second-level application program.
000C: The request was rejected because the timer/clock at the receiver is protected and cannot be set by the request sender.
000D: An SSCP or CP has denied a Locate search request. The receiving SSCP or CP should attempt to reroute the request.
000F: The request was rejected because of constraints or policies specific to the receiving DLUS. The request should not be retried.

080B

Bracket Race Error: Loss of contention within the bracket protocol. This error can arise when bracket initiation/termination by both NAUs is allowed.

080C

Procedure Not Supported: A procedure (Test, Trace, IPL, REQMS type, MS major vector key) specified in an RU is not supported by the receiver.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001-0004: Set aside for implementation specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0005: The MS major vector key is not supported by the receiver.
0006: The MS major vector is identified as one that contains a command, but the receiver does not recognize or support the command subvector. (See the X'086C' sense code for the case in which the command subvector is identified, but an additional required subvector is missing.)
0007: A request for a function is supported by the receiver, but the resource identified in the request does not support that function (no function is specifically indicated).
0009: A request for session information retrieval for an independent LU was received in an REQMS; such requests are permitted only in an NMVT.
000A: A request was received containing a Name List MS subvector or an SNA Address List MS subvector with multiple entries, but the receiver supports only a single entry in such a subvector.
000B: An MS Request Change Control major vector was received requesting automatic delayed acceptance, but the receiver does not support that function.
000C: Set aside for implementation specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
000D: An MS Request Change Control major vector was received requesting post-test, but the receiver does not support that function.
000E: An MS Request Change Control major vector was received prohibiting automatic removal of a change, but the receiver does not support that function.
000F: An Activate MS major vector was received specifying use of changes installed in production only, but the receiver supports such a request only when it is received locally.
0010: Reserved
0011: Set aside for implementation specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0012: Application GDS variable in an MDS-MU not supported.
0013: MDS message type not supported. Receiving node does not support the MDS message type in this MDS-MU.
0014: An MS major vector was received requesting execution window timing, but the receiver does not support that function.
0015: An MS Activate major vector was received specifying change management activation use, but the receiver does not support that function.
0016: An MS Request Change Control major vector was received requesting Activate with Force Delay, but the receiver does not support that function.
0017: The changes referred to in a Request Change Control MS major vector are already installed on trial and the receiver does not support the transfer from trial to production with removability=yes.
0018: An MS Request Change Control major vector was received requesting pre-test, but the receiver does not support that function.
0019: A link trace requested in ACTTRACE is not supported for frame-relay logical links.
01nn: A subvector in an MS major vector is identified as one inside which the receiver requires one of a number of supported subfields, but none of these subfields is present. Byte 3 contains the key (nn) of the subvector.
4001, 4003: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.

080D

NAU Contention: A request to activate a session was received while the receiving half-session was awaiting a response to a previously sent activation request for the same session; for example, the SSCP receives an ACTCDRM from the other SSCP before it receives the response for an ACTCDRM that it sent to the other SSCP and the SSCP ID in the received ACTCDRM was less than or equal to the SSCP ID in the ACTCDRM previously sent.

080E

NAU Not Authorized: The requesting NAU does not have access to the requested resource.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The PU, according to its system definition, does not accept an ACTPU from any SSCP having the network ID of the sending SSCP.
0002: A gateway T4 node received a dynamic dump request from an SSCP that is not in the native network of the gateway T4 node.
0003: The link station received a CONTACT from an unauthorized SSCP.
0004: A BFCLEANUP was received from an unauthorized SSCP.
0005: An RNAA was received from an unauthorized SSCP.
0006: A network node received a Register from an unauthorized APPN end node.
0007: A network node received a Register from another network node.
0008: A network node received a Delete from another network node.
0009: A network node received a Delete from an unauthorized APPN end node.
000A: Retired
000B: A Locate/CD-Initiate was received from a node that is not defined as a client end node. This can be detected by either DS or SS.
000C: A gateway T4 node received a dynamic dump request from an SSCP that is not in the native network of the gateway T4 node.

080F

End User or LU Not Authorized: The requesting end user or LU does not have the proper security authorization to access the requested resource.

0000: No specific code applies.
0001: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0002: An LU that supports only the enhanced LU-LU verification protocol received a BIND or RSP(BIND) that specified the basic LU-LU verification protocol.
0004: An attempt was made to install or remove a database table before issuing a logon to the database.
0983: Access Denied: The request specifies a resource that the requester is not permitted to access. Access to a resource is controlled by evaluation of the requester's identity, profile, or location. This sense data is sent in FMH-7.
6051: Access Security Information Invalid: The request specifies an Access Security Information field that is unacceptable to the receiver; for security reasons, no further detail on the error is provided. This sense data is sent in FMH-7 or UNBIND.
6058: Access Failure: The request specifies an Access Security Information field that is unacceptable because of a processing failure.
| 8000: Access Failure: GSS-API Unexpected Status Value -- A
| GSS-API request returned an unrecognized status value.
| 8001: Access Failure: GSS-API GSS_BAD_MECH -- unsupported
| mechanism requested
| 8002: Access Failure: GSS-API GSS_BAD_NAMETYPE -- name of
| unsupported type provided
| 8003: Access Failure: GSS-API GSS_BAD_BINDINGS -- channel
| binding mismatch
| 8004: Access Failure: GSS-API GSS_BAD_NAME -- invalid name
| provided
| 8005: Access Failure: GSS-API GSS_BAD_STATUS -- invalid input
| status selector
| 8006: Access Failure: GSS-API GSS_BAD_SIG -- token had invalid
| signature
| 8007: Access Failure: GSS-API GSS_DEFECTIVE_CREDENTIAL --
| defective credential detected
| 8008: Access Failure: GSS-API GSS_DEFECTIVE_TOKEN -- defective
| token detected
| 8009: Access Failure: GSS-API GSS_FAILURE -- failure,
| unspecified at GSS-API level
| 800A: Access Failure: GSS-API GSS_NO_CONTEXT -- no valid
| security context specified
| 800B: Access Failure: GSS-API GSS_NO_CRED -- no valid
| credentials provided
| 8101: Retryable Access Failure: GSS-API GSS_CONTEXT_EXPIRED --
| specified security context expired
| 8102: Retryable Access Failure: GSS-API GSS_CREDENTIALS_EXPIRED
| -- expired credentials detected
| 8103: Retryable Access Failure: Deferred Authentication
| processing was requested, but communications failures
| occurred while attempting to communicate with the
| Distributed Authentication Service TP.
| 8104: Retryable Access Failure: Deferred Authentication
| processing was requested, but the origin could not locate
| the conversation's security context.
FF00: Access Failure: The request specifies a password that is expired.
FF01: Access Failure: The request specifies a password that is invalid.
FF02: Access Failure: The request specifies a user ID that is revoked.
FF03: Access Failure: The request specifies a user ID that is invalid.
FF04: Access Failure: The request is missing a user ID.
FF05: Access Failure: The request is missing a password.
FF06: Access Failure: The request specifies a group that is invalid.
FF07: Access Failure: The request specifies a user ID that is revoked in the specified group.
FF08: Access Failure: The request specifies a user ID that is not defined in the specified group.
FF09: Access Failure: The request specifies a user ID that is not authorized to access the remote LU.
FF0A: Access Failure: The request specifies a user ID that is not authorized to access the remote LU from the local LU.
FF0B: Access Failure: The request specifies a user ID that is not authorized to access the transaction program at the remote LU.
FF0C: Access Failure: The request failed as a result of installation exit processing at the remote LU.
FF0D: Access Failure: The request failed because of a processing failure between the local LU and the remote LU. This is a correctable error, so subsequent requests might succeed.
FF0E-FFFF: Reserved for future needs for security.

0810

Missing Requester ID: The required requester ID was missing.

0811

Break: Asks the receiver of this sense code to terminate the present chain with CANCEL or with an FMD request carrying EC. The half-session sending the Break sense code enters chain-purge state when Break is sent; the half-session receiving the Break sense code discards the terminated chain without ever retransmitting it.

0812

Insufficient Resource: Receiver cannot act on the request because of a temporary lack of resources.

Bytes 2 and 3 may contain the following sense code specific information:

0000: No specific code applies.
0001: More PUs or LUs are requested by RNAA than are present in the pool.
0002: More PUs or LUs are requested by RNAA than the attachment resource will hold.
0003: Resources are not currently available to support an XRF session.
0004: The RNAA request indicates that the requested address must be pre-ENA compatible, but no pre-ENA compatible address is available.
0005: The Requested Reserved Resources for Sessions Are Not Available: In RNAA, a reservation of session resources exceeded those available; no address was assigned and no change was made to the LU's current reservation.
0006: Unsuccessful Allocation: The intermediate session router or boundary function lacks resources to support a session connector. The RU being rejected is a BIND.
0007: Insufficient resources are available for LU address allocation.
0008: No Buffer Space: The session was deactivated because of a buffer shortage when extending a nonextended positive RSP(BIND). Insufficient resources exist to extend a BIND response.
0009: No unreserved session connectors are available to add an LU.
000A: A network node does not have adequate resources to honor a Register request (the available directory capacity has already been reached).
000B: A BFSESSINFO was received for an unknown LU.
000C: Not enough buffer space exists to support a deadlock-free transmission group. The receiver does not have enough buffers to allocate a BIND receive buffer.
000D: Insufficient buffers exist to activate a session.
000E: A BIND or BFCINIT cannot be processed because of insufficient storage to keep the network-qualified name of the initiating control point.
000F: Insufficient buffer space exists to build a BFINIT.
0010: The CP does not have adequate resources to process a GDS variable request; it will deactivate its CP-CP sessions with the partner CP.
0011: Insufficient storage is available to the SNA component to satisfy the request at this time.
0012: No memory is available to establish the timer queue specified in the request.
0014: This session has failed because of storage depletion at an intermediate node.
0015: Insufficient resources are available to initiate a short-hold mode connection.
0016: Unknown network identifier
0017: Insufficient buffer space exists to process a nonimmediate UNBIND.
0018: All LFSIDs this node is allowed to assign on the TG are in use at this time; the request is rejected.
0019: Insufficient storage is available to conduct an XID exchange.
001A: Insufficient storage is available to activate a TG.
001B: Insufficient resources to activate a token-ring connection.
001C: Insufficient storage exists to respond precisely to an error condition.
Note: This sense data is returned when node buffer resources are in critical depletion and storage cannot be obtained to build a more specific error response.
001D: The receiving T4 node does not have sufficient disk space to perform the requested dump.
001E: A session has failed because depletion of pooled buffer storage has exceeded a critical threshold resulting from that session's monopolizing usage.
001F: Cannot create or access an internal space or object.
0021: A received XID3 cannot be fully processed because the receiver has insufficient storage to keep the network-qualified name of the sender's control point.
0025: Insufficient storage to keep the network-qualified name of the connection network.
| 0026: The specified TG was not activated because insufficient
| bandwidth was available on the local port.
| 0027: The specified TG was not activated because insufficient
| bandwidth was available on the destination port.
| 0028: The specified TG was not activated; a switched subnetwork
| had insufficient resources to accept a connection request.
nxxx: Insufficient resources of type n (n = 1 or 2) exist to fully satisfy the received request. The value xxx is a byte offset into the received RU indexing the first specified network element (e.g., PU, LU, or Link) for which resources could not be obtained. The type (n) of resource specified is product dependent.

0813

Bracket Bid Reject--No RTR Forthcoming: BID (or BB) was received while the first speaker was in the in-bracket state, or while the first speaker was in the between-brackets state and the first speaker denied permission. RTR will not be sent.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
Note: For LU 6.2, this is the only setting defined.
0001: Bracket Bid Reject: The component was in the in-bracket state when a bracket request was received.
0002: Bracket Bid Reject: The component was in the between-bracket state when a bracket request was received.

0814

Bracket Bid Reject--RTR Forthcoming: BID (or BB) was received while the first speaker was in the in-bracket state, or while the first speaker was in the between-brackets state and the first speaker denied permission. RTR will be sent.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
Note: For LU 6.2, this is the only setting defined.

0815

Function Active: A request to activate a network element or procedure was received, but the element or procedure was already active.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: A session activation request was received by a boundary function to activate a session that was already active.
0002: A session activation request was received by a gateway function to activate a cross-network session that was already active.
0003: Processing for another management services request in progress. Sender should retry the request.
Note: This sense data is sent only by a type 2 node, which may lack sufficient queuing space.
0004: A BIND was received from a T2.1 node when the session is already active; i.e., the LFSID is in use. The receiver rejects the BIND.
0005: An IPL function (the loading or storing of a load module) is in progress.
0006: The short-hold mode connection selected has been recalled on another port.
0007: A session activation request was received by an APPN node to activate a CP-CP session that was already active.
0009: A session activation request was received by an APPN end node to activate a CP-CP session with a network node when a CP-CP session is already active with another network node.

0816

Function Inactive: A request to deactivate a network element or procedure was received, but the element or procedure was not active.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: A session deactivation request was received by an APPN node to deactivate a CP-CP session that was not active.

0817

Link or Link Resource Inactive: A request requires the use of a link or link resource that is not active.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Link inactive.
0002: Link station inactive.
0003: Switched link connection inactive.
0004: The TG number of the desired link has been renegotiated to a new value; the route cannot be activated.
0005: Service link inactive.
0006: The link between an SNA node and an attached processor is inactive; for example, the connection between the main processor and its attached service processor goes down.
0007: The requested test was not initiated because the link to be tested was put into an inactive state.
0008: The requested test was interrupted because the link to be tested was put into an inactive state.
0009: Transport configuration table entry not active.
4001: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.

0818

Link Procedure in Process: CONTACT, DISCONTACT, IPL, or other link procedure in progress when a conflicting request was received.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001,0002: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0003: CONTACT Not Serialized, Retry: An initial CONTACT procedure is in progress and a nonactivation CONTACT was received by the PU. The nonactivation CONTACT is rejected until the initial CONTACT procedure is completed.
0004: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0005: Link problem determination test for a modem in progress.
0006: On-line terminal test in progress.
0007: SDLC link test, level 2, in progress.
0009: The requested test was not initiated because another test was already in progress.
000A: An on-line terminal test (OLTT) is active on the service link.
000B: SDLC link test, level 2, in progress on the service link.
000C: Link problem determination test for a modem on the service link in progress.

0819

RTR Not Required: Receiver of Ready To Receive has nothing to send.

081A

Request Sequence Error: Invalid sequence of requests.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: An ACTLU was received and no SSCP-PU session exists.
0002: An IPL or DUMP RU sequence error has occurred.
0004: An NC-ER-TEST was to be sent as a result of receiving a ROUTE-TEST request. The ROUTE-TEST was sent in one subnetwork, and the NC-ER-TEST was to be sent in another. The SSCP sending the ROUTE-TEST did not have a required alias address within the subnetwork where the NC-ER-TEST was to be sent. (Before sending ROUTE-TEST, the SSCP sends RNAA, or the installation predefines the alias address, so that an origin SSCP address is available within the subnetwork of the route being tested. This address is then specified in the NC-ER-TEST RU.)
0006: RNAA Rejected: If the PU of the node to which an LU is to be added was RNAA-added and a control vector has not been received, the RNAA is rejected. A SETCV for the PU has not been received and processed.
0007: A CONTACT, BIND, or ACTLU has been received from an SSCP that has not established ownership of a permanent (system-defined) resource. The resource is not usable until RNAA(Move) has been received.
0008: A CONTACT, BIND, or ACTLU has been received from an SSCP that has not established ownership of a temporary (DR-added) resource. The resource is not usable until RNAA(Add) has been received.
0009-000F: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0010: The request is rejected or fails because the entry point or a target resource in the entry point is already in the state or condition that the request would have produced.
0011: A CONTACT was received specifying APPN in its Connection Support field, but was not preceded by a CONNOUT, a protocol violation.
0012: A CONTACT was received with a Connection Support field value that does not match that in the preceding CONNOUT.
0013: A CONNOUT, specifying LEN in its Connection Support field, was received for a nonswitched link station, a protocol violation.
0014: A CONTACT was received for an intra-FRSE PVC segment subport whose frame-relay port is in a discontacted state. The CONTACT is rejected.
0015: A CONTACT was received for an RNAA-added intra-FRSE PVC segment subport and a SETCV with a FRSE (X'80') control vector has not been received. The CONTACT is rejected.

081B

Receiver in Transmit Mode: A race condition exists: a normal-flow request was received while the half-duplex contention state was not-receive, (*S,�R), or while resources (such as buffers) necessary for handling normal-flow data were unavailable. (Contrast this sense code with X'2004', which signals a protocol violation.)

081C

Request Not Executable: The requested function cannot be executed, because of a permanent error condition in the receiver.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0002: The receiver has an error resulting from a software problem that prevents execution of the request.
0003: A hardware error was indicated for the link.
0005: A power-on request failed.
0006: A processor microcode load request failed.
0007: An operating system load request failed.
* 0008: Channel device name was not defined.
0009: A processor microcode quiesce request failed.
000A: A power-off request failed.
000B: The requested test was completed successfully, but the results of the test are not available due to a software failure.
00B1: An SDLC error was detected during link problem determination for a modem.
00B2: A modem error (for example, modem check) was detected during link problem determination.
00B3: A timeout threshold was exceeded for a link problem determination aid modem response.
00B4: An overrun or underrun occurred in the node using the link connection during link problem determination for a modem.
00B5: Data Check was signaled during LPDA-2 test.
00B6: Format exception was signaled during LPDA-2 test.
00B7: LPDA-2 modem test was attempted and failed because of a communication controller equipment (for example, scanner) error.
00B8: Hardware error indicated on the service link.
00B9: Service link not defined.
00BA: The receiver has an error resulting from a microcode problem that prevents execution of the request.
0n0m: An error was detected by the DLC manager of the receiving node during the execution of a management services request. If n=X'A', the link connection status has not changed from the state previous to the execution; if n=X'B', the link connection status was modified from the state existing previous to the execution. The error is specified as follows: m=X'1' for volatile storage error, m=X'2' for nonvolatile storage (e.g., file access error), m=X'3' for link connection component (e.g., modem) interface error, and m=X'4' for unspecified software error conditions.

Sense code specific information settings 0004, 0008, 000C, 0010, 0014, 0018, 0020, 0028, 0030, 0034, 0038, 003C, 0040, 0072, 0098, 00AB, 0100-0109, 0120-0126, 0149, 0189-0191, 0200-0209, 0210-0225, 290, 0291, 07**, and 08** are all set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.

081D

Invalid Network Address or Name: A node, station, or CP identifier in the request was found to be invalid.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: The station ID or SSCP ID in the request was found to be invalid.
0001: The network ID, LU name pair in the request was found to be invalid.
0002: Invalid resource name found in the request.
0003: The network ID, SSCP name pair in the request was found to be invalid.
0004: A duplicate CP name has been detected, causing the links to one or both of the nodes having the same CP name to be deactivated.

081E

Session Reference Error: The request contained reference to a half-session that either could not be found or was not in the expected state (generally applies to network services requests).

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: No Session Found: The session identified in the BFCLEANUP was not found; the BFCLEANUP is rejected.
0002: The session identified in the BFCINIT was not found; the BFCINIT is rejected.
0003: No session was found during the processing of a session services request.
0004: The appropriate session was found during processing of a session services request, but the session is not in the expected state.

081F

Request Was Canceled by an Operator.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The operator has either canceled the link activation request or deactivated the link.

0820

Control Vector Error: Invalid data for the control vector specified by the target network address and key.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: In a SETCV defining an intra-FRSE PVC subport set, one or both of the primary subport partners that define the subport set are not defined.
0002: In a SETCV defining an intra-FRSE PVC subport set, a specified element address does not define a subport within a subport set, or is defined more than once in a subport set.
0003: An element address of an intra-FRSE PVC subport set received in a SETCV was found to be already associated with another subport set.

0821

Invalid Session Parameters: Session parameters were not valid or not supported by the half-session whose activation was requested.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Invalid Mode Name at LU: The specified mode name was not recognized by the LU.
0002: Invalid Mode Name at CP: The specified mode name was not recognized by the CP.
0003: The primary half-session requires cryptography, but the secondary half-session does not support cryptography.
0004: The secondary half-session requires cryptography, but the primary half-session does not support cryptography.
0005: Selective or mandatory cryptography is specified, but no SLU cryptographic data key is provided.
0006: The BIND was rejected because it was nonnegotiable and specified a primary send pacing window size larger than the SSCP or BF can handle.
0007: The specified mode name was not recognized in a subarea network.
0008: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0009: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
000A: Specified mode table name not found at receiving CP.
000B: Sent on an UNBIND to signal that a RSP(BIND) was received indicating an insufficient level of compression support.
000C: Sent on an UNBIND to signal that a BIND was received indicating an insufficient level of compression support.

0822

Link Procedure Failure: A link-level procedure has failed because of a link equipment failure, a loss of contact with a link station, or an invalid response to a DLC command. (This is not a path error, since the request being rejected was delivered to its destination.)

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: An IPLINIT request was received by a T4 node, resulting in a link disconnection. The sender should reinitialize the dial connection and resend the IPLINIT request.
80nn: nn is product-specific and will not be otherwise defined in SNA.

0823

Unknown Control Vector: The control vector specified by a network address and key is not known to the receiver.

0824

Logical Unit of Work Aborted: The current unit of work has been aborted; when sync point protocols are in use, both sync point managers are to revert to the previously committed sync point.

For LU 6.2, this sense data is sent only in FMH-7.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000

For LU 6.2, Backout Initiated--No Resync In Progress: A transaction program or its LU has initiated backout. The protected resources for the distributed logical unit of work are to be restored to the previously committed sync point.

When sent in reply to a PS header, no resync in progress means that all resources in the transaction subordinate to the backout sender have backed out.

For non-LU 6.2, no specific code applies.

0001

For LU 6.2, Backout Initiated -- Resync In Progress: A transaction program or its LU has initiated backout. The protected resources for the distributed logical unit of work are to be restored to the previously committed sync point.

When sent in reply to a PS header, resync in progress means that one or more resources in the transaction subordinate to the backout sender have experienced failure so it is not known whether they've backed out.

0825

Component Not Available: The LU component (a device indicated by an FM header) is not available.

0826

FM Function Not Supported: A function requested in an FMD RU is not supported by the receiver. (Note: X'1003' has displaced this value for reporting such conditions.)

0827

Intermittent Error--Retry Requested: An error at the receiver caused an RU to be lost. The error is not permanent, and retry of the RU (or chain) is requested.

0828

Reply Not Allowed: A request requires a normal-flow reply, but the outbound data flow for this half-session is quiesced or shut down, and there is no delayed reply capability.

0829

Change Direction Required: A request requires a normal-flow reply, but the half-duplex flip-flop state (of the receiver of the request) is not-send, and CD was not set on the request. Therefore, there is no delayed reply capability.

082A

Presentation Space Alteration: Presentation space altered by the end user while the half-duplex state was not-send, (�S,*R); request executed.

082B

Presentation Space Integrity Lost: Presentation space integrity lost (for example, cleared or changed) because of a transient condition--for example, because of a transient hardware error or an end user action such as allowing presentation services to be used by the SSCP. (Note: The end-user action described under X'082A' and X'084A' is excluded here.)

082C

Resource-Sharing Limit Reached: The request received from an SSCP was to activate a half-session, a link, or a procedure, when that resource was at its share limit.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Invalid Request: The specified link station has already received a CONTACT and is therefore under the control of another SSCP. This CONTACT would exceed the share limit (=1).
0002: Invalid Request: The specified PU has already received an ACTPU and is therefore under the control of another SSCP. This ACTPU would exceed the share limit (=1).

082D

LU Busy: The LU resources needed to process the request are being used; for example, the LU resources needed to process the request received from the SSCP are being used for the LU-LU session.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.

082E

Intervention Required at LU Subsidiary Device: A condition requiring intervention, such as out-of-paper, power-off, or cover interlock open, exists at a subsidiary device.

082F

Request Not Executable because of LU Subsidiary Device: The requested function cannot be executed, because of a permanent error condition in one or more of the receiver's subsidiary devices.

0830

Session-Related Identifier Not Found: The receiver could not find a session-related identifier for a specified session.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: PCID not found for the specified resources.
0002: LSID not found for the specified session.

0831

LU Component Disconnected: An LU component is not available because of power-off or some other disconnecting condition.

0832

Invalid Count Field: A count field contained in the request indicates a value too long or too short to be interpreted by the receiver, or the count field is inconsistent with the length of the remaining fields.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

nnnn: Bytes 2 and 3 contain a binary count that indexes (0-origin) the first byte of the invalid count field.

Note: This sense code is not used for a BIND error because the displacement of fields within the BIND may not be the same at both ends of a session when the BIND was affected by name transformations--for example, after the BIND has passed through a gateway. Sense code X'0835' is used to specify a displacement for a BIND error.

0833

Invalid Parameter (with Pointer and Complemented Byte): One or more parameters contained in fixed- or variable-length fields of the request are invalid or not supported by the NAU that received the request.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

nnmm: Byte 2 contains a binary value that indexes (0-origin) the first byte that contained an invalid parameter.
Byte 3 contains a transform of the first byte that contained an invalid parameter: the bits that constitute the one or more invalid parameters are complemented, and all other bits are copied.

0834

RPO Not Initiated: A power-off procedure for the specified node was not initiated because one or more other SSCPs have contacted the node, or because a CONTACT, DUMP, IPL, or DISCONTACT procedure is in progress for that node.

0835

Invalid Parameter (with Pointer Only): The request contained a fixed- or variable-length field whose contents are invalid or not supported by the NAU that received the request; or a +RSP(BIND) received at an intermediate node within a session path contained such an error (in which case, it was converted to a -RSP or UNBIND carrying this sense data value)

nnnn: Bytes 2 and 3 contain a two-byte binary count that indexes (0-origin) the first byte of the fixed- or variable-length field having invalid contents.

Note: This sense code is not used to report an invalid value in an MS major vector. If the invalid value occurs in a formatted MS subvector, sense code X'086B' is used. If it occurs in an unformatted subvector, sense code X'0870' is used.

0836

PLU/SLU Specification Mismatch: For a specified LU-LU session, both the origin LU (OLU) and the destination LU (DLU) have only the primary capability or have only the secondary capability.

0837

Queuing Limit Exceeded: For an LU-LU session initiation request (INIT, CDINIT, or INIT-OTHER-CD) specifying (1) Initiate or Queue (if Initiate not possible) or (2) Queue Only, the queuing limit of either the OLU or the DLU, or both, was exceeded.

0838

Request Not Executable Because of Resource or Component State Incompatibility: The request is not executable because it is not compatible with the state of a resource or component in the receiver.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The change referred to in a Request Change Control MS major vector or Report-FS-Action command cannot be deleted or replaced because it is installed marked removable.
0002: One or more of the changes referred to in a Request Change Control MS major vector cannot be installed, removed, or accepted because they are in back-level state (see Note).
0003: One or more of the changes referred to in a Request Change Control MS major vector cannot be installed marked on-trial because they are already installed marked on-trial (see Note).
0004: One or more of the changes referred to in a Request Change Control MS major vector cannot be installed marked on-trial or in-production because they are already installed marked in-production removably (see Note).
0005: One or more of the changes referred to in a Request Change Control MS major vector cannot be installed marked on-trial or in-production because they are already installed marked in-production and nonremovable (see Note).
0006: One or more of the changes referred to in a Request Change Control MS major vector cannot be removed or accepted because they are installed marked nonremovable (see Note).
0007: One or more of the changes referred to in a Request Change Control MS major vector cannot be removed or accepted because they are not installed (see Note).
0008: Pre-test is not applicable to one or more of the changes referred to in a Request Change Control MS major vector (see Note).
0009: Execution window timing is not applicable to one or more of the changes referred to in a Request Change Control MS major vector (see Note).
000A: Automatic removal is not applicable to one or more of the changes referred to in a Request Change Control MS major vector (see Note).
000B: Post-test is not applicable to one or more of the changes referred to in a Request Change Control MS major vector (see Note).
000C: Automatic delayed acceptance is not applicable to one or more of the changes referred to in a Request Change Control MS major vector (see Note).
000D: One or more of the changes referred to in a Request Change Control MS major vector cannot be installed marked in-production because they are installed marked on-trial with a set of corequisites different from those requested on this install request.
One or more reported-on token strings are used to identify the corequisite changes currently installed when the report code is carried in an SNA condition report.
000E: One or more of the changes referred to in a Request Change Control MS major vector cannot be accepted because they are installed marked on-trial (see Note).
000F: One or more of the changes referred to in a Request Change Control MS major vector or Report-FS-Action command cannot be replaced or deleted because they are critical system components that must always have an installed instance. The only possibility is to perform data object renewal using Send-and-Install with removability prohibited or desired (but not required) (see Note).
0010: One or more of the changes referred to in a Request Change Control MS major vector or Report-FS-Action command cannot be stored or installed because an implementation-defined limit on the number of changes has been exceeded (see Note).
0011: One or more of the changes referred to in a Request Change Control MS major vector or Report-FS-Action command cannot be deleted or replaced because they are required in order to maintain removability of other changes. They may be in backup state or installed marked in-production (see Note).
0012: One or more of the corequisite changes referred to in a Request Change Control MS major vector are missing or are in a state incompatible with the request (see Note).
0013: The change referred to in a Request Change Control MS major vector or Report-FS-Action command cannot be replaced because it is installed marked in-production and non-removable and another change is not being installed in this operation (see Note).
0014: One or more of the changes referred to in a Request Change Control MS major vector cannot be installed because a precluded combination of values in the Removability, Automatic Removal, Automatic Acceptance, or Activation Use subfields was specified (see Note).
0015: One or more of the changes referred to in a Request Change Control MS major vector cannot be installed because one or more changes already installed are still removable for one or more components to be altered by these changes (see Note).
0016: One or more of the changes referred to in a Request Change Control MS major vector or Report-FS-Action command cannot be replaced because they would be required for removable installation, and removability is required (see Note).
0017: Execution of the request referred to in an MS Cancel major vector has proceeded too far to cancel.
001A: The request will not be honored because it was either queued or active at a node at the time a local operator assumed control of the node, thus effecting its cancellation.
001B: The request will not be honored because it was submitted to a node at a time when a local operator or other application was in control of the node.
001C: One or more of the changes referred to in a Request Change Control MS major vector cannot be installed removably because the implementation does not support removability for certain classes of data objects (see Note).
001D: One or more of the changes referred to in a Request Change Control MS major vector cannot be installed because the implementation precludes corequisite specification for certain classes of data objects (see Note).
001E: One or more of the changes referred to in a Request Change Control MS major vector or Report-FS-Action command cannot be installed or stored because the implementation has identified a prerequisite change that is either not installed or is installed at an incompatible level (see Note).
001F: The change referred to in a Request Change Control MS major vector or Report-FS-Action command cannot be stored because the implementation has identified a missing larger entity that must first be stored before the subentity may be stored (see Note).
0020: One or more of the changes referred to in a Request Change Control MS major vector are installed in production but cannot be removed or accepted because they are required in order to maintain removability of other changes (see Note).
0021: One or more of the changes referred to in a Request Change Control MS major vector cannot be installed, removed, or accepted because the implementation does not support certain classes of data objects (see Note).
0022: The change referred to in a Report-FS-Action command cannot be stored because another change having the same data object class already exists in sent state and the implementation prohibits more than one change of the same object class to exist in sent state for certain classes of objects. The previous change must first be installed or deleted.
A reported-on token string is used to identify the change currently in sent state when the report code is carried in an SNA condition report.
0023: The request will not be honored because a system resource file was locked at the time execution was attempted.
0024: One or more of the changes referred to in a Request Change Control MS major vector could not be installed because an unexpected error was encountered while performing the installation process (see Note).
0025: The change referred to in a Request Change Control MS major vector or Report-FS-Action command cannot be stored because a reactivation of the node must first be performed (see Note).
0026: The target group object of one or more changes referred to in a Request Change Control MS major vector does not exist (see Note).
0027: The target group object of one or more changes referred to in a Request Change Control MS major vector is not accessible (see Note).
0028: The class code of one or more changes referred to in a Request Change Control MS major vector is inconsistent with the class code of the target group object for the affected component (see Note).
0029: The installation of one or more changes referred to in a Request Change Control MS major vector would require nesting of group objects, which is not supported (see Note).
002A: The class code of one or more changes referred to in a Request Change Control MS major vector is inconsistent with the class code of installed changes affecting the same component (see Note).
002B: The installation procedure for one or more changes referred to in a Request Change Control MS major vector was not found (see Note).
002C: The command processor to execute the installation procedure for one or more changes referred to in a Request Change Control MS major vector could not be found (see Note).
002D: The name of one or more changes referred to in a Request Change Control MS major vector does not contain an architecturally defined subtree as required by the receiver (see Note).
002E: The specification of Alter_Active_Components=No is not supported by the receiver for the class code of one or more changes referred to in a Request Change Control MS major vector (see Note).
002F: No group object is defined, and either insufficient or illegal default group information was provided for one or more changes referred to in a Request Change Control MS major vector (see Note).
0030: One or more of the changes referred to in a Request Change Control MS major vector cannot be removed (or accepted) because a previous Accept (or Remove) request has failed and its effects could not be backed out. Only a retry of the same request can be attempted (see Note).
0031: One or more of the changes referred to in a Request Change Control MS major vector are not independent and can not be installed as corequisites (see Note).
0032: The modification level of one or more changes referred to in a Request Change Control MS major vector is inconsistent with the modification level of installed changes affecting the same component (see Note).
0033: The version tokens of one or more changes referred to in a Request Change Control MS major vector are inconsistent with the version tokens of installed changes affecting the same component (see Note).
0034: The request will not be honored because it was canceled by the operating system at the node to which it was sent.
0035: The class code specified in a Request Change Control MS major vector for one or more changes is inconsistent with the class code specified in the local FS catalog for the same object (see Note).
0036: Access to one or more local files associated with one or more changes referred to in a Request Change Control MS major vector was denied (see Note).
0039: Queuing not supported
003A: The requested function cannot be completed because the specified adjacent node's CP Capabilities GDS variable does not indicate support for the complementary function.
003B: The number of target installation parameters in the system-specific information file exceeds the implementation limit.
003C: The number of target hardware parameters in the system-specific information file exceeds the implementation limit.
003D: The internal version of the named change file is not supported by the current target agent.
003E: The prerequest command specified in the named change file has failed.
003F: The postrequest command specified in the named change file has failed.
0040: One or more substitution tokens were unresolved within a target file specification contained in the named change file.
0041: The request-specific customization controlling the pre-change management phase specified in the named change file has failed.
0042: The request-specific customization controlling the post-change management phase specified in the named change file has failed.
0043: The request-specific customization controlling the pre-change management phase specified in the named change file was not found.
0044: The request-specific customization controlling the post-change management phase specified in the named change file was not found.
0045: One or more AIX licensed program product options have been applied or committed either outside the change management product process or as a part of another change file.
0046: One or more AIX licensed program product options are in a state in which a re-installation of the named change file should be performed.

Note: One or more reported-on token strings are used to identify these changes when the report code is carried in an SNA condition report.

0839

LU-LU Session Being Taken Down or LU Being Deactivated.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: During session-initiation processing, a session-termination request has caused the LU-LU session to be taken down.
0002: RNAA(Type 3) received for a session during the process of session deactivation. The RNAA should be retried.
0003: SSCP detected that this session should no longer exist and requested its termination. For example, a BFSESSINFO was received reporting a subject LU address that the SSCP believed already belonged to an other-domain resource.
0004: A service TP send failure was detected by the CP, causing both contention-winner and contention-loser CP-CP sessions to be deactivated. (Retired)

083A

LU Not Enabled: At the time an LU-LU session initiation request is received at the SSCP, at least one of the two LUs, although having an active session with its SSCP, is not ready to accept CINIT or BIND requests.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The PLU is not enabled.
0002: The SLU is not enabled.

083B

Invalid PCID: The received PCID for a new session or route setup procedure duplicated the PCID assigned to another session or route setup procedure, the received PCID intended as an identifier for an existing session or route setup procedure could not be associated with such an existing session or route setup procedure, or an error was detected in the format of the received PCID.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The PCID contained in CDINIT(Initiate or Queue), INIT-OTHER-CD, or CDTAKED duplicates a PCID received previously in one of these requests.
0002: The received fully-qualified PCID duplicated one assigned to another session.
0003: The received fully-qualified PCID contains a network-qualified CP name identical to that of the receiving node.
0004: The received fully-qualified PCID duplicated one assigned to another route setup procedure.
0005: The fully-qualified PCID received in BFCINIT is not assigned to an existing route setup procedure. The BFCINIT is rejected.
0006: The fully-qualified PCID received in BFCLEANUP is not assigned to an existing route setup procedure. The BFCLEANUP is rejected.

083C

Domain Takedown Contention: While waiting for a response to a CDTAKED, a CDTAKED request is received by the SSCP containing the SSCP-SSCP primary half-session. Contention is resolved by giving preference to the CDTAKED sent by the primary half-session.

083D

Dequeue Retry Unsuccessful--Removed from Queue: The SSCP cannot successfully honor a CDINIT(Dequeue) request (which specifies "leave on queue if dequeue-retry is unsuccessful") to dequeue and process a previously queued CDINIT request (for example, because the LU in its domain is still not available for the specified session), and removes the queued CDINIT request from its queue.

083E

Implementation-Defined Retry Limit Exhausted.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The implementation-defined limit on XID exchanges was exceeded before link activation completed.
0002: The implementation-defined limit on XID exchanges was exceeded before a nonactivation exchange completed.
0004: The implementation-defined limit on contention-winner CP-CP session activation attempts has been exceeded.

083F

Terminate Contention: While waiting for a response to a CDTERM, a CDTERM is received by the SSCP of the SLU. Contention is resolved by giving preference to the CDTERM sent by the SSCP of the SLU.

0840

Procedure Invalid for Resource: The received RU is not supported in the receiver for this type of resource (for example, (1) SETCV specifies boundary function support for a type 1 node but the capability is not supported by the receiving node, or (2) the PU receiving an EXECTEST or TESTMODE is not the primary PU for the target link.)

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
* 0001: Surrogate session setup failed.
| 0002: Invalid Link: A BIND was received over a subarea link,
| but the next hop is over a port that supports only HPR
| links. The receiver does not support this configuration.
0003: Invalid Link: The link to which the PU is to be added is not an SNA link. Only SNA links are supported.
0004: Invalid Link: A request that is allowed only for a nonswitched link was received for a link that is defined to the receiver as switched.
0005: Resource Not Dynamically Added: This request works only with resources that were added through dynamic reconfiguration.
0007: Resource Not Found: A Delete or Find could not be satisfied because the specified entry does not exist in the receiver's directory.
0009: RNAA(Move) was received for a resource that was added through dynamic reconfiguration; such a resource may not be moved using RNAA(Move).
000A: Procedure Invalid for Resource: A node supporting independent LUs has dialed into a subarea boundary node that does not support sessions with independent LUs.
000C: Conflicting Entry Type on Delete: The Delete request attempted to delete a home entry, i.e., one defined at the receiver by its own network operator facility (NOF).
0010: A SETCV with control vector X'43' has been received for a nonswitched resource.
0011: A dynamically added or a switched resource has not yet been activated.
0012: A request was received that is allowed only for a primary link station. The request must use the service link, and that link is defined as secondary.
0013: A CONNOUT request was received that contained an invalid X.21 call type.
0014: A CONNOUT or CONTACT was received specifying that the receiver is to designate itself as an APPN end node in XID3s that it sends to an attached APPN or LEN node, but the receiver does not support this option.
0015: An APPN session route must be calculated in two pieces (using two separate RSCVs) but it is determined that the two RSCVs identify a common node; that is, the session route passes through a given node twice.
0016: An RSCV is precalculated because the OLU or DLU was thought to be in a subarea network but it is determined (based on the RSCV) that the location of the DLU is incorrect; that is, the RSCV indicates that the DLU is in the APPN network, but the DLU is really in a subarea network, or vice versa.

0841

Duplicate Network Address: In an LU-LU session initiation request, one of the specified LUs has a duplicate network address already in use.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: The SSCP of the DLU determines that the OLU network address specified in the CDINIT request is a duplicate of an LU network address assigned to a different LU name.
0001: A duplicate SLU address is found during session initiation.
0002: A duplicate PLU address is found during session initiation.
0003: An SSCP finds a duplicate network address for the DLU on the OLU side of the gateway.
0004: An SSCP finds a duplicate network address for the DLU on the DLU side of the gateway.
0005: An SSCP finds a duplicate network address for the OLU on the OLU side of the gateway.
0006: An SSCP finds a duplicate network address for the OLU on the DLU side of the gateway.
0008: An ACTCDRM request was received that contained a network address already in use.

0842

Session Not Active.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000

SSCP-SSCP Session Not Active: The SSCP-SSCP session, which is required for the processing of a network services request, is not active; for example, at the time an LU-LU session initiation or termination request is received, at least one of the following conditions exists:

The SSCP of the ILU and the SSCP of the OLU do not have an active session with each other, and therefore INIT-OTHER-CD cannot flow.
The SSCP of the OLU and the SSCP of the DLU do not have an active session with each other, and therefore CDINIT or CDTERM cannot flow.

Note: This value is used if there is not enough data to select one of the more specific codes listed below.

0001

The session between T2.1 CPs is not active.

0002

For a session-initiation request, an SSCP does not have an SSCP-SSCP session with an SSCP in the direction of the DLU.

0003

For a session-initiation request, an SSCP does not have an SSCP-SSCP session with an SSCP in the direction of the OLU.

0004

An intermediate SSCP has lost connectivity with an SSCP in the session setup path for an LU-LU session. This sense data is used when the SSCP previously lost connectivity with one or more participating gateway nodes so that it cannot learn that the LU-LU session is ended by receiving a NOTIFY RU from a gateway node.

FFFF

The session is not active because the session initiation request has been transferred to another PLU.

0843

Required Synchronization Not Supplied: For example, a secondary LU (LU type 2 or 3) received a request with Write Control Code = Start Print, along with RQE and �CD.

0844

Initiation Dequeue Contention: While waiting for a response to a CDINIT(Dequeue), a CDINIT(Dequeue) is received by the SSCP of the SLU. Contention is resolved by giving preference to the CDINIT(Dequeue) sent by the SSCP of the SLU.

0845

Permission Rejected--SSCP Will Be Notified: The receiver has denied an implicit or explicit request of the sender; when sent in response to BIND, it implies that the secondary LU will notify the SSCP (via NOTIFY vector key X'0C') when a BIND can be accepted, and the SSCP of the SLU supports the notification. (See the X'080A' sense code for a contrasting response.)

0846

ERP Message Forthcoming: The received request was rejected for a reason to be specified in a forthcoming request.

0847

Restart Mismatch: Sent in response to STSN, SDT, or BIND to indicate that the secondary half-session is trying to execute a resynchronizing restart but has received insufficient or incorrect information.

0848

Cryptography Function Inoperative: The receiver of a request was not able to decipher the request because of a malfunction in its cryptography facility.

0849

User Names Lost: An exception condition has resulted in the loss of user names associated with the identified message unit.

084A

Presentation Space Alteration: The presentation space was altered by the end user while the half-duplex state was not-send, (�S,*R); request not executed.

084B

Requested Resources Not Available: Resources named in the request, and required to honor it, are not currently available. It is not known when the resources will be made available.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0002: Requested Resource Not Available: For dynamic reconfiguration MOVE, ADD, or ADDLIKE operation, the requested local address is already assigned to an active resource. For MOVE PU this is the DLC address; for MOVE LU, the LU local address.
0003: The application transaction program specified in the request is not available.
0004: Session Resources Unavailable: The receiver of the RNAA cannot satisfy the request for reserved session resources specified on the Assign LU Characteristics (X'30') control vector.
0005: Controller resource is not available.
6002: The resource identified by the destination program name (DPN) is not supported.
6003: The resource identified by the primary resource name (PRN) is not supported.
6031: Transaction Program Not Available--Retry Allowed: The FMH-5 Attach command specifies a transaction program that the receiver is unable to start. Either the program is not authorized to run or the resources to run it are not available at this time. The condition is temporary. The sender is responsible for subsequent retry. This sense data is sent only in FMH-7.

084C

Permanent Insufficient Resource: Receiver cannot act on the request because resources required to honor the request are permanently unavailable. The sender should not retry immediately because the situation is not transient.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: For LU 6.2, Transaction Program Not Available--No Retry: The FMH-5 Attach command specifies a transaction program that the receiver is unable to start. The condition is not temporary. The sender should not retry immediately. This sense data is sent only in FMH-7.
For non-LU 6.2, no additional information is specified.
0001: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0002: Creating Allocation Exception: The receiver is unable to create the specified data object as a result of an insufficient storage condition that occurred at allocation time. When this SNA report code is used in an SNA condition report, it is optionally accompanied by one or more structure reports that identify the allocation requests that failed.
0003: Replacing Allocation Exception: The receiver is unable to replace the specified data object as a result of an insufficient storage condition that occurred at allocation time. When this SNA report code is used in an SNA condition report, it is optionally accompanied by one or more structure reports that identify the allocation requests that failed.
0004: Reserved
0005: Reserved
0006: Data-Object Storing Exception: The receiver is unable to store the specified data object as a result of an insufficient storage condition that occurred during the storing process. When this SNA report code is used in an SNA condition report, it is optionally accompanied by one or more structure reports that identify containing the allocation requests that failed.
0007: Data-Object Classification Code Not Supported: The receiver is unable to satisfy the allocation requirements of the specified data-object classification code. When this SNA report code is used in an SNA condition report, it is accompanied by a supplemental report containing the data-object classification code that failed.
0008: Volume Not Mounted: The receiver is unable to perform the requested allocation/storing operation because the required volume is not mounted. When this SNA report code is used in an SNA condition report, it is accompanied by a supplemental report identifying the volume that was not mounted.
0009: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
hnnn: where h�8, i.e., the high-order bit in byte 2 is set to 1. The 15 low-order bits of bytes 2 and 3 contain a binary count that indexes (zero-origin) the first byte of the field found to be in error.

084D

(Retired) Invalid Session Parameters for Boundary Function.

084E

Invalid Session Parameters--PRI: A positive response to an activation request (for example, BIND) was received and was changed to a negative response because of invalid session parameters carried in the response. The LU receiving the response will send a deactivation request for the corresponding session.

084F

Resource Not Available: A requested resource is not available to service the given request.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The receiver's disk is full; therefore, a received load module cannot be stored.
0002: Security component not available: The security component required to process the request is currently not available. This sense data is sent only in UNBIND and -RSP(BIND) records.
0003: A coded graphics character set ID (CGCSID) needed to interpret the request is not supported by the receiver. When this report code is used in an SNA condition report, it is accompanied by a supplemental report containing the 2-byte CGCSID not supported.

0850

Link-Level Operation Cannot Be Performed: An IPL, dump, or RPO cannot be performed through the addressed link station because the system definition or current state of the hardware configuration does not allow it.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Link Activation Limit Reached: The specified TG was not activated because the maximum number of active link stations allowed on this port has already been reached.

0851

Session Busy: Another session that is needed to complete the function being requested on this session is temporarily unavailable.

0852

Duplicate Session Activation Request: Two session activation requests have been received with related identifiers. The relationship of the identifiers and the resultant action varies by request.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: If the RU is an ACTPU or ACTCDRM, it means that a session has already been activated for the subject destination-origin pair by a session activation request that carried a larger activation request identifier than the current request; the current request is refused.
If the RU is a BIND, it means that the BIND request was received with the same session instance identifier (in the structured subfield X'03' of the User Data field) as an active session's; the current request is refused.
0001: A second BIND has been received from a peripheral node PLU while the session was still in the activation process.
0002: A REQACTPU has been received by an SSCP that has already sent an ACTPU for the same PU.

0853

TERMINATE(Cleanup) Required: The SSCP cannot process the termination request, as it requires cross-domain SSCP-SSCP services that are not available. (The corresponding SSCP-SSCP session is not active.) TERMINATE(Cleanup) is required.

0854

Retired

0855

Route Setup Procedure Failure: An intermediate or destination node was unable to successfully complete the processing of a high-performance routing (HPR) Route Setup request or reply.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The destination LU is not ready to accept sessions.
0002: An unknown destination LU was specified in the request.
0003: A TG specified in the RSCV could not be activated.
0004: An unknown TG was specified in the RSCV.
0005: A TG specified in the RSCV has failed.
0006: A TG specified in the RSCV was not activated as an HPR TG.
0007: An intermediate node had insufficient storage to activate a TG specified in the RSCV.
0008: The receiving node had insufficient storage to process the Route Setup request.
0009: The Route Setup request was received over a TG that was not activated as an HPR TG.
000A: A VR within a composite network node is inoperative.
000B: The receiving node does not support HPR protocols.
000D: The Route Setup request or reply could not be forwarded over the TG in the FID2 format because its size was greater than the TG's maximum BTU size.
000E: The value of the Current Hop Count field of the RSCV received in a Route Setup request exceeded the value of the Destination Hop Index field in the request (i.e., the Route Setup request appeared to have passed the destination node.)
000F: The Route Setup reply was not received in the allotted time (i.e., the Route Setup timer expired).
0020: The intended destination was not able to perform the RTP function (e.g., it does not support the RTP option set).

0856

SSCP-SSCP Session Lost: Carried in the Sense Data field in a NOTIFY (Third-Party Notification vector, X'03') or -RSP(INIT_OTHER) sent to an ILU to indicate that the activation of the LU-LU session is uncertain because the SSCP(ILU)-SSCP(OLU) session has been lost. (Another sense code, X'0842', is used when it is known that the LU-LU session activation cannot be completed.)

0857

SSCP-LU Session Not Active: The SSCP-LU session, required for the processing of a request, is not active; for example, in processing REQECHO, the SSCP did not have an active session with the target LU named in the REQECHO RU.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The SSCP-SLU session is in the process of being reactivated.
0002: The SSCP-PLU session is inactive.
0003: The SSCP-SLU session is inactive.
0004: The SSCP-PLU session is in the process of being reactivated.
0005: The SSCP lost connectivity with the PLU after the LU-LU session was started, and has no other way to learn that the session has ended; the SSCP either never had a session to a gateway node in the LU-LU session path, or had previously lost connectivity to it.
0006: The SSCP lost connectivity with the SLU after the LU-LU session was started, and has no other way to learn that the session has ended; the SSCP either never had a session to a gateway node in the LU-LU session path, or had previously lost connectivity to it.
0007: The selected ALS for the OLU is not in a state permitting LU-LU sessions to be established using it. The condition is detected when the session request (BFINIT) was received, but, when the request was processed, the ALS was no longer in an active state. The session request is rejected.
0008: The selected ALS for the DLU is not in a state permitting LU-LU sessions to be established using it. The condition is detected when the session request was being processed in the DLU domain and the ALS selected for the DLU is no longer in an active state. The session request is rejected.

0858

SSCP-SSCP Session Activation Rejected.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: An SSCP rejects a received ACTCDRM attempting to restart a session that terminated as a result of an operator-initiated nondisruptive deactivation request.

0859

REQECHO Data Length Error: The specified length of data to be echoed (in REQECHO) violates the maximum RU size limit for the target LU.

085A

Specific Server Exception: An architecturally defined or user-defined server that is sensitive to data object contents, has detected an exception.

085B

Unknown Resource Name: The identified resource, required to complete the requested unit-of-work, is not known to the SNA node.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Unknown server name. When this SNA report code is used in an SNA condition report, it is accompanied by a supplemental report containing the server name.
0002: Unknown agent.
0003: The clock identifier specified in an MS Set Clock major vector is unknown to the receiver.
0004: The timing source name specified in an MS Set Clock major vector is unknown to the receiver.
0005: The agent unit-of-work correlator referred to by an MS Cancel major vector is unknown to the receiver, or represents a unit of work already completed.
0006: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.

085C

System Exception: The node experiences an exception condition within a resident system or subsystem that inhibits subsequent processing by the SNA component.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The exception is identifiable as a system-related problem.
0002: The exception is identifiable as a permanent system-related problem.
0003: The system has logged additional information that should be used when reporting this defect.

085D

MU-ID Could Not Be Accepted in the MU-ID Registry.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0001: The MU-ID is a duplicate. When this SNA report code is used in an SNA condition report, it is accompanied by three supplemental reports that identify information about the receiver's MU-ID registry: supplemental report 1 contains the lowest MU-ID the receiver would accept; supplemental report 2 contains the highest MU-ID the receiver would accept; supplemental report 3 contains the time stamp of the receiver's MU-ID registry.
0002: The MU-ID value is greater than expected. When this SNA report code is used in an SNA condition report, it is accompanied by three supplemental reports that identify information about the receiver's MU-ID registry: supplemental report 1 contains the lowest MU-ID the receiver would accept; supplemental report 2 contains the highest MU-ID the receiver would accept; supplemental report 3 contains the time stamp of the receiver's MU-ID registry.
0003: A temporary condition prevents acceptance of the MU-ID.
0004: A permanent condition prevents acceptance of the MU-ID.
0005: The MU-ID registry is not initialized.

085E

Operator Intervention

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The operator has suspended the transmission of the message unit.
0002: The operator has purged the message unit.

0860

Function Not Supported--Continue Session: The function requested is not supported; the function may have been specified by a request code or some other field, control character, or graphic character in an RU.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

nnnn: Bytes 2 and 3 contain a 2-byte binary count that indexes (0-origin) the first byte in which an error was detected. This sense data is used to request that the session continue, thereby ignoring the error.

0861

Invalid COS Name: The class-of-service (COS) name, either specified by the ILU or generated by the SSCP of the SLU from the mode table is not in the "COS name to VR identifier list" table used by the SSCP of the PLU.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: COS name was generated by the SSCP.
0001: COS name was generated by the ILU.
0002: The COS name generated by the T2.1 CP local to, or the T2.1 NNCP server for, the ILU is not in the COS name definition table.
0003: The CDINIT request or response contains a Session Initiation (X'14') control vector that has Class-of-Service (COS) Name fields that have not been properly specified.

0862

Medium Presentation Space Recovery: An error has occurred on the current presentation space. Recovery consists of restarting at the top of the current presentation space. The sequence number returned is of the RU in effect at the top of the current presentation space.

nnnn: Bytes 2 and 3 following the sense code contain the byte offset from the beginning of the RU to the first byte of the RU that is displayed at the top of the current presentation space.

0863

Referenced Local Character Set Identifier (LCID) Not Found: A referenced character set does not exist.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code appplies.
hnnn: where h�8, i.e., the high-order bit in byte 2 is set to 1. The 15 low-order bits of bytes 2 and 3 contain a binary count that indexes (0-origin) the first byte of the field found to be in error.

0864

Function Abort: The conversation was terminated abnormally. Other terminations may occur after repeated reexecutions; the request sender is responsible to detect such a loop.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000

For LU 6.2, Premature Conversation Termination: The conversation is terminated abnormally; for example, the transaction program may have issued a DEALLOCATE_ABEND verb, or the program may have terminated (normally or abnormally) without explicitly terminating the conversation.

For LU 6.2 half-duplex conversations, this sense data is sent only in FMH-7 or UNBIND.

For LU 6.2 full-duplex conversations, this sense data is sent also in the negative response that precedes an FMH-7 when there is a chain to respond to. The sense data in the negative response results in advance notice to the transaction program (in the form of an error return code) that an ERP message is forthcoming. For this error, the ERP message will contain the same sense data value used in the negative response.

For non-LU 6.2, no additional information is specified.

0001

System Logic Error--No Retry: A system logic error has been detected. No retry of the conversation should be attempted.

For LU 6.2 half-duplex conversations, this sense data is sent only in FMH-7 or UNBIND.

0002

Excessive Elapsed Time--No Retry: Excessive time has elapsed while waiting for a required action or event. For example, a transaction program has failed to issue a conversation-related protocol boundary verb. No retry of the conversation should be attempted.

For LU 6.2 half-duplex conversations, this sense data is sent in UNBIND when there is no chain to respond to; otherwise, it is sent in FMH-7.

For LU 6.2 full-duplex conversations, this sense data is sent also in the negative response that precedes an FMH-7. The sense data in the negative response results in advance notice to the transaction program (in the form of an error return code) that an ERP message is forthcoming. For this error, the ERP message will contain the same sense data value used in the negative response.

0003

Allocation Error Message Forthcoming: An error has been detected in a received Attach request, resulting in a rejection of the Attach. The sense data value that indicates the reason for rejection will be specified in a forthcoming FMH-7.

This sense data is sent in the negative response that precedes an allocation error FMH-7 for an LU 6.2 full-duplex conversation. The negative response results in advance notice to the transaction program (in the form of an error return code) that an ERP message is forthcoming.

Note: The phrases following the sense data are symbolic return codes provided to a full-duplex transaction program when a negative response with sense data is received by the LU. (See SNA Transaction Programmer's Reference Manual for LU Type 6.2 for full-duplex verbs and their possible return codes.)

08640000: ERROR_INDICATION (with a subcode of DEALLOCATE_ABEND_PROG)
08640001: ERROR_INDICATION (with a subcode of DEALLOCATE_ABEND_SVC)
08640002: ERROR_INDICATION (with a subcode of DEALLOCATE_ABEND_TIMER)
08640003: ERROR_INDICATION (with a subcode of ALLOCATION_ERROR)

0865

Retired

0866

Retired

0867

Sync Event Response: Indicates a required negative response to an (RQE,CD) synchronizing request.

0868

No Panels Loaded: Referenced format not found because no panels are loaded for the display.

0869

Panel Not Loaded: The referenced panel is not loaded for the display.

086A

Subfield Key Invalid: A subfield key in an MS subvector was not valid in the conditions under which it was processed.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

nnmm: Byte 2 following the sense code contains the subvector key (nn) of the subvector containing the unrecognized subfield, and byte 3 contains the unidentified subfield key (mm).

086B

Subfield Value Invalid: A value in a subfield within a control vector or an MS major vector is invalid for the receiver.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

nnmm: Byte 2 following the sense code contains the key (nn) of the control vector or the MS subvector containing the subfield with the invalid value, and byte 3 contains the subfield key (mm) of the subfield with the invalid value.

Note: See sense code X'0870' for the case in which the invalid value occurs in an unformatted subvector, that is, one not containing subfields with keys and lengths, or in the unformatted portion of a partially formatted subvector.

086C

Required Control Vector or Subvector Missing: One or more control vectors or MS subvectors that are required by the receiver to perform some function are missing from the received message, or are not present in the required position.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

nn00: Byte 2 following the sense code contains the key (nn) of one of the control vectors or subvectors that is missing, or improperly positioned. Byte 3 is reserved (00).

Note: See the X'080C0006' sense data for the case in which the major vector key is recognized but a subvector representing the function to be performed cannot be identified.

086D

Required Subfield Missing: A control vector or MS subvector lacks one or more subfield keys that are required by the receiver to perform the function requested.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

nnmm: Byte 2 following the sense code contains the key (nn) of the subvector or control vector lacking a required subfield, and byte 3 contains the subfield key (mm) of a missing subfield.

086E

Invalid Subvector Combination: Two or more subvectors, each permissible by itself, are present in a combination that is not allowed.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

nnmm: Bytes 2 and 3 following the sense code contain the subvector keys (nn) and (mm) of two of the subvectors that should not be jointly present.

086F

Length Error: A length field within a structure is invalid, or two or more length fields are incompatible.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The MS major vector length is incompatible with the RU length.
0002: The sum of the MS subvector lengths is incompatible with the MS major vector length.
nn03: The sum of the subfield lengths in a MS subvector is incompatible with the subvector length. Byte 2 following the sense code contains the subvector key (nn).

nn05: MS subvector length invalid. Byte 2 following the sense code contains the relevant subvector key (nn). (This is specified only if the sum of the subvector lengths is compatible with the major vector length.)
nn06: Subfield length invalid. Byte 2 following the sense code contains the subvector key (nn) of the MS subvector containing the invalid subfield length. (This is specified only if the sum of the subfield lengths is compatible with the subvector length.)
0007: The length field of an MDS_MU is incompatible with the sum of the lengths of the imbedded GDS variables or an invalid length was found in an imbedded structure (or GDS variable).
0008: The length field of a CP-MSU is incompatible with the sum of the lengths of the imbedded structures.
nn09: The sum of the subfield lengths in a control vector is incompatible with the control vector length. Byte 2 following the sense code contains the control vector key (nn).
000A: The length field of a Route Setup GDS variable is incompatible with the sum of the lengths of the imbedded structures.
000B: The sum of the control vector lengths in an RU or XID is incompatible with the length of the RU or XID.
nn0C: The length field of a control vector in an RU or XID is invalid. Byte 2 following the sense code contains the control vector key (nn).

0870

Unformatted Subvector Value Invalid: A value in an unformatted MS subvector, or in an unformatted portion of a partially formatted MS subvector, is invalid.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

nnxx: Byte 2 following the sense code contains the subvector key (nn) of the MS subvector containing the invalid value. Byte 3 contains a one-byte binary count that indexes the first byte in which the invalid value falls. The indexing is zero-origin, from the beginning of the subvector.

Note: See sense code X'086B' for the case in which the invalid value occurs in a formatted MS subvector, that is, one containing subfields with keys and lengths, or in the formatted portion of a partially formatted subvector.

0871

Read Partition State Error: A Read Partition structured field was received while the display was in the retry state.

0872

Explicit or Implied Orderly Deactivation Refused

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: An NC_DACTVR(Orderly) request has been received, but sessions are assigned to the VR and it will not be deactivated.
0001: An MS major vector specifying or implying orderly deactivation of the receiving node has been received, but the node is not in a quiesced state and deactivation is not allowed; the requested action will not proceed.
0002: An MS major vector specifying or implying orderly deactivation of the receiving node has been received, but the receiver cannot determine if a quiesced state has been attained; the requested action will not proceed.

0873

Virtual Route Not Defined: No ERN is designated to support this VRN.

0874

ER Not in a Valid State: The ER supporting the requested VR is not in a state allowing VR activation.

| Bytes 2 and 3 following the sense code contain sense-code
| specific information. Settings allowed are:

| 0000: No specific code applies.
| 0001: A gateway node (GWN) received an RNAA from a gateway
| SSCP but either (1) no operative ER exists in the
| network adjacent to the GWN on the origin NAU's side
| to the subarea containing the origin NAU's address,
| or (2) no operative ERs exist at all in the network
| adjacent to the GWN on the destination NAU's side.

0875

Incorrect or Undefined Explicit Route Requested: The reverse ERNs specified in the NC-ACTVR do not contain the ERN defined to be used for the VR requested, or the ERN designated to be used for the VR is not defined.

0876

Nonreversible Explicit Route Requested: The ERN used by the NC-ACTVR does not use the same sequence of transmission groups (in reverse order) as the ERN that should be used for the RSP(NC-ACTVR).

0877

Resource Mismatch: The receiver of a request has detected a mismatch between two of the following: (1) its definition of an affected resource, (2) the actual configuration, and (3) the definition of the resource as implied 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

Link Defined as Switched Is Nonswitched: A link defined to an ACTLINK receiver as being switched was found to be nonswitched during the activation attempt.

0002

Link Defined as SDLC Is Non-SDLC: A link defined to an ACTLINK receiver as being SDLC was found to be non-SDLC during the activation attempt.

0003

Link Defined as Having Automatic Connect-Out Capability Does Not: A link defined to an ACTLINK receiver as having automatic connect-out capability was found to lack it during the activation attempt.

0004

ACTLINK Received for a Resource Other Than a Link: An ACTLINK was received that resolved to a local device address representing a device other than a link.

0005

Link defined as X.21 is not X.21.

0006

Link defined as LPDA-capable is configured in NRZI mode.

0007

A request that is allowed only for a primary link station was received for a link station that is defined to the receiver as secondary.

0008

A request for link problem determination for modems was received for a link that is defined to the receiver as not supporting link problem determination for modems.

0009

A request for link problem determination for modems was received for a link that is defined to the receiver as supporting link problem determination for modems, but no link station or resource supporting link problem determination for modems was found on the link.

000A

A request that is allowed only for a nonswitched link was received for a link that is defined to the receiver as switched.

000B

A request that is allowed only for a link with a modem not using the multiplexed links feature was received for a link that is defined to the receiver as having a modem using the multiplexed links feature.

000C

Resource Definition Mismatch for Modems: A request that is allowed only for a link with a nontailed modem was received for a link that is defined to the receiver as having a tailed modem.

000D

The sending SSCP and the receiving T4 node have conflicting system definitions. A BIND has been received for an LU address that is currently being used by an active LU-LU session. The LU address is primary on this active session. The LU address cannot be used for a secondary role on a new session.

000E

The sending SSCP and the receiving T4 node have conflicting system definitions. A BIND has been received for an independent LU, but the LU specified is not in a T2.1 node.

000F

The sending SSCP and the receiving T4 node have conflicting system definitions. The SSCP owner is the same as the SSCP sending the nonactivation CONTACT PIU, but the node to be contacted is not a T2.1. The CONTACT is for a T2.1 node, but the node to be contacted is not defined as a T2.1 node to the receiver.

0010

The BFCLEANUP is for an independent LU, but the LU specified is not an independent LU.

0011

The subarea address portion of an addressed LU is not equal to the subarea address of the T4 node. The LU is not in the same subarea as the T4 node.

0012

A BFCLEANUP is for a resource that is not a BF LU, and hence the request is rejected. This is a situation where the function is not supported by the target resource. It can be caused by a system definition mismatch between the T4 node and the SSCP.

0013

The network ID in the BIND SLU name is not equal to the network ID of the boundary function, or the SLU name is not equal to the LU name in the boundary function control block for the LU, or the network ID in the BIND SLU name is not equal to the LU network ID in the boundary function control block for the LU.

0014

The LU specified in the FNA is not associated with the PU specified in the FNA; that is, an LU address (bytes 7-n) is not associated with the PU target address specified.

0015

BFCINIT Name Mismatch: The BIND cannot be built from the BFCINIT because the network-qualified PLU name does not match. The session activation is rejected by the boundary function with a BFTERM.

0016

Invalid Target Address: Either of the following conditions holds:

The PU with which the specified LUs are to be associated is not type 1 or type 2; i.e., the SSCP attempts to add an LU to a PU, but the boundary function has defined that PU as a type 4.
The SSCP sent an RNAA assignment type X'0' or X'5' with a PU or LU specified instead of a link. This is caused by a definition mismatch.

0017

An entire network address including subarea and element is required for pre-ENA address assignment: If an entire network address is not specified and an RNAA requesting a pre-ENA address is received, the RNAA is rejected.

0018

An RNAA type 4 was received requesting an auxiliary address on a dependent LU.

| 0019

Multiple sets of DLC signaling information were received
| for an ATM port, but ATM supports only one set of DLC
| signaling information.

001A

The target LU specified in BFCLEANUP or BFCINIT is not associated with the same link station that is associated with the session indicated in the URC control vector.

001B

The target link station specified in a BFCLEANUP is not the same link station as the session indicated in the URC control vector.

001C

Resource Definition Mismatch for BFCINIT: The sending SSCP and the receiving T4 node have conflicting system definition. A BFCINIT has been received for an LU address that is currently being used by an active LU-LU session. The LU address is primary on this already active session. The LU address cannot be used for a secondary role on a new session.

001D

The LU address in the BFCINIT is a secondary address; the BFCINIT is rejected.

001E

The subject LU specified in the BFSESSINFO RU is not defined to the SSCP as an independent LU; this is a mismatch between the SSCP and the BF.

001F

A dependent LU is attached to a PU that indicates ACTPU is to be suppressed; the SSCP cannot activate the LU because ACTLU is not supported.

0020

A peripheral node supporting independent LUs has received an ACTLU request for an LU. This request is rejected, as an independent LU does not support ACTLU.

0021

An RNAA(Add) was received by the boundary function for a resource defined at system definition time, which is not allowed.

0022

The link for which ACTLINK was issued is a S/390 channel that has been defined for connections only to a T2.1 node. However, the SSCP that sent ACTLINK had previously indicated it does not support T2.1 connections.

0023

Modem test support cannot be changed. The RNAA or SETCV containing the SDLC Secondary Station (X'03') or the Extended SDLC Secondary Station (X'43') control vector is rejected.

0024

The data mode cannot be changed. The RNAA or SETCV containing the SDLC Secondary Station (X'03') or the Extended SDLC Secondary Station (X'43') control vector is rejected.

0025

The receiving node is unable to process a BIND for the LU type specified for the given LU name.

| 0026

Link Definition Error: A link is defined as not
| supporting HPR, but the port only supports HPR links.

0027

A link connection request for a nonempty active link connection configuration was received by the management services element; the active link connection configuration of the DLC element is empty; i.e., it has no link connection components present.

0028

An RNAA(Move) was received for a link station, and the link station's primary-secondary role is incompatible with the target link.

0029

The RU refers to a resource, and the sender and receiver disagree about its status. One considers it a static resource, the other a dynamic resource.

002A

A session cannot be activated because the node does not support segment generation and the maximum link BTU size is too small to satisfy a requirement on the minimum send RU size as defined for the session mode.

002B

A session cannot be activated because the node does not support segment reassembly and the maximum link BTU size is too small to satisfy a requirement on the minimum receive RU size as defined for the session mode.

002C

A BFINIT session request was received from a PLU that is not in the same network as this SSCP, or a BFSESSINFO was received reporting a subject LU in another network.

002D

BFSESSINFO was received for an independent subject LU, but the reported LU is considered by the receiver as a dependent LU.

002E

BFSESSINFO was received reporting a dynamic subject LU that the receiver considers to be located under a different ALS from that reported in the BFSESSINFO. The SSCP will attempt to correct this configuration mismatch.

002F

BFSESSINFO was received reporting a subject LU that the receiver considers to be located under a different ALS from that reported in the BFSESSINFO. The SSCP cannot correct this configuration mismatch.

0030

BFSESSINFO was received for a subject LU, but the receiver has the address associated with a different LU, which it considers to be static.

0031

BFSESSINFO was received for a subject LU, but the receiver has the address associated with anything other than a static LU or an other-domain resource.

0032

BFSESSINFO was received for a subject LU that is verified, but, for a given session, either the partner LU is reported as the primary and the receiver does not consider that LU to be primary-capable, or the partner LU is reported as the secondary and the receiver does not consider that LU to be secondary-capable.

0033

Upon receipt of BFSESSINFO, the receiver considers the control block associated with a partner LU to be an other-domain resource that is not active or an application program that is not active.

0034

Upon receipt of BFSESSINFO, an SSCP is unable to associate the information received about a partner LU to be associated with an LU, an other-domain resource, or an application program.

0035

A network address was returned in RSP(RNAA) that the receiver believes is already associated with a different resource.

0036

BFSESSINFO received containing an invalid ALS address. For example, the ALS does not represent a T2.1 node.

0037

BFSESSINFO received for a subject LU, where the secondary address specified in the BFSESSINFO does not match the secondary address the SSCP believes is associated with the LU.

0038

The subject LU specified in the BFSESSINFO RU is not defined to the SSCP as an LU or an other-domain resource.

0039

A request that is valid only for a switched subarea link was received for a link that is not subarea-capable.

003A

A request that is valid only for a nonswitched subarea link was received for a subarea dial link.

003B

An RNAA(Add) was received for an LU; however, an LU with the same name but a different local address already exists under the specified ALS.

0041

Takeover processing completed, but the SSCP did not receive a BFSESSINFO for a resource that the SSCP believed to be a static, independent LU.

0042

A BFINIT session request was received from a PLU that is not controlled by this SSCP.

0043

A request was received for a nonswitched resource that is valid only for a switched resource.

0044

A CONNOUT requested X.21 dial and auto-call capability was not present; resource mismatch.

0045

The DLU for a session request specified a network ID that did not match the network ID for the ALS providing services for the session.

0046

A CONNOUT was received indicating the sender and receiver have a system-definition mismatch: the CONNOUT Connection Type field specified a nonswitched link, but the receiver does not define the affected node as a T2.1 node on a nonswitched link or as one that supports XID3 exchange.

0047

The OLU for a session request or subject LU for a BFSESSINFO specified a network ID that did not match the network ID for the ALS providing services for the session.

0048

The DLU is an independent LU but the boundary function selected to provide its services is not capable of supporting independent LUs. The condition detected during session initiation processing after the ALS was selected for a switched resource.

0049

During processing of a BFSESSINFO for a subject LU, that LU was found to be inactive.

0050

The element address of an intra-FRSE PVC segment subport specified in a SETCV resides on the same frame-relay port as another subport within a subport set.

0051

The maximum frame size in the system-definition differs for any two partners in an intra-FRSE PVC segment subport set specified in a SETCV.

0052

Adjacent frame-relay equipment management protocols are not supported on either of the frame-relay ports for the primary or its backup subport specified in the SETCV for the intra-FRSE PVC segment subport set.

* 0054

SETCV was received to define an intra-FRSE segment subport
* set between subports that are incompatible: one of the
* subports does not support alternate physical paths.

* 0055

SETCV was received to define an intra-FRSE segment subport
* set between subports that are incompatible: one of the
* subports is on an outboard DLC and the other is not on an
* outboard DLC.

0056

A CPSVRMGR session cannot be established over a LEN connection that is not of type TCP.

* 0057

An RNAA(Type=X'05') requested the addition of an Internet
* Protocol (IP) PU to a frame-relay line that does not
* support IP traffic.

* 0058

A request was received for either an intra-FRSE segment
* subport set or a subport in a set, and the subport set
* contains incompatible subports: one of the subports is on
* an outboard DLC and another is not. A microcode-level
* upgrade is required to support this configuration.

0059

The same signaling information subfield has been received in a FID2 Encapsulation GDS variable from both the DLUR and DLUS, but the subfields have different values, and the DLUR cannot reconcile the differences.

005A

The same signaling information subfield has been received in a FID2 Encapsulation GDS variable from both the DLUR and DLUS, but the subfields have different values, and the DLUS cannot reconcile the differences.

0878

Insufficient Storage: The storage resource required for a data format is not available.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: CONNOUT contained more dial digits than can be stored by the receiving product.

0879

Storage Medium Exception: An exception has occurred involving a storage medium.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Disk I/O error.
0002: A nonrecoverable I/O exception has been encountered.
* 0003: Automatic DUMP/RE-IPL switches not saved to disk.

087A

Format Processing Error: A processing error occurred during data formatting.

087B

Resource Unknown: The request contains a session key that does not identify a session known to some gateway node; for example, a session activation request arrives at a gateway node after it has released the address transform for the intended session.

087C

SSCP-PU Session Not Active: For example, a gateway SSCP-PU session that is needed to establish an address transform for a requested cross-network LU-LU session was not active.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: An SSCP in the session setup path for an LU-LU session has lost connectivity with a gateway node traversed by the session, and has no other way to learn that the session has ended. An intermediate SSCP sends this sense data to one adjacent SSCP when it had previously lost connectivity with the other adjacent SSCP on the same session setup path. An endpoint SSCP sends this sense data to its adjacent SSCP when it had previously lost connectivity to a dependent LU or the boundary function of an independent LU.
0002: The SSCP lost connectivity with the boundary function of an independent PLU after the LU-LU session was started, and has no other way to learn that the session has ended; the SSCP either never had a session to a gateway node in the LU-LU session path, or had previously lost connectivity to it.
0003: The SSCP lost connectivity with the boundary function of an independent SLU after the LU-LU session was started, and has no other way to learn that the session has ended; the SSCP either never had a session to a gateway node in the LU-LU session path, or had previously lost connectivity to it.

087D

Session Services Path Error: A session services request cannot be rerouted along a path of SSCP-SSCP sessions. This capability is required, for example, to set up a cross-network LU-LU session.

Bytes 2 and 3 contain sense code specific information that indicates the specific reason for not rerouting the request. Settings allowed are:

0000: No specific code applies.
0001: An SSCP has attempted unsuccessfully to reroute a session services request to its destination via one or more adjacent SSCPs; this value is sent by a gateway SSCP when it has exhausted trial-and-error rerouting.
Note: This code is used when SSCP rerouting fails completely. The remaining codes are used for failures to reroute to a particular SSCP. For example, they are associated with specific SSCPs when information about a rerouting failure is displayed in the node that was trying to reroute.
0002: An SSCP is unable to reroute a session services request because a necessary routing table is not available, that is, there is no adjacent SSCP table corresponding to the rerouting key in the Resource Identifier control vector. The receiver of this value will, if possible, try rerouting to another SSCP.
0003: This SSCP has no predefinition for an LU, but an adjacent SSCP does not support dynamic definition in partner SSCPs. As a result, this SSCP cannot both dynamically define the LU and reroute to that adjacent SSCP.
0004: A conflict in gateway definition or capabilities has been detected during cross-network session establishment.
0005: (Retired) An SSCP is unable to use the gateway node specified in CDINIT because that gateway node cannot allocate an address transform for the intended cross-network LU-LU session.
0006: (Retired) An SSCP is able to use only a subset of the alternate gateway nodes available to it. However, for the subset that it can use, none can provide the needed alias address pair.
* 0007: Sessions services path error: Two resources have been
* defined to represent the real and alias cross-domain
* resources.
0008: The adjacent SSCP does not support the requested CDINIT function (for example, notification of resource availability or XRF).
* 0009: A gateway SSCP is unable to reroute a CDINIT request: An
* address assigned by a gateway node duplicated an address
* assigned to a different LU name.
000A: An SSCP is unable to reroute a session services request because the request has been routed through the same SSCP twice.
000B: The DLU specified in the CDINIT is unknown to the receiving SSCP, and the receiving SSCP cannot reroute the CDINIT.
000D: An SSCP has purged a session services request because the adjacent SSCP did not respond to the request within a specified installation-defined time limit.

087E

SSCP Visit Count Exceeds Limit: The SSCP visit count specified in the session services request -- CDINIT, INIT_OTHER_CD, or DSRLST -- has been decremented to 0. The session services request has been routed through an excessive number of SSCPs. (The SSCPs are not necessarily distinct.)

087F

Session Services Path Error: A session services request cannot be rerouted into an APPN or subarea network.

Bytes 2 and 3 contain sense code specific information that indicates the specific reason for not rerouting the request. Settings allowed are:

0000: No specific code applies.
0001: A Locate/CD-Initiate reply, indicating Resubmit on Directed Search, was received after a directed search had been performed in response to a previous Locate/CD-Initiate reply.
0002: Duplicate or invalid search request received.
0003: A subarea search was not routed into an APPN network because a requested function was not supported by the APPN-subarea interchange node.
0004: An APPN search was not routed into a subarea network because a "search of subarea" was not permitted.
0005: A subarea search was not routed into an APPN network because the request originated in the APPN network containing the receiving node and the APPN network is capable of executing a broadcast search.
0006: A subarea search was not routed into an APPN network because a required component was not available.
0007: An interchange node received from an APPN network a Locate/CD-Initiate request that contains a control vector X'5D' (with subfield X'81') but cannot route to SSCPs in the network whose net ID is specified in that control vector because the control vector's Disjoint Network indicator is not set to 1.

0881

ACTCDRM Failure--REQACTCDRM Sent: An SSCP-SSCP session-activation request, ACTCDRM, cannot be rerouted to a gateway SSCP because, at some gateway PU, the necessary transform is not complete and the gateway PU has sent REQACTCDRM to the gateway SSCP.

0882

Insufficient Resource -- Additional Control Block Information Included: The NCP receiver cannot act on the request because of a condition that prevents it from allocating the required control block.

Bytes 2 and 3 may contain the following sense code specific information:

ciii

A condition "c" (see below) prevents the allocation of a control block from an NCP control block pool having the control block identifier (CBID) "iii"; the "iii" values are explained in NCP/EP Reference Summary and Data Areas, LY43-0030, under the "GPACBID" field. The values of "c" have the following meanings:

1: The NCP DYNPOOL threshold for dynamically allocated resource control blocks has been reached.
2: The NCP buffer utilization is too near the slowdown threshold.
3: No network element addresses are available.
4: The NCP generation limit for the associated control block has been reached.

0884

ACTCDRM Failure--No REQACTCDRM Sent: An SSCP-SSCP session activation request, ACTCDRM, cannot be rerouted to the destination SSCP because, at some gateway node PU, the necessary transform is not complete and REQACTCDRM cannot be sent to the destination SSCP because the gateway SSCP-PU session is not active or the intended SSCP session partner does not provide gateway services.

0886

Subnetwork Rerouting Not Supported: An SSCP received a session services request--CDINIT, INIT_OTHER_CD, NOTIFY(Vector Key=X'01'), or DSRLST--from an SSCP in its subnetwork that, if rerouted, would not cross a subnetwork boundary. The SSCP does not support rerouting within a subnetwork.

0887

Dequeue Retry Unsuccessful--Session Remains Queued: The SSCP cannot successfully honor a CDINIT(Dequeue) request. The request specifies "leave on queue if dequeue-retry is unsuccessful." The SSCP has left the queued session on its queue.

0888

Name Conflict: A name specified in an RU conflicts with a previous usage, or is unknown, or is known and does not have the required capabilities, or is a duplicate resource for the specified resource type. When a name conflict is detected, further name checking ceases; multiple name conflicts are not reported or detected.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The specified DLU real network name is known, but identifies a resource that is not LU-LU session capable.
0002: The specified DLU alias network name is known, but identifies a resource that is not LU-LU session capable.
0003: The specified OLU real network name is known, but identifies a resource that is not LU-LU session capable.
0004: The specified OLU alias network name is known, but identifies a resource that is not LU-LU session capable.
0005: Name translation was invalid; that is, a different LU name was returned with the same network ID as the original LU name.
0006: The specified DLU real network name is known, but is a duplicate resource.
0007: The specified DLU alias network name is known, but is a duplicate resource.
0008: The specified OLU real network name is known, but is a duplicate resource.
0009: The specified OLU alias network name is known, but is a duplicate resource.
000B: A cross-network DLU name is defined as a shadow resource, but shadow resources are not supported for cross-network sessions.
000C: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
000D: When processing a session initiation RU, an SSCP has found two different resource definitions for the OLU, one with the real OLU name and one with the alias OLU name.
000E: When processing a session initiation RU, an SSCP has found two different resource definitions for the DLU, one with the real DLU name and one with the alias DLU name.
000F: The specified DLU network name is defined as a generic resource. The session should be reinitiated using the name of an LU.
0010: The LU6.2 partner returned a name in the User Data field of its RSP(BIND) that differs from the name it returned in the User Data field of its RSP(BIND) for a previous BIND. Either the partner changed its name or name changes in the network have caused delivery of the latest BIND to a different partner.
0011: The LU6.2 partner receiving a BIND carrying one specific target SLU name returned a name in the User Data field of its RSP(BIND) that is the same as it returned in response to a previous BIND carrying a different target SLU name. Name changes in the network name allowed two names to resolve to the same LU.
0012: The network qualifier of the name returned in the User Data field of a RSP(BIND) is not equal to the network identifier provided by the application that is using network qualified names. Name changes in the network have caused alteration of the network identifier.
0013: A border node received a Topology Database Update from a node within its native subnet containing the CP name of a node that is adjacent to the border node across an intersubnet TG, i.e., in a nonnative subnet.
| 0015: A generic name of a resource has been received when only
| the real name of the resource can be specified.
0016: The DLUR-specified network name is known but is a duplicate resource.

0889

Transaction Program Error: The transaction program has detected an error.

This sense code is sent only in FMH-7.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: Program Error--No Data Truncation: The transaction program sending data detected an error but did not truncate a logical record.
Program Error--Purging: The transaction program receiving data detected an error. All remaining information, if any, that the receiving program had not yet received, and that the sending program had sent prior to being notified of the error, is discarded.
0001: Program Error--Data Truncation: The transaction program sending data detected an error and truncated the logical record it was sending.
0100: Service Transaction Program Error--No Data Truncation: The service transaction program sending data detected an error and did not truncate a logical record.
Service Transaction Program Error--Purging: The service transaction program receiving data detected an error. All remaining information, if any, that the receiving service transaction program had not yet received, and that the sending service transaction program had sent prior to being notified of the error, is discarded.
0101: Service Transaction Program Error--Data Truncation: The service transaction program sending data detected an error and truncated the logical record it was sending.

088A

Resource Unavailable--NOTIFY Forthcoming: The SSCP cannot satisfy the request because a required resource is temporarily unavailable. When the required resource becomes available, NOTIFY NS(s) key X'07' or X'08' will be sent.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: SSCP-SSCP Session Not Active: A SSCP-SSCP session required to reroute the cross-network request was not active.
0003: SSCP-LU session not active: The SSCP(DLU) is currently not in session with the DLU.
0004: LU session limit exceeded: The DLU is currently at its session limit and the requested session would cause the limit to be exceeded.

088B

BB Not Accepted--BIS Reply Requested: Sent in response to a BB (either an LUSTAT bid or an Attach) to indicate that the receiver has sent a BIS request and wishes to terminate the session without processing any more conversations, but without sending an UNBIND. A BIS reply is requested so that the negative response sender may send a normal UNBIND. This sense code is sent only by LUs not supporting change-number-of-session (CNOS) protocols.

088C

Missing Control Vector or Subfield: The RU or XID did not contain a required control vector or subfield.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

nnyy: Byte 2 contains the key (nn) of the subject control vector and byte 3 (yy) contains 0's or the control vector's type or missing subfield, if appropriate.

088D

Duplicate Network Name: An SSCP has detected a violation of the requirement that network names used across multiple domains be unique within the multiple-domain network. For example, the SSCP(DLU) has detected that the OLU name received in CDINIT is currently also defined in the domain of the SSCP(DLU).

088E

Capability Mismatch: A network component detected a capability mismatch between different resources involved in the same network function. For example, an SSCP detects that an LU has been assigned a subarea address too large for one of the other resources involved in the session initiation to support.

Bytes 2 and 3 following the sense code contains sense code specific information. Settings allowed are:

0000: A resource encountered during LU-LU session initiation is not ENA-capable; the session initiation request may be rerouted.
0001: A resource encountered during LU-LU session initiation is not ENA-capable; the session initiation request should not be rerouted.
0002: An SSCP has requested a "pre-ENA compatible" SLU address for an SLU that already has an ENA address.
0003: The gateway node selected by the gateway SSCP from the gateway node list is not ENA-capable when an ENA-capable gateway node is required. Another gateway node may be tried.
0004: During a dynamic path update, the SSCP detected that the update contained a path definition with an ER number greater than 7 and that the target node does not support extended subarea addresses. Therefore, the dynamic path update information for this destination subarea was not forwarded to the target node.
0005: The session could not be established because a specified extended subarea address exceeded that allowed at a node along the selected session setup path. The gateway SSCP doing gateway node selection may retry the session setup by selecting another gateway node having a larger subarea address limit in the network containing the DLU.
0006: The session could not be established because a specified extended subarea address exceeded that allowed at a node along the selected session setup path. The gateway SSCP doing gateway node selection may retry the session setup by selecting another gateway node that uses a smaller subarea address in the network containing the DLU.
0007: During a dynamic path update, the SSCP detected that the update contained a path definition with a subarea address above 255 and that the target node does not support extended subarea addresses. Therefore, the dynamic path update information for the destination subarea was not forwarded to the target node.
0008: The session could not be established because the dependent LU server detected an incompatibility between its capabilities and those of its dependent LU requester.
0009: The session could not be established because the dependent LU requester detected an incompatibility between its capabilities and those of its dependent LU server.
000E: VRTG is not supported across subnetwork boundaries.
000F: An attempt was made to establish a CP-SVR pipe across a subnet boundary between a dependent LU server and a dependent LU requester with limited multisubnet support.

088F

XRF Procedure Error: A request was received for an XRF-active or XRF-backup session and was not acted on.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0003: A SWITCH request specifying a switch to the already existing state was received.
0004: A SWITCH request was received that was invalid.
0005: The SLU has received SWITCH(Conditional, to backup) and no current XRF-backup sessions exist that can replace this session (that is, become the XRF-active session).
0006: An INITIATE request for an XRF-backup session was received that allowed queuing (XRF-backup and session queuing are mutually exclusive functions.)
0007: A CDINIT or INITIATE request was received specifying an XRF-backup session, and the DLU does not support XRF sessions.
0008: An XRF-active BIND was received with a session correlation identifier that duplicates a session correlation identifier associated with an existing XRF session.
0009: An XRF-backup BIND was received for an LU that currently does not have an XRF session.
000A: Cryptography Not Supported: An XRF BIND was received indicating cryptography.
000B: An INITIATE request was received specifying an XRF-backup session, but the OLU does not support XRF sessions. This is a definition mismatch between the OLU and the SSCP(OLU).
000F: An invalid XRF-backup command was received.
0010: An XRF-backup BIND was received with a session correlation identifier that does not match the session correlation identifier associated with the existing XRF session with that LU.
* 0011: Cryptography unavailable for XRF-backup session.
0012: An XRF-backup BIND associated with the existing XRF session supporting data compression was received that did not support compression.
0013: The existing session was negotiated using an extended BIND carrying the Length-Checked Compression (X'66') control vector, but the XRF-backup BIND is nonextended.

0890

Search Failure.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0010: Routing Error during a Directed Search: A Locate GDS variable for a directed search was received by an intermediate NNCP and could not be successfully routed to the destination control point.
0020: Resource Not Found during a Directed Search: A Locate GDS variable for a directed search was received by the named destination CP and the search argument resource is not a local resource.
| 0021: Resource could not be located using only the nonverify
| function and a verify Locate was not permitted as part of
| the search.
0022: Destination of search not served by this CP.
0024: A search request or BIND was received from an unauthorized end node identifying an origin LU not represented in the network node server's directory, and thus could not be authenticated.
0030: Resource Deleted, No Broadcast Required: A Locate GDS variable for a directed search was received by the named destination CP and the search argument resource has been deleted.
0037: Unknown TG Vectors to Dependent LU Requester: A resubmitted Locate search for a dependent LU at its dependent LU requester was unsuccessful. This condition arises only after the dependent LU server has verified the existence of the dependent LU; retry.
0038: Too Many Directed Search Subprocedures: A Locate search exceeded the maximum height of the search tree; too many directed search subprocedures were tried; no retry.
0040: Resource Not Found during a Broadcast Search: A Locate GDS variable for a broadcast search was received by a CP that does not provide network services for the search argument resource and neither do any of the CPs searched in its broadcast subtree. This condition is detected by crossing search requests (a CP sends and receives a search request with the same FQPCID and the same search argument resource) or by a local search failure and all CPs in the broadcast subtree returning this sense data.
0048: Neutral Reply Received from an End Node: A Locate reply with no Found and no Extended Sense Data (X'35') control vector was received from an APPN end node.
0050: Quiesced CP: A CP in the broadcast search tree is in a quiescent state and, therefore, not receiving Locate GDS variables. This condition is detected when a CP in the search subtree is quiesced and no other CP in the subtree found the requested resource.
0060: Storage Not Available: A CP in the broadcast search tree does not have sufficient storage to participate in the search and no other CP in the search subtree found the requested resource.
0070: Session Outage: A CP in the search tree has lost its CP-CP session with a CP that had been sent a Locate GDS variable and no reply had been received.
0080: Duplicate Fully Qualified PCID: A CP in the search tree detected a duplicate fully qualified PCID for a different session request from the session request that first used the fully qualified PCID.
0081: PCID Modifier Too Long: A PCID Modifier List was received that had a length greater than 10 bytes.
0082: PCID Modifier Space Exhausted: A PCID Modifier List was received that contained the maximum of 10 bytes. As the maximum list size has been reached, another list entry cannot be made that was longer than 10 bytes.

0891

Invalid or Missing Network ID.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: PLU Network ID Invalid: The network ID of the PLU is not the same as that of the SSCP(PLU).
0002: Invalid Network ID: The Network ID field in CONNOUT does not match the network ID defined for the target of the CONNOUT.
0003: Invalid network ID: The Network ID field in the RNAA is not the same as the native network ID because of a mismatch between the system definitions of the SSCP and the type 4 node.
0004: The Network Name control vector appended to the received XID3 does not contain a valid network ID. The network ID preceding the CP name must be greater than 0 and less than 8 bytes in length.
Alternatively, a network ID was received as an entry in a Register GDS variable without an accompanying resource name, resulting in an invalid resource name at the receiver; the entry was not registered.
0005: The Network Name control vector appended to the received XID3 does not contain a valid CP name. The CP name, following the network ID, must be greater than 0 and less than 8 bytes in length.
0006: Invalid Network ID: The sender has deactivated CP-CP sessions with the adjacent nonnative CP because neither CP contains border node support (i.e., neither sets byte 9, bit 7, to 1 in the CP Capabilities GDS variable that it sends).
0007: Invalid Network ID: Establishment of a switched link connection failed because the network ID of the destination PU was not equal to that of the requesting SSCP.
0008: Insufficient control blocks for dynamic network ID assignment. A CONNOUT specified a network ID that is not currently defined and sufficient control blocks are not available.
| 0009: The network ID specified in the VRID List (X'1B') control
| vector is invalid.
000A: Invalid Network ID: the network ID in the Network Name control vector does not match the network ID of the target resource of the REQACTPU.

0892

Automatic network shutdown (ANS) has occurred.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Session Reset After Loss of an SSCP: The SSCP controlling an LU has been lost. The session will be terminated because the T4 node, by system definition, terminates such sessions for this LU upon loss of the SSCP.
0002: The LU-LU session was in pending-active state when the SSCP failed. Although the T4 node, by system definition, continues an active LU-LU session upon the loss of the SSCP, the session was not completely set up, and thus it was reset.
0003: XRF-backup Session Reset. The XRF-backup session was reset because the T4 node resets the session upon loss of the SSCP.

0893

Takeover Not Complete

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: PLU Lacking a Control Point, Retry: The PLU is not currently receiving network services from a control point. The BIND is rejected because the session cannot be established. This sense data is returned by the boundary function of the PLU.
0002: SLU Lacking a Control Point, Retry: The SLU is not currently receiving network services from a control point. The BIND is rejected because the session cannot be established. This sense data is returned by the boundary function of the SLU.
0003: Sequence Error: The SSCP should not send an RNAA for an independent LU until the takeover sequence is complete for the link station, that is, until all BFSESSINFOs for that LU have been received and accepted.

0894

Migration Support Error: The sender of the request is relying on migration support that is not available.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: BIND cannot be extended: A BIND that is not an LU6.2 BIND was received and cannot be extended by the receiver.

0895

Control Vector Error: The RU or XID contained a control vector that was in error.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
xxyy: Byte 2 (xx) contains the key of the control vector first detected in error. If more than one control vector is in error, only the first erroneous one is reported. Byte 3 (yy) of the sense code specific data contains the (0-origin) byte offset of the error within the control vector.

0896

Control vector too long.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Network Name (X'0E') control vector is too long; the vector data portion is greater than 18 bytes long.

0897

System Definition Mismatch: The requested function is not supported by the receiver, or a mismatch exists between the system definitions of the sender and receiver.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

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 could also 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: Invalid SLU Name: The network ID (if present) in the 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 T4 node system definition.
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.
0007: The receiving SSCP has a system-defined name for the SSCP(DLU) that differs from the SSCP(DLU) name in the session initiation request.
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.
0009: In a gateway with three gateway SSCPs, none of which is predesignated, the gateway node believes that one is predesignated. As a result, the gateway node receives gateway control RUs such as RNAA from an unexpected SSCP.
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, two gateway SSCPs in the same gateway are both predefined to be predesignated.
000C: The receiver is unable to interpret the DLU name.
000D: Resource type not defined in receiver.
000E: Reserved
000F: Reserved
0010: An adjacent SSCP has the same SSCP name as the SSCP that controls the DLU, but a different network identifier from the DLU.
0012: The receiving SSCP has a system-defined name for the SSCP(OLU) that differs from the SSCP(OLU) name in the session initiation request.
0013: A CDINIT was received that indicated that the receiving SSCP controls the OLU.
0014: The receiving T4 node (though capable of supporting the function) was not defined by local system-definition option to support the requested dump type.
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.
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.
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 recieved 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 invalid 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.

0898

Session Reset: The XRF session is being reset.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The XRF-active session has been reset because the XRF-backup PLU forced a takeover.
0002: XRF-backup Hierarchical Reset: The identified XRF-backup LU-LU session is being deactivated because the related XRF-active session terminated normally. The LU sending this sense data is resetting its half-session before receiving the response from the partner LU. (See UNBIND type X'12'.)
0003: XRF-active Hierarchical Reset: The identified XRF-active LU-LU session is being deactivated because the related XRF-backup session performed a forced takeover of this session (via SWITCH). The LU sending this sense data is resetting its half-session before receiving the response from the partner LU. (See UNBIND type X'13'.)

089A

Invalid File or File Not Found: The requested file was not found, or was found to be an invalid file.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Requested file not found.
0002: The specified load module already exists and, therefore, cannot be added.
* 0003: An IPL time has not been set for the specified load
* module.
* 0004: Another load module on the MOSS disk has the same IPL time
* as the one specified for the load module in the Modify
* load command.
0005: Unable to locate required associated object.

089B

Session Correlation Exception: The session correlation procedure detected an exceptional condition at the SLU.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: RUs Out of Order: A BIND request with the correlating Fully Qualified PCID (X'5F') control vector arrived before UNBIND(Type X'02') was received for the correlated session. This sense data is sent in an UNBIND that terminates the correlated session.
0002: Correlator Not Found: A BIND request with the correlating Fully Qualified PCID (X'5F') control vector cannot be correlated with any previous session.

089C

Duplicate Session-Related Identifier.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Invalid URC: The URC received in a BFINIT duplicates a URC for an outstanding session initiation attempt from the same BF.

089D

Gateway Node Error Detected during Cross-Network Session Initiation.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The gateway node list used to select a gateway node to cross a network boundary is exhausted.
0003: RNAA has failed; another gateway node should be tried.
0004: Address conversion based on the subarea/element address split was unsuccessful.
0005: The gateway node selected by one gateway SSCP is not known to another gateway SSCP in the same gateway. This can be a system definition error in the gateway SSCP that does not recognize the gateway node.
0006: A gateway SSCP has found that a gateway node has assigned duplicate addresses.

089E

Identified Data Object Already Exists.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: A request to create a new data object has failed because the identified data-object already exists at the target node.
0002: A request to replace a data object has failed because it specifies a to-be-deleted data object different from the to-be-stored data object; however, the to-be-stored data object already exists.

089F

Component Not Available: The node component required to satisfy a request is not currently available.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The control point was not available for assignment of the FQPCID.
0002: Reserved
0003: The control point was not available to initialize the next TG of an LU-LU session in an intermediate network node.
| 0004: A session initiation has failed because a generic-resource
| coupling facility is unavailable to do a necessary
| information update.

08A0

Session Reset: An LU or PU is resetting an LU-LU session.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: The identified LU-LU session had to be deactivated because of a forced deactivation of the associated SSCP-PU or SSCP-LU session, for example, because of a received DACTPU, DACTLU, or DISCONTACT. The LU will send an UNBIND with a reason code of X'0A' (SSCP Gone).
0002: The LU or session connection manager (SCM) will send UNBIND with a reason code of X'0F' (Cleanup).
0003: A gateway node is cleaning up the session because a gateway SSCP has directed the gateway node (via NOTIFY) to deactivate the session, for example, a session setup error or session takedown failure has occurred. The gateway node will send UNBIND with a reason code of X'11' (Gateway Node Cleanup).
0004: Reversed FRSN Values: The value in the Last FRSN Sent field is greater than the value in the Current FRSN field in a received TDU GDS variable (no retry). The CP will send an UNBIND with a reason code of X'0F' (Cleanup)
0005: TDU Sent Out of Order: The value in the Last FRSN Sent field of the current TDU GDS variable is less than the value of the Current FRSN field in the TDU GDS variable that immediately preceded it, or is greater than it and the receiver cannot store the out-of-sequence value (no retry). The CP will send an UNBIND with a reason code of X'0F' (Cleanup)
0006: Invalid FRSN Value: In a CP Capabilities GDS variable, the adjacent node indicated receipt of a TDU with a FRSN value greater than the last one sent.
0007: DLUS-DLUR Session Deactivation (Disruptive): LU-LU sessions for DLUR-supported dependent LUs should be reset.
0008: DLUS-DLUR Session Deactivation (Nondisruptive): LU-LU sessions for DLUR-supported dependent LUs should not be reset.
0009: DLUS-DLUR Session Deactivation (Nondisruptive): Protocol violation detected; LU-LU sessions for DLUR-supported dependent LUs should not be reset.
000A: DLUS-DLUR Session Deactivation (Nondisruptive): DLUR should wait for DLUS reactivation of the DLUS-DLUR session; LU-LU sessions for DLUR-supported dependent LUs should not be reset.

08A2

Resource Active. The requested function must be performed on an inactive resource, and the resource is active.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: RNAA(Move) was received for an active resource.

08A3

Invalid Data in Control Vector.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Invalid data returned in Call Security Verification control vector.

08A4

Token-Match Exception: Partial name matching is unsuccessful during the required find or store operation. The canonical identifier involved in the exception is reported in the FS server report.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: One or more must-match tokens were not specified. When this report code is used in an SNA condition report, it is accompanied by a structure report containing the token-match indicators, as specified in the request plus a supplemental report containing the token attributes, as they appear in the report's directory.
0002: Specified token-match indicators yield multiple directory matches. When this report code is used in an SNA condition report, it is accompanied by a structure report containing the token-match indicators, as specified in the request plus a supplemental report containing the token attributes, as they appear in the report's directory.

08A6

Object Not Found: An exception has occurred when the general server attempted to process the server object, but the server object could not be found.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No additional code applies.
0001: Server object not found.

08A8

Multiple-Domain Support Routing Exception: The MDS router in the reporting NAU is unable to perform the required routing for an MDS-MU.

When this SNA report code is used in an SNA condition report (X'1532') GDS variable, the destination NAU name is included in the Reported on Location Name (X'09') subvector and the destination MS application name is included in the Reported On Agent (X'04') subvector of the condition report.

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Destination NAU name unknown. Directory services could not locate the requested destination name.
0002: Directory services unavailable. No routing possible.
0003: MS application program name not recognized.
0004: Use of CPSVCMG session not permitted. The reporting network node has received an MDS-MU over a CPSVCMG session from another network node. These sessions are used for MDS-MUs only between a network node and its served end nodes.
0005: Function not supported by EN destination. The back-level end node destination does not support receipt of MS messages (reported by serving network node).
0006: Function not supported by destination. The back-level destination does not support receipt of MS messages other than MS Capabilities and Alert.
0007: Function not supported by serving NN. The serving network node of the end node destination does not support routing of MS messages (reported by network node performing routing).
0008: Function not supported by EN. The reporting end node has received an MDS-MU with a destination other than itself.
0009: Destination not supported by reporting NN. A network node has received an MDS-MU from another network node that cannot be routed. The destination is not the reporting network node itself nor is it one of the served end nodes.
If the MDS-MU was routed based on nonverified directory information (as indicated by the Routing verification indicator in the MDS Routing Information), the MDS-MU will be returned to the routing network node along with the SNA condition report.
000A: Unrecoverable session failure. The MDS_SEND TP in the reporting node was unable to send the message because of an allocation error. Retries have been exhausted.
000B: Unrecoverable TP failure in remote node. The MDS_SEND TP in the reporting node was unable to send the message because of a TP failure in a remote node. Retries have been exhausted.
000C: MS Application program failure. The MDS router in the destination NAU is unable to communicate with the destination MS application program.
000D: Unrecoverable TP failure in reporting node. The MDS router in the reporting node was unable to send the message because of a local TP failure.
000E: Correlation error. An MDS-MU has been received that is not the first for a unit of work (First MDS Message indicator in the MDS Routing Information Message is 0), but the agent unit of work correlator is unknown (does not match any active MDS transaction). Also used to report the receipt of a duplicate correlator (MDS-MU with first MDS message indicator is 1, but the agent unit of work correlator matches one currently in use).
000F: MS application program congestion. The MDS router in the destination NAU is unable to communicate with the destination MS application program because of local congestion (implementation buffer space for queuing additional MDS-MUs has been exhausted).
0010: MDS HPO not supported by remote node. The destination NAU does not support the MDS high performance option.
0011: MDS HPO not supported by MS application program. The destination MS application program does not support the use of the MDS high performance option.
0012: Unrecoverable failure of user-mode session. MDS has detected an error on a user-mode session (a user-mode session in this context is one with a mode name other than SNASVCMG or CPSVCMG). Retries have been exhausted. Application program data may have been lost.
0013: Session UNBIND notification. The last session to the indicated destination has been deactivated. Refer to product documentation for additional information.

08A9

Multiple-Domain Support Transaction Failure: The reporting MDS router or MS application program has detected a condition that has impacted an outstanding unit of work (identified by the agent unit of work correlator of the MDS error message).

Bytes 2 and 3 following the sense code contain sense code specific information. Settings allowed are:

0000: No specific code applies.
0001: Failure caused by outage of a CPSVCMG session.
0002: Failure caused by outage of an SNASVCMG session. All retries have been exhausted.
0003: Unit of work canceled by reporting MS application program. The unit of work has been canceled because of a timeout in the reporting MS application program.
0004: Unit of work canceled by reporting MDS Router. The unit of work has been canceled by a garbage-collection timeout in the reporting MDS router.
0005: MDS router i