SNANLS API Problems Using Far-East Codepages

 Last reviewed: April 14, 1997
Article ID: Q164642
The information in this article applies to:
  • Microsoft SNA Server version 3.0.

SYMPTOMS

There are two problems which can occur when calling the SNANLS API using Far East code pages (such as Japan and China):

  • Incorrect return codes may be returned.
  • There is no support for Unicode to double-byte character set (DBCS) extended binary coded decimal interchange code (EBCDIC) conversion.

CAUSE

This is a problem with the SNANLS API.

RESOLUTION

The SNANLS API libraries have been modified so that: 

   Correct return codes are now returned from the TrnsDt API.

   -and-

   Unicode to DBCS EBCDIC conversion is now supported.
The updated modules are \<snaroot>\System\Snanls.dll for Microsoft SNA Server, Windows NT, and Windows 95 clients.

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: prodsna snaprog sna30
Keywords : kbbug3.00 kbfix3.00.sp1 kbnetwork prodsna snaprog
Version : 3.0
Platform : WINNT
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.