Note: The following information applies to native code only.
When you link a program
, you link it to any run-time support modules that it uses, and to the run-time system that it needs.
There are two ways to link to the shared run-time system: by importing the run-time system, or by binding to the run-time
The way you link depends on the type of application, as follows:
- Application for selling on to an end user
- such as those written by Independent Software Vendors (ISVs). This type of application is likely to be the sole COBOL application
that the user runs, and so it does not share the run-time system and support files with other applications. If there are other
applications, they each use their own versions of the run-time files without disruption. With this model, you create an application
that imports the run-time system and support files.
To build this type of application, you build a modular application, and link it with the run-time system. You do not enable
dynamic binding so that the run-time files are imported into the application.
- Application for corporate use
- where multiple COBOL applications are running, and need to share the run-time system and support files both on disk and in
memory. With this model, you create an application that is dynamically bound to the run-time system and support files.
To build this type of application, you build a modular application, and dynamically bind it to the run-time system. To do
this, you link the top-level COBOL executable to the run-time system and enable dynamic binding.