NonStop System Glossary

LC-SC cable
A multimode fiber cable that connects a modular ServerNet expansion board (MSEB) to an I/O
adapter module (IOAM) or a Fibre Channel switch (FC switch).
ld utility
A utility that collects, links, and modifies code and data blocks from one or more
position-independent code (PIC) object files to produce a target TNS/R native object file. See also
nld utility and eld utility.
ldev
See logical device number (ldev).
LDEV
Logical device. The HP term for a disk in the Enterprise Storage System (ESS).
LED
See light-emitting diode (LED).
legacy system
An operating system that is not open but from which applications must be ported or users transferred.
libList
The list of libraries to be loaded along with a loadfile. When linking the loadfile, the linker constructs
the libList from the names of libraries specified in the linker’s command stream. It stores the libList
within the loadfile.
library
A generic term for a collection of routines useful in many programs. An object code library can
take the form of a linkfile to be physically included into client programs, it can be an OSS archive
file containing several linkable modules, it can be a loadfile, or it can be a system-managed
collection of preloaded routines. Source-code libraries fall outside the scope of this glossary. See
also dynamic-link library (DLL) and shared run-time library (SRL).
library client
A program or another library that uses routines or variables from that library.
library file
See library.
library import characterization (LIC)
A list of the export digests and relocation offsets of all the libraries used to resolve symbols in a
loadfile. It allows the loader and operating system to determine when a file is being loaded in an
environment equivalent to that found by the linker or to a previous load. (See fastLoad.) A LIC is
generated and stored in the loadfile by the linker when a file is preset; it can be used in a subsequent
load step to determine whether the loadfile’s existing bindings can be reused. The operating system
can also retain the bindings as modified when a loadfile is loaded and associate a LIC with those
cached bindings, so that they can be reused when the same file is again loaded in an equivalent
environment. (See cached bindings.)
L 115