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

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

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

To create executable code, you need either a COBOL job or a COBOL far project. Select Project > properties > Micro focus > develop Configuration and also create or edit a configuration, selecting a Target varieties option of all Executable documents or single Executable File.

Object password thing code files are produced when you construct your task . The object code record is no executable. It requires linking with the run-time mechanism to create an executable file.

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

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

Java bytecode Java bytecode can be executed on a Java Virtual device (JVM).

You create a JVM COBOL task in the ide in a similar means as you create any type of COBOL project and also many of the configuration options are common to both. Select record > new > COBOL JVM Project.

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

Intermediate password


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

Restriction: it is not possible to construct JVM tasks to .int files.
intermediary code papers are typically for testing and debugging. The Compiler create the intermediate code file during its an initial phase, once it check the regime syntax. The Compiler likewise creates a thesaurus file, i m sorry is used by the debugger. Intermediary code files compile quickly.

Intermediate code records have the expansion .int.

.int records are dynamically loadable, and don"t have to be linked into a system executable. You deserve to ship them come your individuals as executable files, however we recommend the you use .exe files and also .dll files for this.


To compile come intermediate code files, set the following properties:
Tip: friend can check Override project Settings in the build configuration properties and specify to develop a collection of either .int or .gnt files for a certain build configuration. To develop a mixture of .int and also .gnt files from one construct configuration, modify the individual file properties - right-click on individual files and also check Override task Settings. Then, either examine or clean Compile come .gnt come compile to .int or .gnt, respectively.
produced code
Restriction: girlfriend cannot construct JVM tasks as .gnt files.
The Compiler creates the created code, top top request, during its 2nd phase. Produced code is slower to compile 보다 intermediate code yet the resulting code runs faster.

Use produced code files for testing and debugging. As produced code runs faster than intermediary code, it can be useful in debugging for large programs, or for debugging programs where the distance in between breakpoints is large, because that example.

Generated code papers have the extension .gnt.

.gnt papers are dynamically loadable, and also don"t have to be attached into a system executable. You can ship them come your customers as executable files, but we recommend the you use .exe files and .dll papers for this.


To compile produced code files set the adhering to properties:
Dynamic link Libraries (Windows) or Callable shared objects (UNIX) Dynamic link Libraries (Windows) or Callable mutual objects (UNIX) are dynamically invited at operation time once required, that is, as soon as referenced as a main entry allude (for example, by run (Windows) or cobrun (UNIX)) or by the COBOL speak to syntax. As soon as all the entry points in a Dynamic connect Library (Windows) or a callable shared object (UNIX) have actually been canceled then the document is unloaded, releasing any memory used.

This behavior is similar to .int and .gnt code however is different to attached shared libraries and also system executables, i beg your pardon are always loaded at process start-up, even if it is they are offered or not. Further, the code and also memory supplied by common libraries and system executables are only unloaded once the procedure terminates.

A Dynamic attach Library (Windows) or a callable shared object (UNIX) have the right to contain much more than one COBOL program and also can also contain various other language programs, such together C and also C++. Dynamic link Libraries (Windows) or callable common objects (UNIX) can additionally be linked with 3rd party object records or mutual libraries. This habits is comparable to system executables and also shared libraries but differs indigenous .int and also .gnt files, whereby each document corresponds come a solitary COBOL program.

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

A callable shared object file (UNIX) has a filename expansion of .so.

To create Dynamic attach Libraries (Windows) or callable common objects (UNIX), you need either a COBOL job or a COBOL far project. Select Project > nature > Micro emphasis > develop Configuration and also create or modify a configuration, choosing a Target varieties option of All native Library papers or solitary Native Library File.


Bundling intermediary or generated code files

You have the right to bundle .int files and also .gnt documents in Micro emphasis library files. The benefits of this are:

A library document has the paper extension .lbr.


For example, given the adhering to programs in our application:
Figure 1. Programs in application
*

ProgC and also ProgD might be compiled as created code files, and also then placed in a library file, mylib.lbr. Once ProgA call ProgC, mylib.lbr would certainly be loaded right into memory, likewise loading progc.gnt and also progd.gnt. You would must ship proga.gnt, progb.gnt, and also mylib.lbr, as well as a cause program.

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


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


See more: Question: How Many Oz In A 1.75 Liter Bottle Sizes, Allens Retail Liquor Store

Restriction: You cannot compile .lbr documents for JVM or mainframe projects.