ftp.microsoft.com /bussys/winnt/sna-public/fixes/sna30/hotfixes-postsp1/appc-fix "APPC" Update to SNA Server 3.0 Service Pack 1 Last updated: July 3, 1997 The enclosed updates to SNA Server 3.0 Service Pack 1 correct various problems found when using different third party products over the SNA Server APPC interface. The problem descriptions are included below, along with the knowledgebase article number, internal SNA Server bug number, and module name containing the fix: Q170070 7724 SNA Client Allocate Requests May Hang After AS/400 IPL Module updated: \system\SNASERVR.EXE Q170776 7924 TP_STARTED may hang if NT application opens > 256 TP's Module updated: \system\WAPPC32.DLL Q170071 7700 Invokable TP Timeout May Occur With Non-queued Operation Modules updated: \system\SNADMOD.DLL (for Windows NT) \system\DMODAPPC.DLL (for Windows 95) Q170289 7830 DISPLAY or CNOS calls fail with UNEXPECTED_DOS_ERROR Module updated: \system\WAPPC32.DLL NOTE: Fixes to these problems will be included in the upcoming SNA Server 3.0 Service Pack 2, scheduled for late summer 1997. Microsoft recommends upgrading to Service Pack 2 when it is available. Modules updated (for Intel systems only): \system\SNASERVR.EXE 06/27/97 12:15p 462,432 (build 439) \system\WAPPC32.DLL 06/27/97 12:15p 253,120 (build 439) \system\SNADMOD.DLL 05/22/97 07:11p 459,472 \system\DMODAPPC.DLL 05/23/97 11:51a 83,968 (SNA Windows 95 client) \symbols\exe\SNASERVR.DBG 06/27/97 12:15p 428,032 (symbol file) \symbols\dll\SNADMOD.DBG 05/22/97 07:11p 605,384 (symbol file) \symbols\dll\WAPPC32.DBG 06/27/97 12:15p 114,424 (symbol file) Applying the update: -------------------- WARNING: The updated SNADMOD.DLL will only function on systems which are already running SNA Server 3.0 Service Pack 1. This service pack must first be applied before this update is applied. The self-extracting service pack file (for Intel systems) can be located on ftp.microsoft.com, under /bussys/winnt/sna-public/fixes/sna30/ussp1/30sp1is.exe - Stop the SNA Server service and SnaBase service (on the server) - Rename the existing modules on the SNA Server machine: rename \system\snaservr.exe snaservr.sp1 rename \system\snadmod.dll snadmod.sp1 rename \system\wappc32.dll wappc32.sp1 - Apply the updated modules copy SNASERVR.EXE \system\snaservr.exe copy SNADMOD.DLL \system\snadmod.dll copy WAPPC32.DLL \system\wappc32.dll - for Windows NT client machines, apply the updated SNADMOD.DLL and WAPPC32.DLL - for Windows 95 client machines, apply the updated DMODAPPC.DLL NOTE: Symbol files (with *.DBG extension) do not need to be applied for the updates to function. These are only needed if further troubleshooting is required, as directed by Microsoft support personnel. =========================================================================== SNA Client Allocate Requests May Hang After AS/400 IPL [sna] ID: Q170070 CREATED: 13-JUN-1997 MODIFIED: 16-JUN-1997 PUBLIC | -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server for Windows NT, version 2.11, 2.11 SP1 & SP2, 3.0, 3.0 SP1 -------------------------------------------------------------------------- SYMPTOMS ======== If an APPC or CPIC application issues several conversation startup requests (i.e. [MC_]ALLOCATE or CMALLC) immediately after an AS/400 IPL, some allocates may fail to complete, or complete after further client ALLOCATE's are issued. This problem occurs after SNA Server renegotiates session limits for an LU/LU pair, where some pending client ALLOCATE request are queued incorrectly and fail to be processed. The symptoms of the problem may vary, based on the application being used. This problem would occur most commonly with an APPC or CPIC application which initiates many conversations concurrently to the same remote system (say, an AS/400 or CICS). It would be unlikely to occur when starting a single conversation (for example, 5250 emulation) on multiple client machines. CAUSE ===== After the remote system is stopped and started (the AS/400 in this example), the existing session limits on all LU6.2 pairs have not been reset. If one or more users attempts to activate a new LU6.2 session at the same time, after the remote system has been reactivated, the remote system rejects the BIND request with sense code 08050000 (session limit exceeded), which causes SNA Server to reinitiate change-number-of-sessions (CNOS) renegotiation with the remote system. The problem is that SNA Server was incorrectly queueing the user's initial activation requests after CNOS renegotiation has taken place, causing the client application to hang on the ALLOCATE request (for an APPC application) or CMALLC request (for a CPIC application). RESOLUTION ========== An update to SNA Server 3.0 Service Pack 1 is available to correct this problem. The updated module is SNASERVR.EXE. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server version 2.11 (including SP1 and SP2) and SNA Server 3.0 (including SP1). A supported fix is now available for systems running SNA Server 3.0 Service Pack 1, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information. KBCategory: kbbug kbnetwork KBSubcategory: prodsna snaserverservice snaappc snacpic lu62 Additional reference words: =========================================================================== TP_STARTED may hang if NT application opens > 256 TP [sna] ID: Q170776 CREATED: 27-JUN-1997 MODIFIED: 30-JUN-1997 PUBLIC -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server for Windows NT, version 2.11, 3.0 -------------------------------------------------------------------------- SYMPTOMS ======== After opening more than 255 transaction programs from a single Windows NT application, a TP_STARTED request may hang. CAUSE ===== The internal APPC callback function for the get_server_list and get_default_lu's RPC calls was assuming that SNADMOD would return only an 8 bit TP control block index. However, if the application has already opened more than 256 TP's, the SNADMOD could return a larger value, causing the APPC interface to fail to respond to the TP_STARTED request. RESOLUTION ========== A hotfix for SNA Server 3.0 (post SP1) is available from Microsoft. The updated module is \system\WAPPC32.DLL. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server version 2.11 and 3.0. A supported fix for 3.0 (post SP1) is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information. KBCategory: kbnetwork kbbug kbprg KBSubcategory: prodsna snaappc snacpic snaprog Additional reference words: idea =========================================================================== Invokable TP Timeout May Occur With Non-queued Operation [sna] ID: Q170071 CREATED: 13-JUN-1997 MODIFIED: 16-JUN-1997 -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server for Windows NT, versions 2.11, 3.0 -------------------------------------------------------------------------- SYMPTOMS ======== When attempting to invoke a non-queued Win32 autostarted APPC or CPIC application configured to run on an SNA Server Windows NT or Windows 95 client machine, the following error may occur: Event ID: 60 Failed to invoke APPC TP , sense data = 084C0000 SNA client-side traces reveal that the application is invoked and correctly posts a RECEIVE_ALLOCATE (or CMACCP) before the dynamic load request for the TP arrives, though the RECEIVE_ALLOCATE (or CMACCP) never completes and the above dynamic load timeout error is logged. CAUSE ===== Due to changes implemented within SNA Server 2.11 (and later versions) to support IBM CICS for Windows NT, invokable APPC TP's which require non-queued operation may occasionally experience dynamic load timeout problems along with Event 60. RESOLUTION ========== An update to the SNA Server 3.0 Windows NT and Windows 95 client is available to correct this problem (post-SP1) . With this update applied, a new registry setting can be configured to disable this special support for the IBM CICS product: CicsSupport: REG_DWORD: 0 where: 0 = disable support for IBM CICS for Windows NT 1 = enable support (the default) If the initial invokable TP is written as a Windows NT service, then the registry key value to add exists in: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/ /Parameters/ If the initial invokable TP is written as a Windows NT application, then the registry key value to add exists in: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/SnaBase/Tps //Parameters/ If the initial invokable TP is configured to run on a Windows 95 client, then the registry key value to add exists in: HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/SnaBase/Parameters/TPs //Parameters/ where is the APPC or CPIC transaction program name. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server version 3.0 and 3.0 Service Pack 1. A supported fix is now available for 3.0 Service Pack 1, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information. KBCategory: kbbug kbnetwork kbinterop kbprg KBSubcategory: prodsna sna3rdparty snaappc snatp snaprog Additional reference words: SAS =========================================================================== DISPLAY or CNOS calls fail with UNEXPECTED_DOS_ERROR [sna] ID: Q170289 CREATED: 17-JUN-1997 MODIFIED: 18-JUN-1997 PRODUCT: SNA -------------------------------------------------------------------------- The information in this article applies to: - Microsoft SNA Server for Windows NT, versions 2.11, 3.0 -------------------------------------------------------------------------- SYMPTOMS ======== When calling the DISPLAY or CNOS functions on Windows NT (over the SNA Server Windows NT client software), these functions may eventually fail with the following error: primary_rc = 0xF011 (UNEXPECTED_DOS_ERROR) secondary_rc = 593 (internal error - maximum routing procs defined) CAUSE ===== This problem can occur when an APPC application calls WinAPPCStartup and WinAPPCCleanup a number of times without being terminated. The APPC library registers an internal routing procedure for each call to WinAPPCStartup, but fails to deregister the routing procedure when the application calls WinAPPCCleanup. This causes the internal routing procedure table to fill, leading to the above error. RESOLUTION ========== A hotfix to SNA Server 2.11 (post SP2) and 3.0 (post SP1) is available to correct this problem. The updated module is WAPPC32.DLL. STATUS ====== Microsoft has confirmed this to be a problem in SNA Server version 2.11 (post SP2) and 3.0 (post SP1). A supported fix is now available for both 2.11 and 3.0, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information. KBCategory: kbnetwork kbbug kbprg KBSubcategory: prodsna winappc wincpic snaprog Additional reference words: SAS