SNAX/APN Application Programming Manual

The SNALU Interface
SNAX/APN Application Programming Manual—420111-001
4-23
SNALU Application Terminates Session With
Remote SLU
A quick way of detecting positive responses is to test the value of the RTI control bit in
the RH header (bit 3 of the eighth byte in the application I/O buffer); if it is clear
(RTI= 0), the response is positive. The SNALU application may also want to check the
request code and sequence number to verify the request to which it is responding.
Table 4-7 shows how a negative response appears to an UNBIND request in the
application’s buffer.
For negative responses, the SNALU application should examine at least the sense data
(bytes 9 through 12 of the incoming record) to determine why the SLU responded
negatively. As with positive responses, it might also check the request code and
sequence number to verify which request is being responded to.
Bytes 9 through 12 of a negative response contain a 4-byte SNA sense code that
specifies why the request was rejected. The sense codes are described in the IBM
System Network Architecture: Network Product Formats manual.
Table 4-6. Positive Response to UNBIND Request
Byte Description
0-8 SNAX header
(0-1) X’0100’ TC indicators field: EFI=1
(2-3) X’0000’ Status codes field
(4-5) Sequence number field
(6-8) X’6B8000’ RU category: session control
RH indicators: RRI=0,FI=DR1I=1
9 Request code (X’32’ for UNBIND)
Table 4-7. Negative Response to UNBIND Request
Byte Description
0-8 SNAX header
(0-1) X’0100’ TC indicators field: EFI=1
(2-3) X’0000’ Status codes field
(4-5) Sequence number field
(6-8) X’EF9000’ RU category: session control
RH indicators: RRI=1, FI=SDI=1, DR1I=RTI=1
9-12 Sense data
13 Request code (X’32’ for UNBIND)