Microsoft SNA Server 2.1 4/5/95 Status: Confirmed Modules updated: \system\SNASERVR.EXE 04/05/95 01:55p 435,316 (Intel version) \system\SNAEVENT.DLL 04/05/95 01:56p 347,940 (Intel version) \system\TRCSERVR.EXE 04/05/95 01:55p 717,972 (debug only) (current through hotfix build 283) Description of fixes: 2639 SNA Server incorrectly rejects host BIND +RSP if LU6.2 session security set and a large number of LU6.2 sessions were being autoactivated. 2874 SNA Server application exception if there is a long path to the SNA Server configuration file (greater than 50 characters). 2897 SNA Server application exception defaulting unique device names when users share QPCSUPP mode sessions. 2932 LU6.2 session not freed after 5250 printer client stopped or client-server LAN session is lost. When the print emulator is stopped, a Deallocate(ABEND) negative response is generated. However, if the LU6.2 session is in a receive state, this response can't be sent (according to LU6.2 protocol). If the application ends or the SNA Server client-server LAN session is lost, SNA Server now treats this condition as though the TP issued a TP_ENDED(HARD) which causes the session to be unbound immediately instead of trying to deallocate the conversation. 2940 Incoming connection over 802.2 ethernet link may fail to activate. Improving support for handling incoming XID's exposed a problem matching up flipped ethernet address on an incoming XID message. 2898 Correct tracing of LPI addresses within an SNA Server DLC trace (support issue). The Locality values will still not match in the Node and Link service traces - this was the case in SNA Server 2.0 as well. However, P and I values should always be the same for identical messages. L values leaving a component will always have a source of 1, and arriving at a component, the destination will be 1. 2907 When the remote system responds with Unbind(Cleanup) on an LU6.2 allocate, SNA Server incorrectly returns AP_ALLOCATION_FAILURE_NO_RETRY instead of AP_ALLOCATION_FAILURE_RETRY (related to fix for 2639 above). 3005 Downstream LUs not reactivated after upstream system sends DACTLU/ACTLU sequence. 3023 5250 Emulator session hangs pressing Attn key (Esc) several times. When a user presses the the Attention key a number of times, the 5250 session appears to hang up. Traces show emulator issuing a REQUEST_TO_SEND verb which gets to the server, but no SIGNAL is sent to the AS/400. LU6.2 is queuing SIGNAL requests when the chain send FSM is in pending response or pending send reply state. This is correct according to the LU6.2 architecture - however the architecture is incorrect in this case. Removed the case for queuing RTS so it always gets sent (to not queue this expedited message). 2817 SNA Server retries Open(Link) after link service responds with a nonrecoverable error (such as hardware initialization failure). 3032 Incoming connection responds with XID error when in inactive state. If SNA Server receives an XID on a connection configured for incoming calls, but the connection is in an Inactive state (i.e. disabled), SNA Server sends an XID containing an error vector in response. This causes some remote systems to fail to retry. SNA Server now sends no response to an XID when the connection is disabled, so that the remote system will retry the connection. 2847 SNA Server should default RENEGLIMITS to YES. This change causes the RENEGLIMITS setting to be enabled by default, as documented in Appendix C of the SNA Server Reference Guide. 2947 Event log should occur if NO2001 workaround is used. During SNA Server stress testing, a problem was found in the Windows NT 3.5 DLC.SYS driver that caused a duplicate DLC frame to be passed to SNA Server, causing SNA Server to drop the connection (causing SNA Server to issue a sense code of 2001). To workaround this, the following registry entry cna be set: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/SnaServr/Parameters NO2001:REG_SZ:YES When this setting is enabled and the condition occurs, SNA Server now reports the following event to the Windows NT application event log: 1021 Duplicate RU sequence number received and NO2001 environment option is set. 3053 SNA Server rejects null XIDs during xid negotiation. If SNA Server is processing an XID exchange (during connection activation, and the X.25 line goes down, SNA Server does not receive indication of line failure (because of pad). When X.25 lines comes up again, SNA Server receives polling null XIDs and rejects them. SNA Server now requires a Format 3 XID in response to a null XID during negotiation. 3094 SNA Server rejects bind response from IBM NS/Win. IBM NS/Win responds incorrectly to the SNA Server SNASVCMG mode bind message, causing SNA Server to reject the bind response. IBM NS/Win changes byte 6 of the bind response from 0x05 to 0xD1 (bit 7 is the setting which causes the problem). This update relaxes SNA Server bind response checking on this bit, since it is meaningless in a bind response anyway. 3134 Intermittent problem in SNA Server causing automatic reestablishment of LU6.2 sessions to fail when CICS is started, due to SNA Server timing problem in CNOS negotiation. Applying the update: - Stop the SNA Server service (Warning: This will cause all users to lose their SNA Server sessions). The service can be stopped through the SNA Admin program or from the Windows NT command line ("net stop snaserver"). - Rename the current version: rename \SYSTEM\SNASERVR.EXE SNASERVR.21 rename \SYSTEM\SNAEVENT.DLL SNAEVENT.21 - Apply the updated version: copy SNASERVR.EXE \SYSTEM copy SNAEVENT.DLL \SYSTEM - Restart the SNA Server service Note: Keep the TRCSERVR.EXE on the \SYSTEM directory in case this is needed by SNA Server support personnel.