Error Codes for Status-Error Messages
The possible error codes delivered to the function management interface (FMI) application on Status-Error messages are tabulated in the following table. A Status-Error message is delivered to the application in one of several cases, as shown in the following list:
The local node detects an error in a response sent from the application (as a Status-Acknowledge or Status-Control Ack/Nack-1 message).
The local node detects an error in some data from the host that will not be delivered to the application as an system detected error indicator (SDI) message (such as an expedited flow request).
The application sends an invalid Status message.
For inbound responses, the Status-Error codes have first byte 0x00. When the application is in error, the table indicates whether the error is critical, applying to the primary logical unit (PLU) connection only. If the error is critical, the application will receive a Close(PLU) Request as the next message.
The sense codes beginning with 0x40 will only be delivered if the corresponding receive check has been enabled in the connection information control block (CICB) on the Open(SSCP) Request from the application.
Where the sense code is marked with the * symbol, the second word of sense information carries the request code of the expedited flow request that was in error (for example 0x00C9 for SIGNAL).
Negative response already sent to this chain.
Invalid Status message from application.
Session failure due to correlation table shortage.
Invalid sequence number on Status-Ack.
Application may not send status control (STSN) negative acknowledge if it supports transaction numbers.
Status-Ack sent when previous RQD chains are outstanding. (For more information, see Outbound Data.)
Message received when pacing count is zero.
BIND from another PLU when already bound.
Mode inconsistency (QEC or SHUTD).
BIND from same PLU when already bound.
Incorrect ACTLU type (SSCP connection).
Wrong profile/network control request/invalid session control message.
Data traffic reset.
Data traffic not reset (STSN after SDT).
Change direction (CD) not allowed.
Chaining not supported.
Brackets not supported.
Incorrect use of FI.
Incorrect use of request/response unit (RU) category.
Incorrect use of definite response 1 (DR1), definite response 2 (DR2), exception response (ER).