PRB: ESQL: Error When Compiling COBOL Application in OS/2 2.0

Last reviewed: April 28, 1997
Article ID: Q96872
The information in this article applies to:

  - Microsoft Embedded SQL version 4.2 for COBOL

SYMPTOMS

You may compile and link embedded SQL for COBOL (ESQL/COBOL) applications under OS/2 2.0. However, you may have to manually modify certain configuration files in order to make it work correctly.

When compiling an ESQL/COBOL application, you may encounter the following compiler errors:

   Load failure (173) on file C:\COBOL\EXEDLL\_SQLPRM.DLL
   Description: Called program file not found in
      driver/directory (173)

However, when you check the C:\COBOL\EXEDLL directory, the file _SQLPRM.DLL is there. Moreover, the C:\COBOL\EXEDLL directory is on both LIBPATH and PATH.

CAUSE

This error will occur when the compiler cannot locate the run time support modules (DLL files) that come with the ESQL package.

By default, the ESQL installation program will automatically update the CONFIG.SYS file to put the DLL directory on the LIBPATH. However, under OS/2 2.0, the CONFIG.SYS file may reside on drive D if you choose to, leaving drive C for other operating systems such as MS-DOS. This will cause the ESQL installation program to update the wrong CONFIG.SYS file on drive C, while leaving the correct CONFIG.SYS not updated. As a result, the ESQL DLL directory will not be on the LIBPATH, which will cause the above error to occur.

WORKAROUND

Check the correct CONFIG.SYS file to make sure the ESQL DLL directory is on the LIBPATH. Manually modify this file so that this directory is the first on the LIBPATH.


Additional query words:
Keywords : kb3rdparty
Version : 4.2
Platform : OS/2


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