Implicit linking to the global program cache
The linker process is started when the first call of a POSIX program contained in a library for which implicit linking is activated is made. The program is loaded via the BLS BIND interface. The program core image is analysed in the Cl.6 memory prior to the start of the program. All necessary information about the loaded program (for each slice: address, length and attributes) is returned by BLS. All slices of the loaded program are copied to the global program cache and the program is then started.
There is a number of commands which are used only relatively rarely and cannot therefore be loaded automatically into the global program cache. These are, for example, daemons or commands from the mount/umount complex.
Explicit linking to the global program cache
This is different from the implicit linker process in that the super user can copy any POSIX program into the global program cache. The command call
posdbl -b path
starts the linker process. The ready-to-run core image of the program with the path name path is copied into the global program cache.
Explicit linking to user-specific program cache
USERWIDE
With the command call
pdbl -u -b path
the linker process is initiated. The ready-to-run core image of the program with the path name path is copied into the user-specific program cache.
SESSIONWIDE
The command call
pdbl -s [sid] -b path
starts the linker process. The ready-to-run core image of the program with the path name path is copied into the user-specific program cache of the session sid. If sid is not indicated, then the current session will automatically be used.
The user must have execute permission for the program indicated in path.