Hi Senthilkumar,

Runtime error 173 typically indicates that a program being called is not found. See documentation link for this: 
https://www.microfocus.com/documentation/enterprise-developer/ed90/ED-VS2022/HRERRHRERR3M.html

In the directory where the program DB2INT is expected you would expect to see a .dll / .INT /.GNT program, the 'DB2INT.obj' and 'DB2INT.idy' entries are not the ones that would be called. If the .dll / .INT /.GNT is missing then consider compiling and deploying that, then confirm if the issue persists.

Regards,
Kim

For information: You mentioned product Visual COBOL, but have posted this on the Enterprise Developer/Server forum. For information, there is a separate forum for Visual COBOL.

Hi Kim Hoskin ,

I can't find db2int.dll/.int.gnt file anywhere in the system. Will I get it somewhere or how?

Hi,
I do not recognize db2int being part of the Visual COBOL product. Is it part your own application (COBOL program), or from a 3rd party vendor such as DB2?
Is your batch file performing some SQL work, which SQL pre-processor is used, e.g. IBM's DB2 one?

Hi Kim,

We are not sure about whether DB2 is a third part vendor software and there is no program for DB2INT. Also searched the db2int.dll/.int/.gnt in the full machine and don't find anything.

We are doing some SQL work in the program and trying to connect the Sybase database from the program. So could you please help me to configure the Sybase DB in the program and how to call it from the program.

Thanks!

Hi,
The error is clear, you are trying to call a DB2INT program that is not being found, you should locate the missing program and copy that to the relevant directory to avoid the error.

If you require further support I recommend you to consider raising a support case to ask for further assistance that way, or seek help from our consulting team who can work closely with you and find a solution to your application requirement.

Thanks kim.

We will create a case for the technical support for the DB configuration and calling it in the program.

Hi,
Some additional information to add which may be relevant is:
DB2INT could also be an entry point within another program so there doesn't necessarily need to a .dll/.int/.gnt with that name. It could be that another program containing the entry point, if that is the case, needs to be loaded. It might even be an entry point in some third party code.

Hi,
Please consider the following also:
-As you have DB2INT.obj/DB2INT.idy files, can you check if you have a DB2INT.CBL in the directory, or on the machine? That may be the source file for the missing program.

-Also, as you have a DB2INT.obj you can create a DB2INT.DLL from that using the cbllink tool. To do this open a Visual COBOL command prompt (either 32 or 64bit one, match bitism of your application) > Navigate to the directory where you find the DB2INT.obj > run command: "cbllink -d DB2INT.obj" > Confirm a DB2INT.dll file is now seen. Check if the issue is resolved.

Hi Kim,

I have created DB2INT.dll file using DB2INT.obj file through Visual Cobol command prompt as you mentioned. Now I'm able to see DB2INT.dll file in the mail folder where I have the program. But getting below errors while building the solution. Do I need to worry about these errors or I shall try to clear the SQL errors that getting in the program.

Build started at 10:52 AM...
1>------ Build started: Project: Avpbgks, Configuration: Debug x86 ------
1>
1> * Cobsql Integrated Preprocessor
1> * CSQL-I-008: Invoking cp Preprocessor
1> * CSQL-F-010: Irrecoverable error writing STK record
1> * CSQL-E-023: File Status 4/ 8
1> COBOL compile: 0 item(s) succeeded or up-to-date, 1 failed.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========
========== Build completed at 10:52 AM and took 02.924 seconds ==========

Hi,
I suggest you to check:
-With the DB2INT.dll present, is the initial RTS 173 error still shown?
-Is the application running as expected now or not?

Looking at the Preprocessor events you share:
-Is this when you compile DB2INT or another program?
-For "CSQL-F-010: Irrecoverable error writing STK record", see this documentation link: www.microfocus.com/.../HRDBRHESQL1I.html

Hi Kim,

With the DB2INT.dll present, is the initial RTS 173 error still shown? - I got the db2int.dll file using db2int.obj file and placed in the main folder where the program available. I'm not getting the DB2INT related errors now.

Is the application running as expected now or not? - No, not getting expected all the files as output.

Is this when you compile DB2INT or another program? - No, it is appearing for main program where I'm trying to connecting the DB.

Hi, 
If the original 173 error is now shown anymore then you may want to consider creating a new forum post for the current question / issue.


Is the current issue that during a build of your application's solution you get:

Build started at 10:52 AM...
1>------ Build started: Project: Avpbgks, Configuration: Debug x86 ------
1>
1> * Cobsql Integrated Preprocessor
1> * CSQL-I-008: Invoking cp Preprocessor
1> * CSQL-F-010: Irrecoverable error writing STK record
1> * CSQL-E-023: File Status 4/ 8
1> COBOL compile: 0 item(s) succeeded or up-to-date, 1 failed.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========
========== Build completed at 10:52 AM and took 02.924 seconds ==========

As previously shared please review this link:
CSQL-F-010: Irrecoverable error writing STK record (microfocus.com)
The page includes this content:
CSQL-F-010: Irrecoverable error writing STK record
In a stacked environment (for example when COBSQL invokes another Integrated Preprocessor such as CP), COBSQL stores information returned from the other Integrated Preprocessor in a side file that has an extension of STK. The file has the same basename as the input file. This message is displayed if COBSQL receives a COBOL error while trying to write out a record to the STK side file. COBSQL also displays error message CSQL-E-023 (file I/O error) giving the COBOL I/O error message.

Does the file that it tries to write to exist, do you have full permissions to write to the file?