BIND -RSP for Host-Initiated Dependent LU6.2 Sessions

Last reviewed: April 14, 1997
Article ID: Q165647

The information in this article applies to:

Microsoft SNA Server version 3.0

SYMPTOMS

SNA Server 3.0 sends a negative response to a BIND sent by a host for a dependent LU6.2 session even though the BIND is correct. If the BIND is elicited by SNA Server sending an INIT-SELF, the BIND is responded to positively. When the host initiates the BIND, SNA Server may reject it with sense code 0835xxxx (where xxxx offset may vary)

CAUSE

This was a problem found in the SNA Server service.

RESOLUTION

A fix was made to the SNA Server service to resolve this issue. To resolve this problem, obtain the hotfix mentioned below.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0. This problem was corrected in the latest Microsoft SNA Server 3.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

Additional query words: cics appc lu62
Keywords : kbbug3.00 kbfix3.00.sp1 kbnetwork prodsna snaappc snaserverservice
Version : 3.0
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

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: April 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.