SYMPTOMS
If the host sends an UNBIND in response to an SNA Server BIND attempt to
activate independent LU6.2 sessions, SNA Server logs the following event
into the Windows NT application event log:
Event: 18
Description: APPC session activation failure: BIND negative response
or UNBIND request received:
Sense data = 0032xxxx
Connection = <connection name>
LU alias = <local LU name>
PLU alias = <remote LU name>
Mode name = < SNASVCMG or LU6.2 mode name>
where 0032 means UNBIND, and xxxx is the unbind type. Under SNA Server 2.1,
the "unbind type" is converted internally as follows:
Event log Actual UNBIND type
-------------------------------
0007 FE session failure
0008 0F cleanup
0009 06 invalid session parameters
0010 0C unrecoverable LU failure
Under SNA Server 2.11 or 3.0, the actual unbind type is logged in the
"sense data" field in Event 18.
Note that 0032xxxx is not SNA Sense data.
NOTE: Chapter 5 of the "IBM SNA Formats Guide" lists all unbind types and
their format. The most common unbind type logged during session activation
is:
This indicates the route extension used by the LU-LU session has become
inoperative, thus forcing the deactivation of the identified LU-LU session.
NOTE: The Sense data field includes an SNA sense code if the host responds
with SNA sense data instead of an UNBIND. SNA sense data codes are listed
in Chapter 9 of the "IBM SNA Formats Guide".