"SNA Formats 10" via IBM BookManager BookServer

Request Error (Category Code = X'10')

This category indicates that the request was delivered to the intended NAU component, but could not be interpreted or processed. This condition represents a mismatch of NAU capabilities.

Category and modifier (in hexadecimal):

1001

RU Data Error: Data in the request RU is not acceptable to the receiving component; or a +RSP(BIND) received at an intermediate node within a session path contained such data. For example, a character code is not in the set supported, a formatted data field is not acceptable to presentation services, or a value specified in the length field (LL) of a structured field is invalid.

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

0000: No specific code applies.
0001: The request contains a subarea address of 0 or a subarea address greater than the maximum subarea value within the specified or implied network.
0002: The network ID specified in the ACTPU is unknown, or is not valid on the link over which the ACTPU was received.
0003: Isolated Pacing Message (IPM) Format Error: An incorrectly formatted IPM was received.
0005: An RNAA type 4 was received in which the local address field length is greater than 1. The implementation does not support a length other than 1.
0006: An RNAA type 4 was received in which the link station address field length is greater than 1. The implementation does not support a length other than 1.
0007: On BFCINIT, the network name portion of the network-qualified name field has a format error.
0008: An invalid character code was found.
0009: The formatted data field is unacceptable to presentation services.
000A: An invalid length field for a structured field was found.
000B: The value in the name length field is too great.
000C: The value in the cryptography key length field is too great.
000D: The URC field length is invalid.
000E: The control vector length field is inconsistent with the control vector data.
000F: A PLU or SLU role specification encoding is invalid.
| 0010: A User Data control vector is invalid.
0020: Too many session keys are present.
0021: A control vector or session key data is invalid.
0022: A BIND image in a session services RU is invalid.
0023: A device characteristics field is invalid.
0024: A BIND or +RSP(BIND) that was not for LU type 6.2 and not in extended format was received at an intermediate APPN network node. The session is terminated.
0026: The length of a GDS variable within the request RU is invalid.
0027: A GDS variable within a Locate is invalid.
| 0029: The IP address specified in an RNAA(Type=X'05') for a new
| Internet Protocol (IP) PU is not a valid internet host
| address.
| 0032: The Maximum Transfer Unit (MTU) value specified in an
| RNAA(Type=X'05') for a new Internet Protocol (IP) PU is
| not in the valid range 283-MAXFRAME.
0033: The name of the deciphering CP in the X'82' subfield of a Cryptography (X'63') control vector does not match the name of the CP(PLU) receiving the control vector.
0037: The subnetwork mask specified for the DR ADD of a frame-relay IP PU is not a valid subnetwork mask for the network involved.
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.

1002

RU Length Error: The request RU was too long or too short; or a +RSP(BIND) received at an intermediate node within a session path was too long or too short.

1003

Function Not Supported: The function requested is not supported. The function may have been specified by a formatted request code, a field in an RU, or a control character.

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

0000

No specific code applies.

0001

The half-session receiving the request did not perform the function because it is not capable of doing so. The requesting half-session requested a function that the receiver does not support and the receiver did not specify that it was capable of supporting the function at session activation; consequently, there is an apparent mismatch of half-session capabilities.

Note: This is to cover a system error. For example, if the PU receiving a SETCV(Vector Key=X'15') is not a gateway PU, that is, the PU did not indicate in the ACTPU response that it is a gateway PU, the PU reports to the SSCP that sent the SETCV that there is an apparent mismatch of half-session capabilities.

0002

The half-session receiving the request did not perform the function, though it is capable of doing so. The requesting half-session did not specify at session activation that it was capable of supporting the function; consequently, there is an apparent mismatch of half-session capabilities.

Note: This is to cover a system error. For example, if the SSCP sending a SETCV(Vector Key=X'15') is not known to the receiving PU as a gateway SSCP, that is, the SSCP did not indicate in ACTPU that it is a gateway SSCP, the PU reports a mismatch of capabilities.

Note: 0001 and 0002 are also assigned for implementation-specific use; see implementation documentation for details of usage.

0003

The component received an unsupported normal-flow DFC command.

0004

The component received an unsupported expedited-flow DFC command. For example, the LU 6.2 half-session may have received a SIGNAL RU when its local conversation style is full-duplex. (However, the half-session rejects the SIGNAL only if it is for the current bracket. Early SIGNALs are held for the correct bracket by saving the SIGNAL value until the correct BB arrives.)

0005

The component received a network control command during an LU-SSCP session.

0006

The component received an unsupported session control command during an LU-SSCP session.

0007

The component received an unsupported data flow control command with LU-SSCP session specified.

0008

Broadcast Search with Reservation: An NNCP received a broadcast search request with reservation.

0009

Initiate Type: The initiate type requested in the CD-Initiate GDS variable or Initiate-Other-CD GDS variable is not supported at the receiver.

000B

A BIND specifying delayed request mode was received from a non-6.2 type LU, but delayed request mode is not supported in the receiver.

000C

A standalone BIND was received from a node that is served by an SSCP that does not support standalone BINDs.

000D

The function identified in the request is not supported by the processing application transaction program.

0010

The RU is not known to session services.

0011

A session key is not supported.

0012

A control vector is not supported.

0014

Cryptography is not supported but a nonzero length was specified for the cryptography key.

0015

Queuing not supported for a controller session.

0016

Service parameter not supported. When this SNA report code is used in an SNA condition report, it is accompanied by a supplemental report identifying the service parameter triplet (or triplets) that was not supported.

0017

Service parameter level not supported. When this SNA report code is used in an SNA condition report, it is accompanied by a supplemental report identifying the service parameter triplet (or triplets) that was not supported.

0018

Destination-role function not supported. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report identifying the structure and containing the contents that specified the unsupported function. Whenever the structure report is not sufficient to identify the unsupported functions, the supplemental report may also be present.

0019

All-role function not supported. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report identifying the structure and containing the contents that specified the unsupported function. Whenever the structure report is not sufficient to identify the unsupported functions, the supplemental report may also be present.

001A

Reserved.

001B

Unable to initiate Agent.

001C

Function conflicts with Format Set 1 encodings. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report identifying the structure and containing the contents that specified the conflicting function.

001D

Reserved

001E

Reserved

001F

Multiple-destination traffic not supported. The reporting location is a specialized, end-only role implementation that supports single-destination traffic only.

0020

A session initiation request specified an OLU and DLU that are the same LU. A dependent LU cannot establish a session with itself.

0021

There is a mismatch between session initiation request type and LU type (independent or dependent). For example, a session initiation request other than BFINIT identifies an independent LU as a session partner.

0023

A session initiation request requiring extended session services support from its network node server was received at an APPN end node that does not have this service available to it.

0025

The component received a NOTIFY RU whose type is not supported.

0027

LU type not supported.

0028

Nonnegotiable BIND not supported by the receiver.

0029

Transmission service (TS) profile of BIND not supported by the receiver.

0030

Normal-flow send/receive mode conflicts with the mode specified in the transmission services (TS) profile of a received BIND.

0031

The primary LU cannot support being first speaker; secondary LU must be first speaker.

0032

In BIND, the specified bracket termination is not supported by the receiver.

0033

Definite response mode is not supported by the receiver.

0034

Secondary LU cannot send EB when normal-flow send/receive mode is full-duplex.

0035

Bracket error resulting from failure of sender to enforce bracket rules for the session.

0036

A network node server received a Notify GDS variable whose type is not supported by the client DLU.

0037

Direction Error: An RU was received inappropriate to the NAU type.

0038

Surrogate autologon support is not provided for this session.

0039

A third-party-initiated session request specified an initiating LU (ILU) and a destination LU (DLU) that are the same LU. An application program cannot initiate a third-party-initiated session to itself.

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.

Note: This sense data value can also be used instead of X'0826'.

* 1004

Request error: function not supported.

1005

Parameter Error: A parameter modifying a control function is invalid, or outside the range allowed 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: For NMVT, the address type field in an SNA Address List subvector does not match the address type required by the command subvector.
0002: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0004: Invalid display type was requested.
0005: Invalid storage length for display type requested.
0006: Invalid storage address; out of specified range.
0007: The command in a Request Change Control MS major vector is incompatible with the SNA/FS server instruction.
0008: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
0010: Incorrect setting of backup focal point flag. The MS Capabilities (X'80F0') major vector received from the focal point contains a backup focal point flag with a value of 1 (indicating that the entry point is to keep its current focal point), but the Focal Point Identification (X'21') subvector in the same major vector names a new backup focal point.
0121-0229,: 0260 Set aside for implementation-specific use, and wil not be otherwise defined in SNA; see implementation documentation for details of usage.

1006

Required field or parameter is missing.

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 required COS names were omitted.
0002: A required name was omitted.
0003: A required network identifier was omitted.
0004: A required session key was omitted.
0005: A required control vector was omitted.
0006: A required subfield of a control vector was omitted.
0007: The TG number field was omitted.
0008: The system-defined ID number, used within the Node Identification field of an XID, was omitted.
* 0009: A required GDS variable was omitted.

1007

Category Not Supported: DFC, SC, NC, or FMD request was received by a half-session not supporting any requests in that category; or an NS request byte 0 was not set to a defined value, or byte 1 was not set to an NS category 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: Invalid NS header received. An NS request byte 0 was not set to a defined value.

1008

Invalid FM Header: The FM header was not understood or translatable by the receiver, or an FM header was expected but not present. For LU 6.2, this sense data value is sent in FMH-7 or UNBIND.

Bytes 2 and 3 following the sense code contain sense code specific information. Figure 10-2 shows the usage of the allowed values by LU type. Settings allowed are:

0000: No specific code applies.
0801: The function code parameters are invalid.
0803: The forms functions cannot be performed.
0805: The copy function cannot be performed.
0806: Compaction table outside the supported set: The number of master characters is not within the valid range.
0807: The PDIR (peripheral data information record) identifier is invalid.
0808: The printer train function cannot be performed.
0809: The FCB (forms control block) load function cannot be performed.
080A: The FCB (forms control block) load function is not supported.
080B: The compaction table name is invalid.
080C: The ACCESS is invalid.
080D: The RECLEN is invalid.
080E: The NUMRECS is invalid.
080F: The data set is in use.
0810: The data set cannot be found.
0811: The password is invalid.
0812: The function is not allowed for the destination or for the data set.
0813: The record is too long.
0814: The data set is full.
0815: The RECID is invalid.
0816: Reserved
0817: The VOLID format is invalid.
0818: The maximum number of logical records per chain is exceeded.
0819: The data set exists.
081A: No space is available.
081B: The VOLID is invalid.
081C: The DSACCESS is invalid.
081D: The RECTYPE is invalid or the data set cannot be found.
081E: The resolution space is insufficient.
081F: The key technique is invalid.
0820: The key displacement is invalid.
0821: The key is invalid.
0822: There is an Invalid N (number of records.)
0823: The KEYIND is invalid.
0824: The SERID is invalid.
0825: Disk Error: An error was detected while reading from, or writing on, the disk.
0826: The RECID format is invalid.
0827: The password has not been supplied.
0828: The record ID has not been supplied.
0829: The Volume ID has not been supplied.
082A: The PGMNAME is invalid.
1204: Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.
2001: The destination (active) is invalid.
2002: The destination (inactive) is invalid.
2003: The destination (suspended) is invalid.
2004: The suspend-resume sequence is invalid.
2005: There has been an interruption level violation.
2006: The resume properties are invalid.
2007: The destination is not available.
2008: The end sequence is invalid.
2009: The FM header length is invalid.
200A: Invalid field setting: The reserved field is set to 1 or the setting is not defined.
200B: Invalid destination: The destination does not exist.
200C: The ERCL is invalid.
200D: The DST is invalid.
200E: Invalid Concatenation Indicator: The concatenation indicator is on, but concatenation is not allowed.
200F: FM data is not allowed for the header.
2010: The FM header set specified in the BIND has been violated.
2011-2013: Reserved
2014: The FM header was not sent concatenated.
2015-2018: Reserved
2019: The stack reference indicator (SRI) is invalid.
201A: The CMI modification could not be accepted.
201B: The CPI modification could not be accepted.
201C: The ECRL modification could not be accepted.
201D: FM Header and Associated Data Mismatch: The FM header indicated associated data would or would not follow (for example, FM header 7 followed by log data, or FM header 5 followed by program initialization parameters), but this indication was in error; or a previously received RU (for example, -RSP(X'0846')) implied that an FM header would follow, but none was received.
4001: Invalid FM Header Type for this LU: The type of the FM header is other than 5, 7, or 12.
4002: The FMH code is invalid.
4003: Compression is not supported.
4004: Compaction is not supported.
4005: Basic exchange is not supported.
4006: Only basic exchange is supported.
4007: The medium is not supported.
4008: There has been a code selection compression violation.
4009: FMHC is not supported.
400A: Demand select is not supported.
400B: DSNAME is not supported.
400C: The media subaddress field is invalid.
400D: There are insufficient resources to perform the requested function.
400E: DSP select is not supported.
6000: FM Header Length Not Correct: The value in the FM header Length field differs from the sum of the lengths of the subfields of the FM header.
6001: The deblocking algorithm (DBA) is invalid.
6004: The queue name length is invalid.
6005: Access Security Information Length Field Not Correct: The value in the Access Security Information Length field differs from the sum of the lengths of the Access Security Information subfields.
6006: The data stream profile (DSP) is invalid.
6007: The FMH-7 is not preceded by a negative response carrying the X'0846' sense code.
6008: The Attach access code is invalid.
6009: Invalid Parameter Length: The field that specifies the length of fixed-length parameters has an invalid setting.
600A: This is not the first FMH-5, the interchange unit type is not the same as the old, and the interchange unit end indicator is off.
600B: Unrecognized FM Header Command Code: The partner LU received an FM header command code that it does not recognize. For LU 6.2 this sense data is sent only in FMH-7.
600C: A null sequence field is required.
600D: User to user program transition is not allowed.
600E: User to non-SNA defined program transition is not allowed.
600F: The FMH-5 reset attached program (RAP) was not sent properly.
6010: The FMH-5 reset attached program (RAP) was sent with an inactive Attach register.
6011: Invalid Logical Unit of Work (LUW): The LUW Length field (in a Compare States GDS variable or an FMH-5) is incorrect, or the length field is invalid, or a LUW ID is not present but is required by the setting of the synchronization level field.
6021: Transaction Program Name Not Recognized: The FMH-5 Attach command specifies a transaction program name that the receiver does not recognize. This sense data is sent only in FMH-7.
6031: PIP Not Allowed: The FMH-5 Attach command specifies program initialization parameter (PIP) data is present, but the receiver does not support PIP data for the specified transaction program. This sense data is sent only in FMH-7.
6032: PIP Not Specified Correctly: The FMH-5 Attach command specifies a transaction program name that requires program initialization parameter (PIP) data, and either the FMH-5 specifies PIP data is not present or the number of PIP subfields present does not agree with the number required for the program. This sense data is sent only in FMH-7.
6034: Conversation Type Mismatch: The FMH-5 Attach command specifies a conversation type that the receiver does not support for the specified transaction program. This sense data is sent only in FMH-7.
6040: Invalid Attach Parameter: A parameter in the FMH-5 Attach command conflicts with the statement of LU capability previously provided in the BIND negotiation.
6041: Synchronization Level Not Supported: The FMH-5 Attach command specifies a synchronization level that the receiver does not support for the specified transaction program. This sense data is sent only in FMH-7.
6042: Reconnection Not Supported: The FMH-5 Attach command specifies reconnection support but the receiver does not support reconnection for the specified transaction program. This sense data is sent only in FMH-7.
6043: Unable to Reconnect Transaction Program--No Retry: The FMH-5 Reconnect command specifies the conversation correlator of a transaction program to which the receiver cannot reconnect. The condition is not temporary. This sense data is sent only in FMH-7.
6044: Unable to Reconnect Transaction Program--Retry Allowed: The FMH-5 Reconnect command specifies the conversation correlator of a transaction program to which the receiver cannot reconnect. The condition is temporary. This sense data is sent only in FMH-7.
6045: Reserved
6046: An SNA/DS transaction program is unable to allocate a conversation with a SNA/DS partner.
6047: An SNA/DS transaction program in conversation with an adjacent SNA/DS transaction program has detected from LU 6.2 PS a return code of RESOURCE_FAILURE.
6048: An SNA/DS transaction program in conversation with an adjacent SNA/DS transaction program has detected from LU 6.2 PS a return code of DEALLOCATE Type(Abend).
| 6050: Missing or unexpected X'12F6' GDS.
6051: The length of the Attach Sequence Number field in the FMH-5 is not 0 or 8.
6052: The Attach sequence number is outside the expected range.
| 6053: Incorrect length of X'12F6', X'12F7', or X'12F8' GDS
| variable.
| 6054: Byte 4, bit 5 of the Attach is 1, indicating the use
| of GSS-API based authentication, but either other
| security bits in the Attach are on also or the
| Attach access security information fields are
| present.
6055: Byte 4, bit 3 of the Attach is 1, indicating the presence of a password substitute, but an Attach sequence number is not in the FMH-5.
| 6056: The partner LU responded to an attach with any data
| other than an FMH7 or an Authentication Token GDS
| (id X'12F6').
| 6057: Deferred authentication processing was requested but
| the Attach did not contain a valid conversation
| correlator.
C000: The header is not supported.
C001: The header length is invalid.
C002: There has been a logical message services block-level error.
C003: There is a version ID mismatch.

    ___________ ___________ ___________ ___________ ___________  
   | Range     |    LU 1   |   LU 4    |   LU 6.1  |   LU 6.2  | 
   |___________|___________|___________|___________|___________| 
   | 0801_0824 |     X     |     X     |           |           | 
   |___________|___________|___________|___________|___________| 
   | 0825      |     X     |           |           |           | 
   |___________|___________|___________|___________|___________| 
   | 0826_082A |     X     |     X     |           |           | 
   |___________|___________|___________|___________|___________| 
   | 2001_200D |     X     |     X     |           |           | 
   |___________|___________|___________|___________|___________| 
   | 200E      |     X     |     X     |     X     |           | 
   |___________|___________|___________|___________|___________| 
   | 200F_201C |     X     |     X     |           |           | 
   |___________|___________|___________|___________|___________| 
   | 201D      |           |           |           |     X     | 
   |___________|___________|___________|___________|___________| 
   | 4001_400E |     X     |     X     |           |           | 
   |___________|___________|___________|___________|___________| 
   | 6000      |           |           |           |     X     | 
   |___________|___________|___________|___________|___________| 
   | 6001,6004 |           |           |     X     |           | 
   |___________|___________|___________|___________|___________| 
   | 6005      |           |           |     X     |     X     | 
   |___________|___________|___________|___________|___________| 
   | 6006_6008 |           |           |     X     |           | 
   |___________|___________|___________|___________|___________| 
   | 6009      |           |           |     X     |     X     | 
   |___________|___________|___________|___________|___________| 
   | 600A      |           |           |     X     |           | 
   |___________|___________|___________|___________|___________| 
   | 600B      |           |           |     X     |     X     | 
   |___________|___________|___________|___________|___________| 
   | 600C_6010 |           |           |     X     |           | 
   |___________|___________|___________|___________|___________| 
   | 6011_6034 |           |           |           |     X     | 
   |___________|___________|___________|___________|___________| 
   | 6040      |           |           |     X     |     X     | 
   |___________|___________|___________|___________|___________| 
   | 6041      |           |           |           |     X     | 
   |___________|___________|___________|___________|___________| 
   | 6046      |           |           |           |     X     | 
   |___________|___________|___________|___________|___________| 
   | 6047      |           |           |           |     X     | 
   |___________|___________|___________|___________|___________| 
   | 6048      |           |           |           |     X     | 
   |___________|___________|___________|___________|___________| 
   | 6051      |           |           |           |     X     | 
   |___________|___________|___________|___________|___________| 
   | 6052      |           |           |           |     X     | 
   |___________|___________|___________|___________|___________| 
   | 6055      |           |           |           |     X     | 
   |___________|___________|___________|___________|___________| 
   | C000_C003 |           |           |     X     |           | 
   |___________|___________|___________|___________|___________|

Figure 10-2. Usage of X'1008' Sense Code Specific Information by LU Type

| Figure has NOT been updated for AWP8214, yet.

1009

Format Group Not Selected: No format group was selected before issuing a Present Absolute or Present Relative Format structured field to a display.

100A

Unknown User Name.

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

0001: The specified user name (e.g., origin, destination, or report-to) cannot be identified with an entry in the directory.

100B

Format Exception

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

0000: No specific code applies.
0001: Required structure absent. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies the absent structure.
0002: Precluded structure present. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies the precluded structure.
0003: Multiple occurrences of a nonrepeatable structure. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies and contains the second occurrence of the structure.
0004: Excess occurrences of a repeatable structure. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies and contains the occurrence of the structure that exceeded the maximum, plus a supplemental report that contains the allowed maximum number of occurrences.
0005: Unrecognized structure present where precluded. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies and contains the precluded unrecognized structure, plus a sibling list of all the allowed structures.
0006: Length outside specified range. This code assumes that the length arithmetic balances and that the sender intended to send the structure at that length. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies and contains the header of the excessively long structure, plus a supplemental report that contains the allowed maximum length.
0007: Length exception. Length arithmetic is out of balance. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies and contains the header of the structure that exceeded its parent's boundary.
0008: Required combination of structures absent. When this SNA report code is used in an SNA condition report, it is accompanied by structure reports that identify the structures that make up the combination, indicating for each whether it was present or absent.
0009: Precluded combination of structures present. When this SNA report code is used in an SNA condition report, it is accompanied by structure reports that identify the structures that make up the precluded combination.
000A: Required combination of structures and data values absent. When this SNA report code is used in an SNA condition report, it is accompanied by structure reports that identify the structures and data values that are present, plus structure reports that identify the absent structures needed to complete the combination.
000B: Precluded combination of structures and data values present. When this SNA report code is used in an SNA condition report, it is accompanied by structure reports that identify the structures and data values that make up the precluded combination.
000C: Unknown or unsupported data value. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies the structure and contains the unknown or unsupported data value.
000D: Incompatible data values. When this SNA report code is used in an SNA condition report, it is accompanied by structure reports that identify the structures and the incompatible data values.
000E: Precluded character present. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies the structure, indicates the byte offset of the offending byte, and includes the byte containing the precluded code point.
000F: Data-value out of range. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies the structure and contains the offending data value, plus a supplemental report that contains the maximum value allowed within the range (if a maximum range value is applicable).
0010: Segmentation present where precluded. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies the structure that should not have been segmented.
0011: Precluded data value. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies the structure and contains the offending data value.
0012: Recognized but unsupported structure. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies the structure.
0013: None of several possible structures found. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies the parent of the absent structure and may contain an unrecognized structure that was found in the place of the absent structure. The structure report also contains a sibling list of the possible structures.
0014: Incorrect order of child structures found. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report that identifies the parent of the incorrectly ordered child structures.

100C

Unrecognized Message Unit

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

0001: The received byte stream could not be identified by the receiving SNA component. When this SNA report code is used in an SNA condition report, it is accompanied by a structure report identifying and containing the unrecognized message unit, plus a sibling list of the allowed message units.

100D

Request Inconsistency: The control information provided for the request is not consistent with other information 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: Server object size is incompatible with service level. When this SNA report code is used in an SNA condition report, it is accompanied by one structure report containing the capacity service parameter triplet and one supplemental report containing the server object size.
0002: A reply DTMU was received before completing a three-way responsibility flow in an SNA/DS request. Retry is allowed.

100E

Directing Exception: A node is unable to perform the required directing or redirecting function for a request as a result of insufficient directory support, or incompatibility between TP name and presence/absence of a user name.

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

0000: No specific code applies.
0001: Agent name known but not supported for specified user destination.
0002: Agent name known but not supported for specified node destination.
0003: Agent name is known at this DSU but not available.

100F

Improper SNA/DS Usage of LU 6.2.

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

0001: An SNA/DS transaction program in conversation with an adjacent SNA/DS transaction program has detected an improper sequence of LU 6.2 basic conversation verbs.

1010

Error on Locate Search or CP Capabilities Message Detected.

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

0000: Unrecoverable error, such as a duplicate control vector, was detected.
0001: A broadcast search resulted in two or more conflicting positive replies that differ on the CP owning the target resource. Multiple positive replies are acceptable, as long as all indicate the same owning CP.
0002: Retired -- see 1010 1002 for its replacement.
0003: An error was detected that prevented the exchange of CP capabilities. Recovery may be attempted.
0004: Unrecoverable error on CP Capabilities GDS variable exchange prevented its initiation or completion on a contention-winner CP-CP session.
1000: Length error in CP Capabilities GDS variable.
1002: Invalid GDS variable received when CP Capabilities GDS variable was expected.
4004: Incomplete negative or neutral reply received on a search, or reservation indicated on Broadcast, or "All" specified on a directed search.
5000: Length error in CD-Initiate GDS variable.
5002: No CD-Initiate GDS variable returned on a search request.
5006: Session polarity or initiate type value received in CD-Initiate GDS variable not supported.
500A: Mode name length error in CD-Initiate GDS variable.
A002: Find GDS variable not present on Locate search request.
B080: Command Parameters (X'80') control vector not present on Found GDS variable.

1012

SNA/DS Receiver Exception MU Format Exception: Parsing or building of the SNA/DS Receiver-Exception MU Format was unsuccessful.

1013

Unknown Server Parameters: The specified parameters are not recognized by the server.

1014

Control Vector Error on a Directory Services or Session Services GDS Variable.

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

003C: Missing Associated Resource Entry (X'3C') control vector on Find or Found.
003D: Missing Directory Entry (X'3D') control vector on Find or Found.
0060: Missing Fully Qualified PCID (X'60') control vector on Locate.
0080: Invalid control vector.
023C: Conflicting directory entry or invalid Associated Resource Entry (X'3C') control vector.
502B: No RSCV received from a network node server.
502C: No COS/TPF control vector received in a CD-Initiate reply from a network node server.
5046: TG vectors not present on a CD-Initiate from an end node OLU or DLU.
A080: Missing Command Parameters (X'80') control vector on Find.
A082: Missing Search Argument Directory Entry (X'82') control vector on Find.
B280: A Found from an end node indicated the directory entry for a located resource was a wild-card entry.

1015

XID Length Error: The XID3 was too long or too short.

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

0000: No specific code applies.
0001: The received XID3 has fewer than 29 bytes.
0002: There is a mismatch between the number of bytes specified in the Length field of XID3 and the actual length of the received XID3.

1016

XID Format 3 Parameter Error: Data in the XID3 is not acceptable to the receiving component because the value in the received XID3 field, whose byte and bit offset is specified by the XID Negotiation Error (X'22') control vector (which also carries this sense data), is inconsistent with the corresponding field in the sent XID3.

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

0000: No specific code applies.
0001: The field in the received XID3 that specifies the maximum number of I-frames that the sender can receive before acknowledgment is set to 0.
0002: The adjacent node has been inconsistent in its request for ACTPU. In a nonactivation XID3 exchange, it has changed the value of the ACTPU Suppression indicator sent in the previous XID3 exchange.
0003: The field in the received XID3 that specifies the maximum BTU length that the sender can receive is set to less than 99 bytes, the minimum required.
0004: The received XID was not XID format 3 when XID format 3 was expected.
0005: The adjacent node does not support BIND segment generation but does support receipt of BIND segments. Any T2.1 node supporting receipt of BIND segments must also support generation of BIND segments.
0006: The adjacent node is an end node, does not support BIND segment receipt, and has a maximum BTU size of less than 265, the minimum required in this case.
0007: The adjacent node is a network node, does not support BIND segment receipt, and has a maximum BTU size of less than 521, the minimum size required in this case.
0008: The adjacent node has changed its networking capabilities in an XID3 from those declared in the previous negotiation-proceeding or nonactivation XID3. A node may not change from an end node to a network node or vice versa in two different negotiation-proceeding or nonactivation XID3s.
0009: The adjacent node is an APPN network node, does not provide CP services, and supports CP-CP sessions, a combination not allowed.
000A: During a nonactivation XID3 exchange, the adjacent node has changed the TG number that was negotiated during the activation exchange.
000B: The adjacent node is the TG number negotiation winner and designates a TG number that the receiving node cannot allocate to this connection. When parallel TGs are supported between the two nodes, 0 is always such a number.
000C: The adjacent node is an APPN network node that does not support BIND segment generation, and this node has a maximum BTU receive size of less than 521. This node may, therefore, be unable to receive a BIND with RSCV from the adjacent network node.
000D: The adjacent node indicates that it does not support the SDLC command/response profile in its XID3. This is the only command/response profile supported by APPN and LEN nodes.
000E: Different product set IDs have been given in the Product Set ID (X'10') control vectors appended to two different received XID3s from the same adjacent node.
000F: The link station roles specified in the sent and received negotiation-proceeding XID3s are not compatible. To activate a connection, one node must contain a primary link station; the other, a secondary link station.
0010: The support of combined asynchronous balanced mode link stations indicated in the sent and received negotiation-proceeding XID3s is not in agreement.
0011: A received XID3 indicates an attempt to activate multiple connections has been made when parallel transmission groups are not supported between the two nodes involved in the XID exchange.
0012: The adjacent node has sent the Network Name (X'0E', CP name) control vector in XID3 but indicates it does not support the Exchange State indicators.
0013: The DLC type indicated in the sent and received negotiation-proceeding XID3s is not in agreement.
0014: After sending a negotiation-proceeding XID3 with the Link Station Role field set to either "primary" or "secondary," the adjacent node sends a negotiation-proceeding XID3 with this field set to "negotiable."
0015: During a negotiation-proceeding XID3 exchange, the adjacent node indicated that it supports BIND pacing as a sender but not as a receiver; i.e., byte 10, bits 0-1 in XID3 are set to 10, which is not allowed.
0016: The node receiving the XID3 is attempting to activate a predefined TG, i.e., a TG that will be assigned a number in the range of 1 to 20, but the TG number sent in the adjacent node's XID3 does not agree with the number that the receiving node has assigned to the TG.
0017: After two negotiation-proceeding XID3 exchanges, the Node Identification field of the received and sent XID3s have identical values. When both nodes contain negotiable link stations, link station roles must be resolved within two exchanges of XIDs after link station role negotiation has begun.
0018: The adjacent node is an APPN node but does not support adaptive BIND pacing as a sender and receiver.
0019: The receiving node does not support CP name changes on APPN connections, but has received a nonactivation XID3 with a CP name that differs from that received during the previous XID exchange.
001A: The adjacent node is inconsistent in its support of parallel TGs. Support of parallel TGs between two nodes cannot change either in link-activation XID exchanges on different TGs or in successive XID exchanges on the same TG.
001B: The adjacent node provides or requests CP services but does not support CP-CP sessions; i.e., bytes 8-9, bits 10-11 of the received negotiation-proceeding XID3 were set to 10, a setting combination not allowed for T2.1 nodes.
001C: The adjacent node declares that its link station role is not primary, secondary, or negotiable; i.e., byte 19, bits 2-3 of the received negotiation-proceeding XID3 were set to 10, a value not allowed for T2.1 nodes.
001D: The adjacent node supports two-way alternating as its transmit-receive capability while the receiving node supports two-way simultaneous and cannot negotiate down to a two-way alternating transmit-receive capability.
001E: The adjacent node has not appended its CP name in the Network Name (X'0E', CP name) control vector on XID3, but indicates that it supports CP-CP sessions and requests them from the receiver. Such a node is interpreted as a LEN end node that is requesting APPN function, which is not permitted.
001F: The setting of the Intersubnetwork Link indicator of the TG Descriptor control vector received in XID3 is inconsistent with the receiving node's system definition. This sense data value is issued only if both sender and receiver support the setting of this bit.
0020: The node type the adjacent node declares itself to be in its XID3 is one to which the receiving node cannot activate a TG.
0021: The setting of the Error Recovery Mode field of the HPR Capabilities (X'61') control vector received during a negotiation-proceeding XID3 exchange is inconsistent with the receiving node's system definition. One node specified that error recovery is required, but the other node specified that no error recovery is required. HPR protocols will not be used on this TG. Sense data X'10160021' is not carried in the XID Negotiation Error (X'22') control vector.
0022: The adjacent node is an HPR node (i.e., it included an HPR Capabilities (X'61') control vector in XID3), but the receiving node detected that it specified a maximum BTU size less than 768.
0023: The adjacent node is an HPR node (i.e., it included an HPR Capabilities (X'61') control vector in XID3), but the receiving node detected that it specified an invalid ANR label length (i.e., less than 1 or greater than 8).
0024: The adjacent node is an HPR node (i.e., it included an HPR Capabilities (X'61') control vector in XID3), but the receiving node detected that it specified an invalid CP NCE identifier length (i.e., less than 1 or greater than 8).
0025: The adjacent node is an HPR node (i.e., it included an HPR Capabilities (X'61') control vector in XID3), but the receiving node detected that it specified an invalid route setup NCE identifier length (i.e., less than 1 or greater than 8).
0026: The adjacent node is an HPR node (i.e., it included an HPR Capabilities (X'61') control vector in XID3), but the receiving node detected that the length of the HPR Transport Tower (X'81') subfield of the control vector is inconsistent with the length of a field included in the subfield.
0027: The adjacent node has specified that it supports the Control Flows Over RTP (1402) option set but has not included the Control Flows Over RTP Tower (X'81') subfield in the XID3 HPR Capabilities (X'61') control vector.
0028: The adjacent node has specified an invalid value for the error recovery mode in the XID3 HPR Capabilities (X'61') control vector.
| 0031: The XID3 received from the adjacent node does not contain
| an HPR Capabilities (X'61') control vector. The ATM port
| supports only HPR links.
| 0032: The RTP Supported indicator is set to 0 in the HPR
| Capabilities (X'61') control vector of the XID3 received
| from the adjacent node. The ATM port supports links only
| to nodes that support RTP.
| 0033: The Control Flows over RTP Supported indicator is set to 0
| in the HPR Capabilities (X'61') control vector of the XID3
| received from the adjacent node. The ATM port supports
| links only to nodes that support control flows over RTP.
| 0034: The LDLC Supported indicator is set to 0 in the HPR
| Capabilities (X'61') control vector of the XID3 received
| from the adjacent node. The ATM port supports links only
| to nodes that support LDLC.
| 0035: A negotiable or 0 TG number was received in XID3, but
| multiple links are defined between the paired switched
| ports. Use of predefined TG numbers is required.
| 0036: A predefined TG number received in XID3 was not defined at
| the receiver.
| 0037: A nonzero negotiable TG number was received in XID3, but
| another link between the paired switched ports is using a
| different TG number.
| 0038: A TG number of 0 was received in XID3, but an active link
| between the paired switched ports is using a predefined TG
| number.
| 0039: A "race" was detected (i.e., both nodes are simultaneously
| attempting to activate a switched virtual connection for
| the same link), but multiple virtual connections are not
| needed. According to the race resolution algorithm, the
| other virtual connection will be used for the link.
| 0044: The HPR Capabilities (X'61') control vector received in
| XID3 indicates that Logical Data Link Control (LDLC) is
| supported, but the XID3 does not include a TG Descriptor
| (X'46') control vector containing a TG Identifier (X'80')
| subfield. Configuration services in the receiving node
| requires the subfield when LDLC is supported on the link
| being activated.

1018

MU Sequence Exception: An SNA/DS transaction program has detected an improper sequence of SNA/DS MUs.

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

0001: A DMU has been received, but the MU ID has already been terminated.
0002: The MU ID state received from the partner is incompatible with the state in the MU ID registry.
0003.: Reserved
0004: A previous terminate conversation indication has been ignored.
0005: An RRMU was received but was not followed by a Change Direction indicator (i.e., the RECEIVE_AND_WAIT verb issued after receiving the RRMU, returned something other than WHAT_RECEIVED=SEND).

1019

Invalid Restart Byte Position.

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

0001: The restart byte position value specified in the DCMU is greater than 1 plus the value of the last byte received in the CRMU. When this SNA report code is used in an SNA condition report, it is accompanied by three supplemental reports that identify the invalid restart byte position in the DCMU and the values specified in the CRMU. Supplemental report 1 contains the restart byte position value in the DCMU. Supplemental report 2 contains the last structure received value in the CRMU. Supplemental report 3 contains the last byte received value in the CRMU. If this value was not specified in the CRMU, this report will be omitted.
0002: The receiver does not support the byte-count restart elective, and the restart byte position value specified in the DCMU is not the beginning of the LLID structure following the last successfully received LLID structure. When this SNA report code is used in an SNA condition report, it is accompanied by three supplemental reports that identify the invalid restart byte position in the DCMU and the values specified in the CRMU: Supplemental report 1 contains the restart byte position value in the DCMU. Supplemental report 2 contains the last structure received value in the CRMU. Supplemental report 3 contains the last byte received value in the CRMU. If this value was not specified in the CRMU, the report will be omitted.
0003: The receiver supports the byte-count restart elective, and the restart byte position value specified in the DCMU is not equal to 1 and is less than or equal to the last byte received value specified in the CRMU. When this SNA report code is used in an SNA condition report, it is accompanied by three supplemental reports that identify the invalid restart byte position in the DCMU and the values specified in the CRMU; Supplemental report 1 contains the restart byte position value in the DCMU. Supplemental report 2 contains the last structure received value in the CRMU. Supplemental report 3 contains the last byte received value in the CRMU. If this value was not specified in the CRMU, the report will be omitted.

101A

Invalid Control Vector Sequence: A control vector was found containing a key that was invalid for the position of the control vector within a TDU.

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

0000: No specific code applies.
nnmm: Byte 2 following the sense code contains the key (nn) of the vector previous to the one in error; byte 3 contains the key (mm) of the vector in error.

101C

Invalid Data Received

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

0000: No specific code applies.
0001: Alteration of input data not allowed.

101D

Insufficient Length: The length of the received signal is insufficient to contain additional required fields.

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

0000: No specific code applies.
0001: A BIND or RSP(BIND) was received that was too large to be extended. The BIND was rejected.
0002: An UNBIND was received that was too large to be extended. An UNBIND cleanup is sent on both session stages.

101E

CP Capabilities Mismatch: The CP capabilities of the adjacent node as indicated in the Support Indicators field of the CP Capabilities GDS variable are unacceptable.

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 bit within the Support Indicators field of the received CP Capabilities GDS variable that was considered to be unacceptable by the receiving node. Values X'00'-X'1F' are the only valid settings.