Before your program can be run or debugged, it should be in a type that have the right to be executed. The Compiler can produce the following species of files:

Executable code You produce executable code by compiling and also linking in one step.

An executable record has a filename expansion of .exe (Windows) or no filename expansion (UNIX).

To produce executable code, you require either a COBOL project or a COBOL far project. Choose Project > nature > Micro emphasis > build Configuration and also create or modify a configuration, picking a Target varieties option of every Executable records or solitary Executable File.

Object code object code documents are produced when you develop your project . The object code record is not executable. It requires linking through the run-time device to develop an executable file.

By default, object code documents have the extension .obj (Windows) or .o (UNIX).

Object code documents must be connected to produce .exe or .dll records (Windows) or executable, callable common object or common library documents (UNIX).

Java bytecode Java bytecode have the right to be executed on a Java Virtual device (JVM).

You create a JVM COBOL job in the principle in a similar means as you create any COBOL project and also many of the configuration options are common to both. Select document > brand-new > COBOL JVM Project.

A Java bytecode record has a filename expansion of .class.

Intermediate password

You are watching: The extension name of a java bytecode file is

Restriction: the is not possible to build JVM projects to .int files.
intermediate code files are typically for testing and debugging. The Compiler creates the intermediary code paper during its very first phase, once it checks the routine syntax. The Compiler additionally creates a dictionary file, which is supplied by the debugger. Intermediary code documents compile quickly.

Intermediate code files have the extension .int.

.int papers are dynamically loadable, and also don\"t should be linked into a mechanism executable. You deserve to ship them to your customers as executable files, but we recommend the you usage .exe files and also .dll records for this.

To compile to intermediate code files, collection the adhering to properties:
Tip: you can inspect Override job Settings in the develop configuration properties and specify to produce a collection of one of two people .int or .gnt files for a particular build configuration. To produce a mixture of .int and also .gnt files from one develop configuration, modify the individual record properties - right-click on individual files and also check Override job Settings. Then, either inspect or clear Compile to .gnt come compile to .int or .gnt, respectively.
generated code
Restriction: girlfriend cannot construct JVM jobs as .gnt files.
The Compiler creates the generated code, on request, throughout its 2nd phase. Generated code is slow to compile 보다 intermediate code but the resulting password runs faster.

Use created code records for testing and debugging. As created code runs much faster than intermediary code, it have the right to be valuable in debugging for huge programs, or for debugging programs where the distance between breakpoints is large, for example.

Generated code files have the extension .gnt.

.gnt records are dynamically loadable, and don\"t must be attached into a mechanism executable. You can ship them to your individuals as executable files, however we recommend the you usage .exe files and .dll papers for this.

To compile created code files set the adhering to properties:
Dynamic link Libraries (Windows) or Callable mutual objects (UNIX) Dynamic connect Libraries (Windows) or Callable shared objects (UNIX) are dynamically loaded at run time as soon as required, the is, when referenced as a key entry suggest (for example, by run (Windows) or cobrun (UNIX)) or through the COBOL speak to syntax. Once all the entry points in a Dynamic attach Library (Windows) or a callable shared object (UNIX) have actually been canceled then the paper is unloaded, releasing any memory used.

This actions is comparable to .int and .gnt code but is various to attached shared libraries and system executables, i beg your pardon are constantly loaded at procedure start-up, even if it is they are supplied or not. Further, the code and memory supplied by shared libraries and system executables are just unloaded as soon as the process terminates.

A Dynamic connect Library (Windows) or a callable shared object (UNIX) have the right to contain more than one COBOL program and also can additionally contain various other language programs, such together C and also C++. Dynamic attach Libraries (Windows) or callable mutual objects (UNIX) can likewise be attached with third party object records or shared libraries. This actions is similar to device executables and shared libraries but differs native .int and also .gnt files, whereby each record corresponds to a single COBOL program.

A Dynamic attach Library (Windows) has actually a filename expansion of .dll.

A callable shared object document (UNIX) has actually a filename extension of .so.

To create Dynamic attach Libraries (Windows) or callable shared objects (UNIX), you require either a COBOL job or a COBOL far project. Select Project > properties > Micro focus > develop Configuration and create or edit a configuration, choosing a Target species option that All indigenous Library documents or single Native Library File.

Bundling intermediary or created code files

You deserve to bundle .int files and .gnt papers in Micro emphasis library files. The benefits of this are:

A library paper has the document extension .lbr.

For example, offered the complying with programs in ours application:
Figure 1. Programs in application

ProgC and also ProgD might be compiled as generated code files, and also then placed in a library file, mylib.lbr. Once ProgA calls ProgC, mylib.lbr would be loaded right into memory, likewise loading progc.gnt and also progd.gnt. Friend would need to ship proga.gnt, progb.gnt, and mylib.lbr, and also a trigger program.

To parcel the .int and also .gnt documents into one .lbr file, collection the complying with properties:

following time you construct your project, the project builds .int or .gnt documents as normal, and likewise compiles lock all right into an .lbr file.

See more: If You Want To Play In Texas (You Gotta Have A Fiddle In The Band)

Restriction: You can not compile .lbr records for JVM or mainframe projects.