The information in this article applies to:
SYMPTOMSThe following events are logged in the Windows NT Application Event Log after disconnecting a 5250 display session in the 5250 Applet included with SNA Server:
These events are logged even though the 5250 display session is properly
disconnected using the Session Disconnect option.
NOTE: Although this has only been observed with SNA Server's 5250 Applet, it could occur with any APPC application that calls the TEST_RTS_AND_POST verb to detect direction change for the conversation being used. CAUSEThe 5250 Applet included with SNA Server 3.0 Service Pack 2 was modified to use the APPC TEST_RTS_AND_POST verb to detect change of direction for its APPC conversation. This was done as a performance enhancement. After this change was made, disconnecting a 5250 session in the 5250 Applet causes the TEST_RTS_AND_POST verb to be cancelled. The mechanism used to cancel this outstanding verb causes the Event 92 and 38 to be logged. RESOLUTION
Microsoft has confirmed this to be a problem in SNA Server versions 3.0 SP2,
3.0 SP3, 4.0, and 4.0 SP1. We are researching this problem in SNA Server
version 3.0 and will post more information here in the Knowledge Base as it
becomes available.
S E R V P A C K MORE INFORMATION
In this case, the event 38 and 92 messages are benign and do not indicate a
problem. However, these events may be logged for other reasons that do
indicate a problem. The following is a more detailed explanation of the
Event 38 Qualifier 0005 event:
If a 5250 user is losing their emulation session unexpectedly (because of the client's network session being lost to the SNA Server), capture SNA Server client internal trace, a LU6.2 message trace, and an APPC API trace of the problem, along with a matching sniffer or Network Monitor trace showing the lost network session, and provide them to Microsoft support personnel. Additional query words:
Keywords : |
Last Reviewed: September 20, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |