Guardian Programmer's Guide

Table Of Contents
Glossary
Guardian Programmer’s Guide 421922-014
Glossary - 15
Kernel-Managed Swap Facility (KMSF)
fabrics in G-series release version updates (RVUs). The $ZZKRN Kernel subsystem
manager process is started and managed by the $ZPM persistence manager process.
Kernel-Managed Swap Facility (KMSF). A facility by which the operating system manages
virtual memory using swap files that it owns. Each CPU has at least one
kernel-managed swap file that provides the swap space needs of all of its processes.
key-sequenced file. A file in which each new record is stored in sequence by primary key
value, and whose primary key is either a user-defined or a system-defined value.
Records in a key-sequenced file can be updated or deleted. Contrast with entry-
sequenced file and relative file.
KMSF. See Kernel-Managed Swap Facility (KMSF).
keyword. A character sequence recognized by a command process.
labeled tape. A magnetic tape file described by standard ANSI or IBM file labels. Contrast
with unlabeled tape.
LCT. Seelocal civil time (LCT).
LDEV. See logical device.
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 eld utility and nld utility.
legacy system. An operating system that is not open but from which applications must be
ported or users transferred.
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.
library client. A program or another library that uses routines or variables from that library.
library file. See library.
linking. The operation of collecting, connecting, and relocating code and data blocks from
one or more separately compiled object files to produce a target object file.
load. (1) To transfer the HP NonStop™ operating system image or a program from disk into
a computers memory so that the operating system or program can run.
local millicode. Emulation millicode routines that are physically copied into each TNS
program code file when accelerated for TNS/E. These are a small and frequently used
subset of the full set of accelerated-mode millicode routines located in the system’s