ID: Q118362
The information in this article applies to:
The following is the README.TXT file that accompanies SNA Server 2.0 patch 49 (SNA20.P49):
Note that this article reflects the text of a static document. Therefore, some of the information in this article may be outdated. For example, as of May 20, 1996, Microsoft no longer maintains support forums on CompuServe.
******************* Beginning of Readme ***************************
Product: Microsoft SNA Server for Windows NT v2.0 Update: Patch #49 (includes Patch #5, 11, 34, 37, 42, 47) Status: Confirmed
Date: July 14, 1994
Modules updated:
\SYSTEM\SNASERVR.EXE 07/14/94 01:59p 524,800 (2.0.0.148)
2394 SNA Server application exception under 3270 client stress.
Under 3270 client stress, a freed internal buffer was subsequently reused in error, causing an application exception. The DRWTSN32.LOG shows the failing service as snaservr.exe, in routine s1pduhxr.
2262 SNA Server 3270 problem with Network Control Program v6.2
Following an IBM 3745 upgrade to Network Control Program version 6.2, SNA Server 3270 users no longer receive their 3270 host signon screen, though the 3270 LU's appear as "Available" in SNA Server Admin. Traces showed that the host was failing to respond to SNA Server NOTIFY requests (due to a host problem), causing SNA Server to wait for this host response and causing the session to be unusable. To get around this, a workaround was implemented in the SNA Server service so processing can continue, even if the host fails to respond to the NOTIFY message.
To implement this workaround, this server version must be used and the following registry setting must be enabled using REGEDT32:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Snaservr/Parameters:
NONOTIFYRSP:REG_SZ:YES
A customer had written their own APPC program which supported both invokable and invoking APPC transaction programs. However, their operator started TP's were configured in the registry as autostarted TP's (via snaservicetype:reg_sz:0x5). Under this configuration, there were instances where the SNA Server service would encounter an application exception in the "s1puc62" routine. This update corrects this problem.
2195 SNA Server DSPU connections not reactivating (Patch 42)
The fix for #2073 was not complete. While the internal gateway error log entry no longer occurs during deactivation, this update fixes an additional problem where downstream PU connections would not reactivate.
2073 SNA Server internal gateway error (event 29, sense code 4596).
Observed when using the "exit all" option with the IBM PCOM 3270 emulator running as a downstream PU to SNA Server. If an outage occurs from a downstream PU after an Unbind request is sent to the host, but the Unbind response not yet received, SNA Server sends a termself (which the host rejects). However, the host then sends the Unbind response which the server is not expecting, so it logs an error and fails to send the Notify(unavail) that the host is expecting. The LU is lost until SNA Server is recycled.
XXXX Invalid SNA Server BIND response leads to sense code 1001000E.
SNA Server responds with all control vectors in response to a host BIND message, though not all control vectors may be valid for the response. This can lead to a host sense code of 1001000E, or invalid bind response.
2020 SNA Server hot backup fix for 5250 users.
When more than one SNA Server is configured to support 5250 sessions (for hot backup purposes) and the link fails on one of the servers, the client occasionally has to reopen a new session twice before getting a session through the backup server.
1739 Server gp-fault when LU pool is opened and connections inactive
Start the SNA Server service but leave all connections inactive. At the client, open an LU Pooled session using the 3270 applet. The customer reports that the SNA Server encounters an access violation, though we have been unable to reproduce the problem.
1765 Automatic 5250 device name generation fails after 10 users
This fix applies if over 10 SNA Server users are using the 5250 applet and sharing the same LU/LU pair when communicating to the AS/400, and they are not specifying their own unique device names when opening a session. Under this situation, SNA Server automatically generates unique device names for each client (to prevent conflicts in the use of device names). However, after 10 users, SNA Server fails to generate valid unique device names.
Update Procedure:
- Stop the SNA Server service
- Copy the updated SNASERVR.EXE over the existing version in the server's <snaroot>\SYSTEM directory.
- Restart SNA Server
*********************** End of Readme *******************************
SNA Server 2.0 patches are located on:
1. Library #2 of the MSSNA CompuServe forum.
2. The Internet server under BUSSYS\SNASRVR\SUP-ED\FIXES\ (supported
patches) OR on BUSSYS\SNASRVR\UNSUP-ED\FIXES\ (unsupported patches).
Last Reviewed: April 23, 1996