PSS ID Number: 96872
Article Last Modified on 10/3/2003
The information in this article applies to:
- Microsoft Embedded SQL for COBOL 4.2
This article was previously published under Q96872
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:
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.
Keywords: kb3rdparty KB96872
Technology: kbAudDeveloper kbSQLEmCOBOL kbSQLServSearch kbZNotKeyword3
