Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Dynamic linking with DBL

&pagelevel(4)&pagelevel

With the Dynamic Binder Loader you can perform the following operations in one go:

  1. Temporarily link modules to form a loadable unit

  2. Store the loadable unit in working memory and start it

The generated load unit is deleted at the end of program execution.

If the specified start module is a prelinked module, it must be linked with open external references to CRTE, i.e. without a RESOLVE-BY-AUTOLINK statement to CRTE.
With BINDER, incomplete linkage is possible without precautionary measures.

If the C and/or COBOL runtime system is loaded in the high address space of class 4 memory (see also section “Shareability of CRTE”) you must specify PROG-MODE=ANY in the START-PROGRAM command.

The CRTE libraries for the partial bind linkage method are only allowed for linking. However, you may not use these libraries as the BSLIB for loading programs containing unresolved external references in the event of dynamic binding with DBL, especially not when the CRTE subsystem is preloaded. In this case you may only use the SYSLNK.CRTE library as a BLSLIB.

Employed subsystems

The dynamic linkage technique with DBL described here requires the following subsystems:

  • CRTEC (for C)

  • CRTECOB (for COBOL)