Compiling COBOL code

Before you can run a program, you have to compile the source code.

By default, your project is built automatically, every time you save the project. This ensures that whenever a resource changes, an incremental build starts and all resources modified since the last build are rebuilt. You can force a manual build too, by cleaning the project.

You can configure the compilation using the following techniques:

The Compiler records errors with severity levels ranging from information messages to fatal errors which stop the Compiler working.

When you compile, the Compiler can produce executable code directly or object code. Object code is not executable, and has to be linked to the run-time system to create an executable file. If your project is set to build to .int and .gnt, by default the Compiler produces .int code during its syntax checking phase, and then it can produce .gnt code during the generating phase. You can modify this behavior from the project or the file properties.

Compiling in the IDE

By default, Eclipse is configured to build projects automatically whenever you save a file or change a file's or the project's properties. You can turn off automatic building from Window > Preferences > General > Workspace and unchecking Build automatically.

If automatic builds are not disabled, you can build a project at any time by selecting the project in the Team Developer Tree view and clicking Project and then Build Project to build the currently selected project, Build All to build all projects in the current workspace, or Build Working Set to build a subset of the projects in the workspace.

Important: For applications that use a RDBMS, you might need to set some additional directives in your build configuration.

Compiling from the command line

Using the command line, you can compile without linking using the cobol command (Windows), or compile and link your program in one step using the cbllink utility (Windows) or cob (UNIX) command.

You can either specify all the information required on the command line, or use the Compiler prompts.

Errors reported during a build

Eclipse reports any errors found in your sources in the Problems and in the Console views.

A limit of 10,000 build errors is set for this product. If this number is reached, Eclipse aborts the build to prevent the build from taking up too much memory on the machine. Some of the source files might not compiled. To compile your application, you need to fix the issues that are reported and then rebuild the entire project.