Status-Session Codes
For the status codes used on Status-Session messages, the following table lists:
The value for the status code.
The valid qualifying codes (if any) and their values.
On which sessions the combinations of primary and qualifying status codes can occur.
For an overall description of the role of the Status-Session message, see Status-Session Message. The individual codes are discussed in SSCP Connection and PLU Connection.
Status code | Value | Qualifying code | Value | Usage |
---|---|---|---|---|
STNOSESS (no session) | 0x01 | STPUINAC STPUACT STPUREAC STLUINAC | 0x10 0x03 0x04 0x11 | SSCP SSCP SSCP SSCP |
STLINERR (link error) | 0x02 | DLC ERROR | (See Note 1) | SSCP |
STLUACT (LU active) | 0x05 | - | - | SSCP |
STLUREAC (LU reactivated) | 0x06 | - | - | SSCP |
STBETB (between brackets) | 0x07 | - | - | PLU |
Note
The qualifying status code supplied on a Status-Session link error is the error code supplied by the data link control layer of the local node.
Note
Status-Session link error code 20 is generated by the node rather than by the link service. It indicates that the link service is not yet available, but is being activated. Ignore this error code during session activation. Otherwise, all Status-Session link errors (including 20) will cause the emulator to send a Close(SSCP). When the emulator receives the Close(SSCP) Response, it will start again and send a new Open(SSCP).
Note
The session status identifier is obsolete. It was used by the Microsoft® SNA Server OS/2 and Microsoft MS-DOS®-based 3270 emulators. Its value was obtained by adding 484 (decimal) to the qualifying status code shown in the preceding table.