Secondary Return Codes

The following section contains the LUA secondary return codes:

LUA_SEC_OK

Additional information is available for the primary return code associated with this secondary return code.

LUA_INVALID_LUNAME

The verb specified an invalid lua_name.

LUA_BAD_SESSION_ID

The verb control block specified an incorrect value for the lua_sid parameter.

LUA_DATA_TRUNCATED

The buffer length (as specified in lua_max_length) was not long enough for the data received, so the data was truncated.

LUA_BAD_DATA_PTR

The command requires data to be supplied or returned, but the lua_data_ptr parameter either contains an invalid pointer or does not point to a read/write segment.

LUA_DATA_SEG_LENGTH_ERROR

One of the following conditions occurred:

• The data segment supplied on an RUI_READ or SLI_RECEIVE verb is shorter than the length given in the lua_max_length parameter.
• The data segment was supplied on an RUI_WRITE or SLI_SEND verb is shorter than the length given in the lua_data_length parameter.
• The data segment supplied on an RUI_READ, RUI_WRITE, SLI_RECEIVE, or SLI_SEND verb is not a read/write data segment.

LUA_RESERVED_FIELD_NOT_ZERO

The command that was just issued has a reserved parameter that is not zero.

LUA_INVALID_POST_HANDLE

A valid semaphore was not specified in the LUA verb control block. When an LUA verb does not complete synchronously, a semaphore is needed to signal the completion of the verb.

LUA_PURGED

An RUI_READ or an SLI_RECEIVE verb was canceled because an RUI_PURGE or an SLI_PURGE was issued.

LUA_BID_VERB_SEG_ERROR

The buffer with the SLI_BID verb control block was released before the SLI_RECEIVE with lua_flag1.bid_enable set to 1 was issued.

LUA_NO_PREVIOUS_BID_ENABLED

An RUI_BID or SLI_BID verb was not issued before an RUI_READ or SLI_RECEIVE verb with lua_flag1.bid_enable was issued.

LUA_NO_DATA

An RUI_READ or SLI_RECEIVE verb was issued with the NO_WAIT parameter and there was no data available to read.

LUA_BID_ALREADY_ENABLED

An RUI_BID or SLI_BID verb was active when an RUI_READ or SLI_RECEIVE verb with lua_flag1.bid_enable was issued.

LUA_VERB_RECORD_SPANS_SEGMENTS

The LUA verb control block contains a length parameter that, when added to the offset of the segment, goes past the end of the segment.

LUA_INVALID_FLOW

An LUA verb was issued with the lua_flag1 flow flags set in error. Check that the correct number of lua_flag1 flow flags were set as follows:

• For RUI_READ or SLI_RECEIVE, at least one
• For RUI_WRITE, only one
• For SLI_SEND, only one lua_flag1 flow flag must be set when sending an SNA response.

LUA_NOT_ACTIVE

An application program issued an LUA verb at a time that LUA was not active within Communications Server.

LUA_VERB_LENGTH_INVALID

A verb was issued with an incorrect lua_verb_length parameter. The length specified is not equal to the length that LUA expected.

LUA_REQUIRED_FIELD_MISSING

The issued RUI_WRITE verb either did not include a data pointer (if the data count was not zero) or it did not include an lua_flag1flow flag.

LUA_READY

The SLI session is now ready to process additional commands. This status is issued after a prior NOT_READY status was received, or after a SLI_CLOSE verb completed with the primary return code CANCELED and secondary return code RECEIVE_UNBIND_HOLD or RECEIVED_UNBIND_NORMAL.

LUA_NOT_READY

The SLI session is temporarily suspended for either of the following reasons:

• A CLEAR command was received. The SLI session resumes when an SDT command is received.
• An UNBIND command was received. The session is suspended until BIND, optional STSN and SDT commands are received. Any user extension routines that were supplied by the original SLI_OPEN verb are called again; therefore, these routines must be reentrant. After the SLI processes the SDT command, the SLI session resumes. Two types of UNBIND commands are:
  • UNBIND type X'02', which means that a new BIND is coming
  • UNBIND type X'01', which means that the application specified an lua_session_type of LUA_SESSION_TYPE_DEDICATED in the SLI_OPEN verb that started this session.

LUA_INIT_COMPLETE

When the LUA interface initializes the session while SLI_OPEN is processing, this status is returned on SLI_RECEIVE or SLI_BID verbs for LUA applications that issue SLI_OPEN with the LUA_INIT_TYPE_PRIM_SSCP parameter.

LUA_SESSION_END_REQUESTED

SLI received a SHUTD command from the host, indicating the host is ready to shut down the session.

LUA_NO_SLI_SESSION

A command was issued when a session was not open, or a session is being taken down because of an SLI_CLOSE verb or session failure. An SLI_RECEIVE or SLI_SEND verb issued during the processing of an SLI_OPEN verb returns this code when:

• The SLI_OPEN lua_init_type parameter is not set to LUA_INIT_TYPE_PRIM_SSCP. An SLI_BID verb also returns this code under these circumstances.
• The SLI_RECEIVE or SLI_SEND lua_flag1 parameter does not specify lua_flag1.sscp_norm.

The SLI component is in SLI_OPEN processing after an UNBIND type X'02' command or UNBIND type X'01' (LUA_SESSION_TYPE_DEDICATED) is received and until the SDT command is processed. UNBIND type X'02' indicates that a new BIND is coming.

LUA_SESSION_ALREADY_OPEN

An SLI_OPEN verb was issued for an LU name that already has a session open.

LUA_INVALID_OPEN_INIT_TYPE

An SLI_OPEN verb contained an incorrect value in the lua_init_type parameter.

LUA_INVALID_OPEN_DATA

An SLI_OPEN verb was issued with the lua_init_type parameter set for secondary initialization with INITSELF (LUA_INIT_TYPE_SEC_IS), and the data buffer does not contain a valid INITSELF command.

LUA_UNEXPECTED_SNA_SEQUENCE

During SLI_OPEN processing, an unexpected command or data was received from the host.

LUA_NEG_RSP_FROM_BIND_ROUTINE

The user-provided SLI_BIND routine generated a negative response to the BIND. The SLI_OPEN verb ends unsuccessfully.

LUA_NEG_RSP_FROM_CRV_ROUTINE

The user-provided SLI_BIND routine generated a negative response to the BIND. The SLI_OPEN verb ends unsuccessfully.

LUA_NEG_RSP_FROM_STSN_ROUTINE

The user-supplied SLI STSN routine responded negatively to the STSN. SLI_OPEN ended unsuccessfully.

LUA_CRV_ROUTINE_REQUIRED

The user did not provide an SLI CRV routine, but a CRV was received from the host. The SLI issues a negative response to the CRV, and the SLI_OPEN verb ends unsuccessfully at this time.

LUA_NEG_RSP_FROM_SDT_ROUTINE

The user-provided SLI SDT routine generated a negative response to an SDT. This condition causes the SLI_OPEN verb to end.

LUA_INVALID_OPEN_ROUTINE_TYPE

In the SLI_OPEN extension routine list, the lua_open_routine_type parameter is not valid.

LUA_MAX_NUMBER_OF_SENDS

The application program issued more than two SLI_SEND verbs before one completed.

LUA_SEND_ON_FLOW_PENDING

The application issued an SLI_SEND verb for an SNA flow (SSCP-expedited, SSCP-normal, LU-expedited, LU-normal) that already has an SLI_SEND verb outstanding.

LUA_INVALID_MESSAGE_TYPE

The SLI does not recognize the lua_message_type parameter.

LUA_RECEIVE_ON_FLOW_PENDING

The SLI application issued an SLI_RECEIVE verb for an SNA flow that already has an SLI_RECEIVE verb outstanding.

LUA_DATA_LENGTH_ERROR

An SLI_OPEN command was issued that requires user data that the application program did not supply. Data is required for a secondary-initiated SLI_OPEN verb, and 4 bytes of status is required when the application issues an SLI_SEND verb for an LUSTAT command.

LUA_CLOSE_PENDING

One of the following has occurred:

• A CLOSE_NORMAL was issued while a CLOSE_NORMAL or a CLOSE_ABEND was pending.
• A CLOSE_ABEND was issued while another CLOSE_ABEND was pending. The only valid reason to issue another CLOSE_ABEND is when a CLOSE_NORMAL is pending.

LUA_NEGATIVE_RSP_CHASE

During SLI_CLOSE processing, the SLI received a negative response to a CHASE command from the host. The session is stopped as requested by the SLI_CLOSE.

LUA_NEGATIVE_RSP_SHUTC

During SLI_CLOSE processing, the SLI received a negative response to a SHUTC command from the host. The session is stopped as requested by the SLI_CLOSE.

LUA_NEGATIVE_RSP_SHUTD

During SLI_CLOSE processing, the SLI received a negative response to a SHUTD command from the host. The session is stopped as requested by the SLI_CLOSE.

LUA_NO_RECEIVE_TO_PURGE

An SLI_PURGE verb was issued when no SLI_RECEIVE verb was outstanding. Two possible causes are as follows:

• The address contained in the lua_data_ptr parameter did not point to the outstanding SLI_RECEIVE verb that was to be purged.
• The SLI_RECEIVE verb might have completed while the SLI_PURGE verb was being processed. This is not an error condition. Code the application program to handle this situation.

LUA_CANCEL_COMMAND_RECEIVED

While processing an SLI_RECEIVE verb, the host sent a CANCEL command to cancel the chain of data being received.

LUA_RUI_WRITE_FAILURE

An RUI_WRITE verb posted with an unexpected error to the SLI.

LUA_INVALID_SESSION_TYPE

An SLI_OPEN verb contained a value that is not valid in the lua_session_type.

LUA_SLI_BID_PENDING

An SLI verb was issued while a previously-issued SLI_BID is active. Only one SLI_BID can be active at a time.

LUA_PURGE_PENDING

An SLI_PURGE verb was issued while a previously-issued SLI_PURGE is active. Only one SLI_PURGE can be active at a time.

LUA_PROCEDURE_ERROR

An NSPE or NOTIFY message was received, indicating a host procedure error occurred. The SLI_OPEN is posted with this return code (unless the SLI_OPEN verb retry option is used). With lua_wait set to a nonzero value, the INITSELF or LOGON message is retried until the host procedure is available or the application issues an SLI_CLOSE.

LUA_INVALID_SLI_ENCR_OPTION

The lua_encr_decr_option parameter was set to 128 in the SLI_OPEN verb. The SLI does not support 128 for the encryption or decryption processing option.

LUA_RECEIVED_UNBIND

The SLI received an UNBIND command from the primary LU while there was an active SLI session. The SLI session is stopped.

LUA_RECEIVED_UNBIND_HOLD

During primary- or secondary-initiated SLI_CLOSE normal processing, SLI received an UNBIND type X'02'. Type X'02' means that a new BIND is forthcoming. The session is suspended until BIND, optional CRV and STSN, and SDT commands are received. Any user extension routines that were supplied by the original SLI_OPEN verb are called again; these routines must be reentrant. After the SLI processes the SDT command, the SLI session resumes.

LUA_RECEIVED_UNBIND_NORMAL

During primary- or secondary-initiated SLI_CLOSE normal processing for a session started with an SLI_OPEN verb that specified an lua_session_type of LUA_SESSION_TYPE_DEDICATED, SLI received an UNBIND type X'01'. The session is suspended until BIND, optional STSN and SDT commands are received. Any user extension routines that were supplied by the original SLI_OPEN verb are called again; these routines must be reentrant. After the SLI processes the SDT command, the SLI session resumes.

LUA_SLI_LOGIC_ERROR

The SLI detected an internal logic error.

LUA_TERMINATED

A verb that was pending when an SLI_CLOSE or RUI_TERM verb was issued has been canceled.

LUA_NO_RUI_SESSION

An RUI verb was issued for a session that has not been initialized (with RUI_INIT) or a verb other than RUI_TERM was issued while an RUI_INIT verb for the session was in progress.

This return code can occur when a session outage occurs while no active RUI verbs are outstanding. The next verb issued gets this return code. The application program handles this return code as it would a SESSION_FAILURE.

LUA_DUPLICATE_RUI_INIT

The application program issued an RUI_INIT verb for a session that is already initialized or has an RUI_INIT verb in progress.

LUA_INVALID_PROCESS

An RUI verb was issued for a session that is already owned by another process.

LUA_API_MODE_CHANGE

A non-SLI request was issued to the RUI on a session that was established by the SLI.

LUA_COMMAND_COUNT_ERROR

The maximum number of issued RUI_READ or RUI_WRITE verbs was exceeded, or an RUI_BID or RUI_TERM verb was issued while a previously issued RUI_BID or RUI_TERM verb was still in progress.

LUA_NO_READ_TO_PURGE

An RUI_PURGE verb was issued when no RUI_READ verb was outstanding. Two possible causes follow:

• The address contained in the lua_data_ptr parameter does not point to the outstanding RUI_READ verb to be purged.
• The RUI_READ verb completed while the RUI_PURGE verb was being processed. This is not an error condition. Code the application program to handle this situation.

LUA_MULTPLE_WRITE_FLOWS

More than one flow flag was turned on in the FLAG1 issued to an RUI_WRITE verb.

LUA_DUPLICATE_READ_FLOW

The application program issued an RUI_READ for a flow that already has an RUI_READ pending.

LUA_DUPLICATE_WRITE_FLOW

The RUI_WRITE verb that was issued contained a FLAG1 flow flag that showed a session flow for a previous RUI_WRITE verb that had not completed.

LUA_LINK_NOT_STARTED

LUA could not start the data link during session initialization.

LUA_INVALID_ADAPTER

The DLC adapter configuration is incorrect or the configuration file has been damaged.

LUA_ENCR_DECR_LOAD_ERROR

An unexpected error was received while attempting to load the user-provided encryption or decryption dynamic link library.

LUA_ENCR_DECR_PROC_ERROR

An unexpected error was received while attempting to get the procedure address within the user-provided encryption or decryption dynamic link library.

LUA_LINK_NOT_STARTED_RETRY

An RUI_INIT or SLI_OPEN verb failed because the link could not be activated. This return code implies that something is wrong at the partner location or with the connection between the two machines.

LUA_NEG_NOTIFY_RSP

An RUI_INIT was issued that caused a notify request to be sent to the SSCP to indicate the SLU can now be part of a session. The SSCP responded negatively to this notify request. The intended half-session component understood the supported request, but did not process it.

LUA_RUI_LOGIC_ERROR

An RUI internal logic error occurred.

LUA_LU_INOPERATIVE

A severe error occurred while the SLI was attempting to stop the session. This LU is unavailable for any LUA requests until an ACTLU is received from the host.

LUA_RESOURCE_NOT_AVAILABLE

The LU, PU, link station, or link specified in an RU is not available. The SLI_OPEN verb cannot can be posted with this return code unless the SLI_OPEN retry option is used. With lua_wait set to a nonzero value, the INITSELF or LOGON message is retried until the host procedure is available or the application issues an SLI_CLOSE verb.

LUA_SESSION_LIMIT_EXCEEDED

The requested session cannot be activated because one of the network addressable units (NAUs) is at its session limit, such as the LU-LU session limit or the LU mode session limit. This sense code applies to the ACTCDRM, the INIT, the BID, and the CINIT requests.

The SLI_OPEN verb can be posted with this return code unless the SLI_OPEN verb retry option is used. With lua_wait set to a nonzero value, the INITSELF or LOGON message is retried until the host procedure is available or the application issues an SLI_CLOSE verb.

LUA_SLU_SESSION_LIMIT_EXCEEDED

If accepted, the request would cause the SLU session limit to be exceeded.

LUA_MODE_INCONSISTENCY

The present status does not permit the function to be performed. The intended half-session component understood the supported request, but did not process it. This code can also appear as a sense code in an EXR.

LUA_INSUFFICIENT_RESOURCES

Due to a temporary lack of resources, the receiver cannot act on the request. The intended half-session component understood the supported request, but did not process it.

LUA_RECEIVER_IN_TRANSMIT_MODE

A race condition exists. A normal-flow request was received while the half-duplex contention state was not-receive, or while resources (such as buffers) necessary for handling normal-flow data were unavailable.

This code can also appear as a sense code in an exception request.

LUA_LU_COMPONENT_DISCONNECTED

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

LUA_NEGOTIABLE_BIND_ERROR

A negotiable BIND was received. The SLI does not allow a negotiable BIND unless there is a user-supplied SLI_BIND routine provided through the SLI_OPEN verb.

LUA_BIND_FM_PROFILE_ERROR

An unsupported FM profile was detected on the BIND. The SLI supports FM profiles 3 and 4 only.

LUA_BIND_TS_PROFILE_ERROR

An unsupported TS profile was detected on the BIND. The SLI supports TS profiles 3 and 4 only.

LUA_BIND_LU_TYPE_ERROR

An unsupported LU type was detected. LUA supports LU 0, LU 1, LU 2 and LU 3 only.

LUA_SSCP_LU_SESSION_NOT_ACTIVE

The SSCP-LU session required for processing a request is not active. For example, in processing an INITSELF request, the SSCP did not have an active session with the target LU named in the INITSELF.

Bytes 2 and 3 contain sense-code-specific information. The following settings are allowed:

0000

No specific code applies.

0001

The SSCP-SLU session is being reactivated.

0002

The SSCP-PLU session is inactive. The SLI_OPEN verb can be posted with this return code unless the SLI_OPEN retry option is used. With lua_wait set to a nonzero value, the INITSELF or LOGON message is retried until the host procedure is available or the application issues an SLI_CLOSE verb.

0003

The SSCP-SLU session is inactive.

0004

The SSCP-SLU session is being reactivated.

LUA_REC_CORR_TABLE_FULL

The session receive correlation table for the flow requested reached its capacity.

LUA_SEND_CORR_TABLE_FULL

The send correlation table for the flow requested reached its capacity.

LUA_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. The following settings are allowed:

0000

No specific code applies. The SLI_OPEN cannot be posted with this return code unless the SLI_OPEN retry option is used. With lua_wait set to a nonzero value, the INITSELF or LOGON message is retried until the host procedure is available or the application issues an SLI_CLOSE.

0001

An SSCP tried unsuccessfully to reroute a session services request to its destination through one or more adjacent SSCPs. This value is sent by a gateway SSCP when it has exhausted trial-and-error rerouting.

SSCP rerouting failed completely. An SSCP tried unsuccessfully to a particular SSCP. For example, this code is 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, no adjacent SSCP table corresponds to the rerouting key in the resource identifier control vector.

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.

0005

Retired

0006

Retired

0008

The adjacent SSCP does not support the requested CDINIT function (for example, notification of resource availability or XRF).

000A

An SSCP is unable to reroute a session services request because the request was 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.

LUA_RU_LENGTH_ERROR

The requested RU was too long or too short. The RU was delivered to the intended half-session component, but it could not be interpreted or processed. This condition represents a mismatch of half-session capabilities.

This code can also appear as a sense code in an EXR.

LUA_FUNCTION_NOT_SUPPORTED

The function that was requested is not supported by LUA. The function may have been specified by a formatted request code, a parameter in an RU, or a control character.

Bytes 2 and 3 that follow the sense code are not used for user-defined data. These bytes contain sense-code-specific information. The following setting is allowed:

0000

The requested function is not supported by LUA.

The RU was delivered to the intended half-session component, but it could not be interpreted or processed. This condition represents a mismatch of half-session capabilities.

LUA_HDX_BRACKET_STATE_ERROR

A protocol machine determined that the current request could not be sent under the existing state error.

LUA_RESPONSE_ALREADY_SENT

A protocol machine determined that the current request could not be sent because a response for the chain had already been sent.

LUA_EXR_SENSE_INCORRECT

The application issued a negative response for a previously received exception request. The sense code in the response was not acceptable.

If the sense code in the exception request is X'0813000', the sense code in the negative response can be either X'08130000' or X'08140000'. In all other cases, the sense code in the negative response must be the same as the sense code in the exception request.

LUA_RESPONSE_OUT_OF_ORDER

A protocol machine determined that the current response was not issued to the oldest request.

LUA_CHASE_RESPONSE_REQUIRED

A protocol machine determined that the current request is being attempted with an older CHASE request outstanding.

LUA_CATEGORY_NOT_SUPPORTED

A DFC, SC, NC, or FMD request was received by a half-session not supporting any requests in that category, a network services (NS) request byte 0 was not set to a defined value, or byte 1 was not set to an NS category by the receiver.

LUA_CHAINING_ERROR

An error occurred in the sequence of the chain indicator settings, such as first, middle, first. A request header or a request unit that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_BRACKET

The sender did not enforce bracket rules for the session. A request header or request unit that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_DIRECTION

A normal-flow request was received while the half-duplex flip-flop state was NOT_RECEIVE. A request header or request unit that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_DATA_TRAFFIC_RESET

An FMD or normal-flow DFC request was received by a half-session whose session activation state was active, but whose data traffic state was not active. A request header or a request unit that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_DATA_TRAFFIC_QUIESCED

An FMD or a DFC request, received from a half-session that sent a QC command or a SHUTC command, has not responded to a RELQ command. A response header or request unit that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_DATA_TRAFFIC_NOT_RESET

A session control request was received while the data traffic state was not reset. A request header or request unit that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_NO_BEGIN_BRACKET

A BID or an FMD request that specified BBI=BB was received after the receiver had previously sent a positive response to a BIS command. A request header or request unit that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_SC_PROTOCOL_VIOLATION

An SC protocol was violated. A request allowed only after a successful exchange of an SC request and its associated positive response was received before a successful exchange occurred. Byte 4 of the sense data contains the request code. There is no user data associated with this sense code. A request header or request unit that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_IMMEDIATE_REQ_MODE_ERROR

The immediate request mode protocol was violated by the request. An RH or RU that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_QUEUED_RESPONSE_ERROR

The Queued Response protocol was violated by a request; for example, QRI=¬ QR when an outstanding request has QRI=QR. An RH or an RU that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_ERP_SYNC_EVENT_ERROR

The ERP synchronous event protocol was violated. An RH or an RU that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_RSP_BEFORE_SENDING_REQ

An attempt was made in half-duplex (flip-flop or contention) send/receive mode to send a normal-flow request when a response to a previously received request has not yet been sent. An RH or an RU that is not allowed for the receiver's current session control or data flow control state was detected. This error prevents delivery of the request to the intended half-session component.

LUA_RSP_CORRELATION_ERROR

A response was received that cannot be correlated with a previously sent request, or a response was sent that cannot be correlated with a previously received request.

LUA_RSP_PROTOCOL_ERROR

A response was received from the primary half-session that violated the response protocol, such as:

• A positive response (+RSP) was received for an RQE chain.
• Two responses were received for one chain.

LUA_INVALID_SC_OR_NC_RH

The RH of a session control (SC) or network control (NC) request was not valid. For example, an SC RH with the pacing request indicator set to 1 is not valid. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the sender's failure to enforce session RU.

LUA_BB_NOT_ALLOWED

The begin bracket indicator (BB) was specified incorrectly; for example, BBI=BB with BCI=¬BC. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_EB_NOT_ALLOWED

The end bracket indicator (EB) was specified incorrectly; for example, by EBI=EB with BCI=¬BC, or by the primary half-session when only the secondary can send an EB, or by the secondary half-session when only the primary can send an EB. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_EXCEPTION_RSP_NOT_ALLOWED

An exception response was requested when it was not permitted. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_DEFINITE_RSP_NOT_ALLOWED

A definite response was requested when it was not permitted. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_PACING_NOT_SUPPORTED

The pacing indicator was set on a request, but the receiving half-session or the boundary function half-session does not support pacing for this session. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_CD_NOT_ALLOWED

The change-direction indicator (CD) was specified incorrectly; for example, CDI=CD with ECI=¬EC or CDI=CD with EBI=EB. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_NO_RESPONSE_NOT_ALLOWED

No-response was specified on a request when it was not permitted. No-response is used only on EXR. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_CHAINING_NOT_SUPPORTED

The chaining indicators (BCI and ECI) were specified incorrectly; for example, chaining bits other than BCI=BC and ECI=EC were indicated, but multiple-request chains are not supported for the session or for the category specified in the request header. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent the delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_BRACKETS_NOT_SUPPORTED

The bracket indicators (BBI and EBI) were specified incorrectly; for example, a bracket indicator was set (BBI=BB or EBI=EB), but brackets are not used for the session. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_CD_NOT_SUPPORTED

The change-direction indicator was set, but is not supported. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_INCORRECT_USE_OF_FI

The format indicator (FI) was specified incorrectly; for example, the FI was set with BCI=¬BC or the FI was not set on a DFC request. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_ALTERNATE_CODE_NOT_SUPPORTED

The code selection indicator (CSI) was set when it was not supported for the session. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_INCORRECT_RU_CATEGORY

The RU category indicator was specified incorrectly; for example, an expedited-flow request or a response was specified with the RU category indicator = FMD. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_INCORRECT_REQUEST_CODE

The request code on a response does not match the request code on its corresponding request. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_INCORRECT_SPEC_OF_SDI_RTI

The sense-data-included indicator (SDI) and the response-type indicator (RTI) were not specified correctly on a response. The proper value pairs are (SDI=SD, RTI=negative) and (SDI=¬SD, RTI=positive). The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_INCORRECT_DR1I_DR2I_ERI

The definite response 1 indicator (DR1I), the definite response 2 indicator (DR2I), and the exception response indicator (ERI) were specified incorrectly. For example, a CANCEL request was not specified with DR1I=DR1, DR2I=¬DR2, and ERI=¬ER. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_INCORRECT_USE_OF_QRI

The queued response indicator (QRI) was specified incorrectly; for example, QRI=QR on an expedited-flow request. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_INCORRECT_USE_OF_EDI

The enciphered data indicator (EDI) was specified incorrectly; for example EDI=ED on a DFC request. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_INCORRECT_USE_OF_PDI

The padded data indicator (PDI) was specified incorrectly, such as PDI=PD on a DFC request. The value of a parameter or combination of parameters in the RH violates the architectural rules or previously selected LOGON options. These errors prevent delivery of the request to the intended half-session component and are independent of the current states of the session. These errors might result from the failure of the sender to enforce session rules.

LUA_NAU_INOPERATIVE

The NAU is unable to process requests or responses. For example, the NAU was disrupted by an abnormal end. The request could not be delivered to the intended receiver, because of a path outage, an incorrect sequence of activation requests, or one of the listed path information unit (PIU) errors. A path error that is received while the session is active generally indicates that the path to the session partner is lost.

LUA_NO_SESSION

No half-session is active in the receiving end node for the indicated origin-destination pair or no boundary function half-session component is active for the origin-destination pair in a node that provides the boundary function. A session activation request is needed. The request could not be delivered to the intended receiver because of a path outage or an incorrect sequence of activation requests. A path error that is received while the session is active generally indicates that the path to the session partner is lost.

LUA_BRACKET_RACE_ERROR

A loss of contention within the bracket protocol occurred. When bracket initiation or bracket termination by both NAUs occurs, contention is lost. The intended half-session component understood the supported request, but did not process it.

LUA_BB_REJECT_NO_RTR

A BID or a begin-bracket indicator was received while the first speaker was in the in-bracket state or while the first speaker was in the between-brackets state. The first speaker denied permission. No RTR command will be sent. The intended half-session component understood the supported request, but did not process it.

LUA_CRYPTOGRAPHY_INOPERATIVE

The receiver of a request was not able to decipher the request because of a malfunction in its cryptography facility. The intended half-session component understood the supported request, but did not process it.

LUA_SYNC_EVENT_RESPONSE

A negative response to a synchronizing request was received. The intended half-session component understood the supported request, but did not process it.

LUA_RU_DATA_ERROR

Data in the request RU is not acceptable to the receiving FMDS component. For example, a character code is not in the set that is supported, a formatted data parameter is not acceptable to presentation services, or a required name in the request has been omitted. The RU was delivered to the intended half-session component, but it could not be interpreted or processed. This condition represents a mismatch of half-session capabilities.

LUA_INCORRECT_SEQUENCE_NUMBER

The sequence number that was received on a normal-flow request was not greater than the last sequence number. A sequence number error or an RH or RU that is not allowed for this receiver's current session control or data flow control state was detected. This error prevents the delivery of the request to the intended half-session component.