Hi Jan,

I am not a DB2 expert but I thought that DB2 BIND files only contained the program's actual executable SQL statements. The INCLUDE statements are not SQL statements but instead are precompiler directives that tell the precompiler to copy the specified source files into the program before precompiling it.

Can you please provide some more detail as to what exact problem you are trying to solve?

Thanks

I am not a DB2 expert neither...

We are looking into replacing an older cobol compiler with MF Visual Cobol. We have a program with the listed EXEC SQL commands and in the old BND file we see that the copybooks associated with the EXEC SQL command are somehow coded/present in the BND file. This old code is working as expected, and a SELECT statement is executed when we invoke the old code (it is deployed as a DLL).

When we compile the same source code with MF VC this compiled code now is complaining that it does not recognize the SELECT statement, it does not even write the first DISPLAY text to a log file (this is the first statement in the Procedure Division ( DISPLAY 'ENTERING NFO992JN MICRO FOCUS'). Comparing the BND files it shows that the "PROF TABLE" that is defined in one of the INCLUDE statement is not present in the BND file. Some of the BND files for other programs are also a lot smaller in size when comparing old and new complier (old 43k vs 11k new, old 955k vs 209k new). Although I realize that technology has changed in between the 1990s compiler and the 2020s MFVC compiler, since the new compiled code is not working, the differences in the generated BND files seems to be the first culprit.