Link Settings

Runtime Library

Static

Click this to link the application to the static run-time system. The run-time system is linked into your executable file.

Click this if you are building a monolithic application either as a standalone executable or as a DLL that will be called by a non-COBOL program.

Shared

Click this to link the application to the shared run-time system. The run-time system is not linked into your executable files, but is loaded dynamically when your application is run.

Click this if you are building a modular application, or a DLL that will be called by a COBOL program.

Dynamic

Check this to bind the application to run-time system dynamically at run time. The application binds to any appropriate run-time system on the end-user's system when it is run. The COBOL run-time system files are automatically located on the end-user's system by looking them up in the Windows Registry.

If you don't select this, your application requires the run-time system supplied with this version of your COBOL development system to be available on the end-user's system. You need to install the run-time system files in the same directory as your application's executable file.

Bind to current RTS only

Select this to dynamically bind the application to a run-time system of the same version (or later) as your COBOL development system.

If you don't select this, the application binds to any suitable run-time system on the end-user's system.

Thread Model

Single-threaded

Click this if you want the application to be linked with the single-threaded run-time system.

Multi-threaded

Click this if you want the application to be linked with the multi-threaded run-time system.

Either

Click this if you have chosen dynamic binding for the shared run-time system and you do not care whether the application binds to the single or to the multi-threaded system.

Link Level

If you want to debug statically linked system executable files or dynamic link libraries, ensure that you have selected the Static option under Runtime Library.

Lite

Click this if you want your application to be statically linked with the lite run-time system.

The lite run-time system is a smaller version of the run-time system that includes sufficient support for many statically linked COBOL applications consisting of .obj files only. Do not use it if you need support for any of the following:

• Micro Focus library (.lbr) files
• Run-time system configuration using COBCONFIG
• Shared memory allocation
• DD_ name mapping

Base

Click this if you want your application to be statically linked with the base run-time system.

The base run-time system is the default run-time system for statically linked executable files. It provides all support needed for linking COBOL applications consisting of .obj files only. Do not use it if you need support for the following:

• Micro Focus library (.lbr) files

Full

Click this if you want your application to be statically linked with the full run-time system.

The full run-time system is a slightly larger run-time system that provides full support for all COBOL applications, including support for Micro Focus library (.lbr) files.

Linker Parameters

Link with obj's

Type the names of any .obj files you want to link with this system executable file. Alternatively, you can add them to the Project tree view under the .exe file.

Link with libs

Type the names of any library (.lib) files you want to link with this system executable file. Alternatively, you can add them to the Project tree view under the .exe file.

Additional directives

Type any additional parameters you want to pass to the Cbllink utility. For a list of possible directives, see the command-line reference in the Reference Bookshelf in help, or look up Cbllink utility in the help index.

Entry point

Type the root name of the object file that contains the first module of code to be executed in your application. The root name is the filename without the .obj extension.

Output name

Specify a name for the output application file which can be different for the different configurations.

Keep temporary files

Select this if you don't want temporary files created when linking to be deleted. Temporary files include import libraries, definition (.def) files, and .lnk files.

Include system programs

Select this if you want any run-time system support modules needed by your application to be automatically linked with it. Run-time support modules provide support for the following:

• User-defined classes in SPECIAL NAMES paragraphs
• EXTERNAL files and data
• Enhanced ACCEPT and DISPLAY syntax
• Intrinsic functions
• PC_PRINT library routines

If you don't select this, you need to link any support modules needed by adding them to your project.

If your application needs run-time support other than that listed above, you need to link in the appropriate modules by adding them to your project.

Generate map file

Select this to create a .map file when your application is rebuilt. The linker map file contains information such as a timestamp, a preferred loading address, a list of public entry points used in the linked object files, and a fixup (load offset) table.

Graphical application

Check this if your application uses a graphical user interface.

Verbose output

Select this if you want all notes and messages from the Linker to be displayed in the Output window. Messages that use the LNK prefix are from the Linker, and are explained in more detail in the Microsoft Win32 Software Development Kit.