Error Codes for Status-Error Messages

The possible error codes delivered to the FMI application on Status-Error messages are tabulated below. A Status-Error message is delivered to the application in one of several cases:

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 or not (applying to the 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 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).

Error /
Sense code
Critical
YES/NO
Description
0x0008 NO Negative response already sent to this chain.
0x0040 YES Invalid Status message from application.
0x0046 YES Session failure due to correlation table shortage.
0x0050 YES Invalid sequence number on Status-Ack.
0x0053 YES Application may not send status control (STSN) negative acknowledge if it supports transaction numbers.
0x0056 YES Status-Ack sent when previous RQD chains are outstanding (see Outbound Data).
0x0801 NO Message received when pacing count is zero.
0x0805 NO BIND from another PLU when already bound.
0x0809 * NO Mode inconsistency (QEC or SHUTD).
0x0815 NO BIND from same PLU when already bound.
0x0821 NO Incorrect ACTLU type (SSCP connection).
0x1003 * NO Wrong profile / network control request / invalid session control message.
0x2005 NO Data traffic reset.
0x2007 NO Data traffic not reset (STSN after SDT).
0x4009 * NO CD not allowed.
0x400B * NO Chaining not supported.
0x400C * NO Brackets not supported.
0x400F * NO Incorrect use of FI.
0x4011 * NO Incorrect use of RU category.
0x4014 * NO Incorrect use of DR1, DR2, ER.