Linking user modules

User modules can only be linked in statically and not dynamically (i.e. at runtime). Programs containing “unresolved externals” to user modules cannot be loaded in the POSIX shell.

The following can be input sources to the link editor:

• Object files generated by the compiler (“.o” files)

• Libraries created with the ar utility (“.a” files)

• LLMs that were copied from PLAM libraries into POSIX object files with the POSIX bs2cp command (see “Introductory examples”). These may be LLMs that were generated directly by a compiler in the BS2000 environment (SDF) or object modules which were written into an LLM with the link editor.

• LLMs and object modules in BS2000 PLAM libraries. The PLAM libraries must be assigned with the BLSLIBnn environment variable (see the -l BLSLIB option on "Link editor options").

The modules from the PLAM libraries may be modules generated by any BS2000 compiler with ILCS capabilities (e.g. C/C++, COBOL85, COBOL2000, ASSEMBH).
You must observe language-specific requirements with the above (parameter passing, required runtime systems, etc.).

Internal INCLUDE-MODULES directives are issued during linking with POSIX object files and RESOLVE-BY-AUTOLINK directives are issued for ar libraries and PLAM libraries.