To facilitate conversion of applications with load modules to those with LLMs for the user, BLSSERV enables LLMs to be loaded which were stored in a PAM file with BINDER. In contrast to the LLMs stored in program libraries, these LLMs are called PAM-LLMs.
PAM-LLMs differ from the conventional LLMs in the following ways:
PAM-LLMs can only be loaded with commands, but not with program interfaces such as the BIND macro. (Exception: Slices of a PAM-LLM with user-defined slices can be loaded with the LDSLICE macro.)
The file link name for PAM-LLMs is the same as for program files: ECERDLOD.
As a PAM-LLM runs in ADVANCED execution mode, it is by default loaded in the LOCAL#DEFAULT context, not in the CTXPHASE context, which is reserved for load modules.
The name in the load call is always interpreted as a file name and not as a symbol name. Consequently no search for symbols already loaded takes place in the memory during loading.
During loading no external references are resolved and no autolink function isexecuted.
PUBLIC/PRIVATE-PAM-LLMs cannot be loaded.