Tandem Failure Data System (TFDS) Manual

Glossary
HP Tandem Failure Data System (TFDS) Manual—540122-003
Glossary-8
OSS
OSS. See Open System Services (OSS).
OSS environment. See Open System Services (OSS) environment.
OSS Monitor. See Open System Services (OSS) Monitor.
parallel dumping. For DMR and TMR processors, the TFDS method of reloading a halted
processor before dumping the affected NSBE.
pathname. In the Open System Services (OSS) file system and Network File System
(NFS), the string of characters that uniquely identifies a file within its file system. A
pathname can be either relative or absolute. See also ISO/IEC IS 9945-1:1990
(ANSI/IEEE Std. 1003.1-1990 or POSIX.1), Clause 2.2.2.57.
PE. see processor element.
persistence. For the Subsystem Control Facility (SCF), the capability of a generic process
to restart automatically if it was stopped abnormally. You configure this capability by
specifying a nonzero AUTORESTART value in an ADD command.
persistence count. The number of times the Persistence Manager ($ZPM) will restart a
generic process that has been terminated abnormally. A generic process with an
AUTORESTART value of 10 (the maximum) is said to have a persistence count of 10.
See also persistence.
persistence manager process. The $ZPM process that is started and managed by the
$ZCNF configuration utility process and that starts generic processes in G-series and
H-series release version updates (RVUs) and manages their persistence.
persistent configuration. A configuration that remains the same from one system load to
another.
persistent process. A process that must always be either waiting, ready, or executing.
Persistent processes are usually controlled by a monitor process that checks on the
status of persistent processes and restarts them if necessary.
processor element. A single microprocessor or microprocessor core, with its associated
memory, capable of executing a single instruction stream.
processor slice. See HP NonStop™ Blade Element (NSBE).
program. See program file.
program file. An executable object code file containing a program’s main routine plus
related routines statically linked together and combined into the same object file. Other
routines shared with other programs might be located in separately loaded libraries. A
program file can be named on a RUN command; other code files cannot. See also
object code file.