The format of the link and load module (LLM) permits optimization of loading compared with the object modules (OMs) and prelinked modules of the previous system.
The logical structure of an LLM enables the user to structure his or her application. The user can remove or replace a node when creating or modifying an LLM, or include the node of an LLM in another LLM.
An LLM that is saved in a program library can be modified. Modules can be replaced or additional modules included in the LLM.
The user can specify that all CSECTs that have the same attributes or combination of attributes are to be combined into slices by BINDER. This significantly reduces the loading time and main memory requirements when the LLM is loaded.
Symbols can be selected using wildcards, e.g. when modifying the visibility (masking/nonmasking) of symbols (MODIFY-SYMBOL-VISIBILITY).
List for symbolic debugging (LSD) information can be included in an LLM for testing and diagnostic purposes. The user can select individual object modules (OMs) or sub-LLMs in which the LSD information is to be inserted.
BINDER uses an SDF interface. The statements can be entered in dialog (interactive) mode or in batch mode. Each statement is processed immediately after input.
At any time when creating an LLM the user can request lists to be output (using SHOW-MAP) containing information about the status of the current LLM. The user can then decide whether further modules are to be included in the current LLM or whether modules are to be removed. The lists are output to SYSLST or SYSOUT. BINDER implicitly uses the SDF command SHOW-FILE for this.
In addition to this list output, further easy-to-use information functions are available to the user during a BINDER run.