Sense codes for UNBIND

The following sense data can be sent by VTAM® in the UNBIND RU:

Code

Meaning

X'080Fnnnn'

End user not authorized. The requesting end user does not have access to the requested resource.

Bytes 2 and 3 can contain sense-code-specific information.

X'080F0002'

Session-Level LU-LU Verification Protocol Mismatch. An LU that supports only the enhanced LU-LU verification protocol received a BIND or BIND response that specified the basic LU-LU verification protocol.

X'080F6051'

Access security violation. VTAM or the application program detects a security protocol violation.

X'0812nnnn'

Insufficient resource. The receiver cannot act on the request because of a temporary lack of resources.

Bytes 2 and 3 can contain sense-code-specific information.

X'08120000'

No specific code applies.

X'0812001E'

A session has failed because depletion of pooled buffer storage has exceeded a critical threshold resulting from that session's monopolizing usage.

X'08130000'

Bracket bid reject, no RTR forthcoming. The BID (or BB) is received while the contention winner is in the in-bracket state or the between-brackets state, and the contention winner denies permission. No RTR is to be sent.

X'08140000'

Bracket bid reject, RTR forthcoming. The BID (or BB) is received while the contention winner is in the in-bracket state or the between-brackets state, and the contention winner denies permission. RTR is sent.

X'08190000'

RTR not required. The receiver of READY TO RECEIVE has nothing to send.

X'081Cnnnn'

Request not executable. The requested function cannot be executed because of a permanent error condition in the receiver.

Bytes 2 and 3 can contain sense-code-specific information.

X'081C0000'

No specific code applies.

X'08460000'

ERP message forthcoming. The received request is rejected for a reason that is to be specified in a forthcoming request.

X'08880010'

Name conflict. The partner LU 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.

X'08880011'

Name conflict. The 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.

X'08880012'

Name conflict. A session initiation request is received from the partner LU containing a LUNAME found in an internal table, but with a different network qualifier.

X'1001nnnn'

RU data error. Data in the request RU is not acceptable to the receiving component. For example:

A character code is not in the set that is supported.
A formatted data field is not acceptable to presentation services.
A value specified in the length field (LL) of a structured field is not valid.
A required name in the request is omitted.

Bytes 2 and 3 can contain sense-code-specific information.

X'10010000'

No specific code applies.

X'10010003'

An isolated pacing message is received that is not valid.

X'10020000'

RU length error. The request RU is too long or too short.

X'10030000'

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

X'10030004'

Function not supported. A SIGNAL RU (indicating REQUEST_TO_SEND) was received on a full-duplex conversation, or an EXPD RU was received on a session that does not support full-duplex protocols. The session is unbound.

X'10050000'

Parameter error. A parameter that modifies a control function is not valid or is outside the range that the receiver allows.

An EXPD RU was received with a format or length that was not valid. The session is unbound.

X'10070000'

Category not supported:

DFC, SC, NC, or FMD request is received by a half-session not supporting any requests in that category.
An NS request byte 0 is not set to a defined value.
Byte 1 is not set to an NS category that the receiver supports.

X'1008nnnn'

Not valid FM header. The receiver cannot understand or translate the FM header, or the receiver expects an FM header and one is not present.

Bytes 2 and 3 can contain sense-code-specific information.

X'1008200E'

Not valid concatenation indicator. The concatenation indicator is on but concatenation is not allowed.

X'1008201D'

FM header and associated data mismatch. The FM header indicates that:

Associated data does or does not follow (such as FMH-7 followed by log data or FMH-5 followed by program initialization parameters), but this indication is in error.
A previously received RU implies that an FM header follows, but none is received.

X'10084001'

Not valid FM header type. The type of the FM header is other than 5, 7, or 12.

X'10086000'

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.

X'10086005'

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.

X'10086009'

Not valid parameter length. The field that specifies the length of fixed-length parameters has a not valid setting.

X'10086011'

Not valid logical unit of work:

The LUW length field (in a compare-states GDS variable or an FMH-5) is incorrect.
The LUW is not valid.
An LUWID is not present but is required by the setting of the synchronization level field.

X'10086040'

Not valid ATTACH parameter. A parameter in the FMH-5 ATTACH command conflicts with the statement of LU capability that was previously in the BIND negotiation.

X'20010000'

Sequence number. The sequence number received on the normal-flow request is not one greater than the last sequence number.

X'20020000'

Chaining. An error exists in the sequence of the chain indicator settings (BCI, ECI), such as first, middle, first.

X'20030000'

Bracket. An error results because the sender fails to enforce the bracket rules for the session. (This error does not apply to contention or race conditions.)

X'20040000'

Direction error. An error that results because a normal-flow request is received, and the half-duplex flip-flop state is not received.

Data was received from a partner LU on a full-duplex conversation that is in SEND_ONLY state. The session is unbound.

X'20080000'

No begin bracket. An FMD request that specifies BBI=BB is received after the receiver has received a BRACKET INITIATION STOPPED request.

X'200A0000'

Immediate request mode error. A request violates the immediate request mode protocol.

X'200B0000'

Queued response error. A request violates a queued response protocol, such as QRI=¬QR, when an outstanding request has QRI=QR.

X'200E0000'

Response correlation error. A response is received that does not correlate to a previous request.

A response for an EXPD RU was received, but an expedited request is not outstanding. This session is unbound.

X'200F0000'

Response protocol error. A violation occurs in the response protocol, such as the generation of +RSP to an RQE chain.

An EXPD RU was received, but no response has been sent to a previously received EXPD request. The session is unbound.

X'20110000'

Pacing error. A half-session receives a normal-flow request after the pacing count is reduced to 0 and before a pacing response is sent.

X'20120000'

Not valid sense code received. A negative response is received that contains an SNA-defined sense code that cannot be used for the request that is sent.

X'2013nnnn'

Decompression protocol error: A request containing compressed data was received in error.

Bytes 2 and 3 can contain sense-code-specific information.

X'40030000'

BB not allowed. The begin bracket indicator (BBI) is specified incorrectly, such as BBI=BB with BCI=¬BC.

X'40040000'

CEB or EB not allowed. The conditional end bracket indicator (CEBI) or end bracket indicator (EBI) is specified incorrectly.

X'40070000'

Definite response not allowed. A definite response is requested and is not permitted.

A Confirm request was received on a full-duplex conversation. The session is unbound.

X'40080000'

Pacing not supported. The pacing indicator is set on a request, but the receiving half-session or boundary function half-session does not support pacing for this session.

X'40090000'

CD not allowed. The change direction indicator (CDI) is specified incorrectly, such as CDI=CD with EBI=EB.

X'400B0000'

Chaining not supported. The chaining indicators (BCI and ECI) are specified incorrectly, such as chaining bits indicated other than (BC,EC), but multiple-request chains are not supported for the session or for the category specified in the request header.

A full-duplex conversation received a request carrying a CD indicator with ECI specified.

X'400C0000'

Brackets not supported. The bracket indicators (BBI, CEBI, and EBI) are specified incorrectly. For example, a bracket indicator is set (BBI=BB, CEBI=CEB, or EBI=EB), but brackets are not used for the session.

X'400F0000'

Incorrect use of format indicator. The format indicator (FI) is specified incorrectly. For example, FI is set with BCI=¬BC, or FI is not set on a DFC request.

X'40100000'

Alternate code not supported. The code selection indicator (CSI) is set but is not supported for the session.

X'40110000'

Incorrect specification of RU category. The RU category indicator is specified incorrectly. For example, an expedited-flow request or response is specified with RU category indicator=FMD.

X'40120000'

Incorrect specification of request code. The request code on a response does not match the request code on its corresponding request.

A received expedited flow response was not a SIGNAL or EXPD RU. The session is unbound.

X'40130000'

Incorrect specification of SDI, RTI. The sense data included indicator (SDI) and the response type indicator (RTI) are not specified properly on a response. The proper value pairs are (SDI=SD, RTI=negative) and (SDI=¬SD, RTI=positive).

X'40140000'

Incorrect use of DR1I, DR2I, ERI. The definite response 1 indicator (DR1I), definite response 2 indicator (DR2I), and exception response indicator (ERI) are specified incorrectly. For example, a SIGNAL request is not specified with DR1I=DR1, DR2I=¬DR2, and ERI=¬ER.

X'40150000'

Incorrect use of QRI. The queued response indicator (QRI) is specified incorrectly. For example, QRI=QR is specified on an expedited-flow request.

X'40160000'

Incorrect use of EDI. The enciphered data indicator (EDI) is specified incorrectly. For example, EDI=ED is specified on a DFC request.

X'40170000'

Incorrect use of PDI. The padded data indicator (PDI) is specified incorrectly. For example, PDI=PD is specified on a DFC request.

X'40180000'

Incorrect setting of QRI with loser's BB. The winner of a half-session receives a BB chain that requests use of a session (by means of LUSTAT(X'0006')), but the QRI is specified incorrectly; that is, QRI=¬QR.

X'40190000'

Incorrect indicators with last-in-chain request. A last-in-chain request specifies RH settings that are incompatible, such as RQE*, CEBI=¬CEB, and CDI=¬CD.

X'40210000'

QRI setting in response different from that in request. The QRI setting in the response differs from the QRI setting in the corresponding request.

X'8005nnnn'

No session. No half-session is active in the receiving end node for the indicated origination-destination pair, or no boundary function session connector is active for the origination-destination pair in a node providing the boundary function. A session activation request is needed.

Bytes 2 and 3 can contain sense-code-specific information.

X'80050000'

No specific code applies.