LU6.2 Session May End Abnormally over Twinax Link

Last reviewed: November 5, 1997
Article ID: Q161193
The information in this article applies to:
  • Microsoft SNA Server versions, 2.0, 2.1, 2.11, and 2.11 SP1

SYMPTOMS

APPC transaction programs (TP) running against an AS/400 over a twinax connection may fail. When this occurs, the AS/400 unbinds the session reporting a sequence number error, UNBIND x'FE' with a sense code of 2001. SNA Server will log the following errors when this occurs:

   Event 38: APPC session deactivated abnormally, qualifier = 0003
   Event 20: Negative Response Received on Connection <value> (SENSE = 2001)

CAUSE

The AS/400 twinax link interface does not reliably support LU6.2 sessions that use send or receive pacing greater than one.

RESOLUTION

To solve this problem, the send and receive pacing window values in the APPC mode entry (QPCSUPP or QSERVER) should be set to 1.

NOTE: If twinax connection outages are occurring (causing Event 23 errors for the twinax connection), please see the following article in the Microsoft Knowledgebase for an unrelated problem:

  ARTICLE-ID: Q160980
  TITLE: Event ID 23, Qualifier 11 While Using Andrew or IBM Twinax Link


Additional query words: prodsna andrew ibm
Keywords : snatwinax kbnetwork kbprb
Version : 2.0 2.1 2.11 2.11.SP1
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.