SNA Server Handling of 3270 LU Session Cleanup (132436)
The information in this article applies to:
- Microsoft SNA Server 2.0
- Microsoft SNA Server 2.1
- Microsoft SNA Server 2.11
- Microsoft SNA Server 2.11 SP1
- Microsoft SNA Server 2.11 SP2
- Microsoft SNA Server 3.0
- Microsoft SNA Server 3.0 SP1
- Microsoft SNA Server 3.0 SP2
- Microsoft SNA Server 3.0 SP3
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 SP1
- Microsoft SNA Server 4.0 SP2
- Microsoft SNA Server 4.0 SP3
- Microsoft SNA Server 4.0 SP4
- Microsoft Host Integration Server 2000
- Microsoft Host Integration Server 2000 SP1
This article was previously published under Q132436 SUMMARYIMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry When using pooled 3270 LUs with SNA Server, a 3270 user may access the
previous user's host application session. This occurs when the host did not
clean up the 3270 application after receiving a TERM-SELF message from SNA
Server on the session. If this occurs, the NOTERMSELF:REG_SZ:YES registry
setting should be used to force SNA Server to send an UNBIND(Cleanup) when
the user ends their 3270 session, or when the user's client-server LAN
session is lost.
The NOTERMSELF registry setting is described below, and in the SNA Server
2.1 or 3.0 "Reference Guide".
Modification Type: | Minor | Last Reviewed: | 5/26/2003 |
---|
Keywords: | kbenv kbnetwork KB132436 kbAudDeveloper |
---|
|