The information in this article applies to:
SYMPTOMS
An SDLC connection from SNA Server to a front-end processor (FEP) remains
in a pending state after the host performs an IPL. The only means of
recovery is to stop and restart the SNA Server service.
CAUSESNA Server is erroneously handling the non-activation XIDs sent from the FEP on an SDLC connection and treating this as a connection outage. STATUS
Microsoft has confirmed this to be a problem in SNA Server versions 2.11,
2.11 Service Pack 1 (SP1), and 2.11 SP2. A supported fix is now available
for 2.11 SP2, 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
Technical Support for more information.
Microsoft has confirmed this to be a problem in SNA Server versions 3.0,
3.0 SP1, 3.0 SP2, and 4.0.
S E R V P A C K MORE INFORMATION
With the fix applied, the Ibmsdlc.DLL interface allows for the correct
handling of SDLC non-activation XIDs.
Additional query words: 0xA1 0x25 IPL pending connection
Keywords : kbnetwork kbbug4.00 kbbug3.00 kbbug3.00.sp2 kbfix3.00.sp3 kbbug2.11 kbbug2.11.sp1 kbbug2.11.sp2 kbbug3.00.sp1 snasdlc |
Last Reviewed: November 17, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |