To build an application, you need to compile its programs and link them to a run-time system. You use a build configuration to define how to do this.
Building native COBOL applications
When building native COBOL applications the Compiler first checks the program for syntax errors. Then, it generates native machine code. Finally, the linker links the native machine code into an executable (either an .exe or a .dll).
- The check phase - the Compiler checks the program's syntax and creates files to use for testing and debugging. The check phase creates a dictionary file for use with the Debugger and, if you are building an INT/GNT project or have set the project output type to INT/GNT, it can produce an
.int file.
- The generate phase - during the generate phase, the Compiler creates native machine code from the intermediate code produced during the check phase, and produces either an industry-standard .obj file or, if you are building an INT/GNT project or have set the project output type to INT/GNT, it can produce a
Micro Focus
.gnt file.
You can execute
.int and
.gnt code directly with the run-time system.
You cannot execute the object code file. You must link it with the appropriate run-time system to create an executable file.
- The linking phase - during the link phase, the code is linked to the run-time system and creates an executable file - an
.exe,
.dll or
.so.
Building managed COBOL applications
When building JVM COBOL managed applications, the Compiler compiles your code to Java byte code (.class) which is then executed on a Java Virtual Machine (JVM).
Note: When working with local SQL applications on UNIX, ensure the RDBMS environment is set before you start Eclipse. Refer to your RDBMS vendor's documentation for details.