dfcn and what all goes on when compiling

The Asset Suite application runs with MicroFocus COBOL on non IBM machines. ProCOBOL (Oracle’s COBOL) is in use when a .csm or .ccp program is compiled. The dfcn script in the tools directory runs a custom Ventyx pre compiler that expands certain data type definitions, example: PIC I, and changes and EXEC SQL statements from DB2 style SQL to Oracle SQL (and maybe other stuff that I can’t remember) if Asset Suite is defined to be using the Oracle database. Then the Oracle Pro COBOL compiler will compile the Oracle style SQL and finally the MicroFocus COBOL compiler compiles everything else.

If Asset Suite is using the Oracle database it is possible to write straight Oracle style SQL and use Oracle specific SQL capabilities. The EXEC SQL is marked (I forget exactly how) so that the Ventyx precompiler leaves it alone.

Note that the Ventyx developers use vanilla DB2 style SQL that can be translated to Oracle style SQL. It's the reason why sometimes you'll wonder why the developer didn't use a fancier SQL statement to get the job done.

Changing dfcn to get COBOL compile listing ›
By webmaster | | read more | 3 comments

Reply