Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

DBL and BINDER

  • One of the main features of the actual Binder-Loader-Starter (BLS) system is the large degree of harmonization between BINDER and DBL. This means:

    • Pseudo-calls, such as the TABLE macro previously used as a link between the static loader ELDE and the dynamic linking loader DLL, are superseded as a result of using LLMs. All LLM information that has been specified by BINDER when creating the LLM can be evaluated immediately by the new DBL.

    • External references are resolved by BINDER and DBL according to the same rules.

  • Functions which the DLL could apply only to dynamically loaded object modules (e.g. modify options, information output, unloading) can be applied to the entire load unit by DBL.

  • Both DBL and BINDER can process symbol names up to 32 characters long. These symbol names can be generated by BINDER by renaming the original symbol names in an LLM (RENAME-SYMBOLS).

  • BINDER can generate LLMs with slices formed according to the PUBLIC or PRIVATE attribute of the CSECTs. DBL loads the PRIVATE slice into the user’s class 6 memory. The user declares the PUBLIC slice as shareable by loading it into a common memory pool with the aid of the DBL macro ASHARE.