NonStop S-Series Planning and Configuration Guide (G06.25+)

Table Of Contents
Glossary
HP NonStop S-Series Planning and Configuration Guide523303-015
Glossary-68
null object type
null object type. A placeholder object type for the Subsystem Control Facility (SCF)
NAMES and VERSION commands, which do not require explicit specification of a
particular object type.
null string. In C and C++ programs, a character string that begins with a null character.
This term is synonymous with
empty string.
OBEY file. See command file.
object. One or more of the devices, lines, processes, and files in a subsystem; any entity
subject to independent reference or control by one or more subsystems. In the
Subsystem Control Facility (SCF), each object has an object type
and an object name.
object-code library. Synonym for library.
object code file. A file containing compiled machine instructions for one or more routines.
This file can be an executable loadfile for a program or library or a not-yet-executable
linkfile for some program module. On other systems, an object code file is also known
as a
binary or as an executable.
object name. A unique name for a Subsystem Control Facility (SCF) object within a
subsystem.
object-name template. A name that stands for more than one Subsystem Control Facility
(SCF) object. Such a name includes one or more wild-card characters, such as *
(asterisk) and ? (question mark). See also wild-card character
.
object type. The category of Subsystem Control Facility (SCF) objects to which a specific
SCF object belongs. For example, a specific disk has the object type DISK, and a
specific terminal can have the object type SU. Each subsystem has a set of object
types for the objects it manages.
obsolescent. An indication that a feature or facility exists for compatibility with older
versions or drafts of a standard. Obsolescent features or facilities should not be used
because they might be removed from future versions of a standard and therefore might
not be portable.
offline. (1) Used to describe tasks that are performed outside of the control of an application
or computer system. (2) Used to describe tasks that require system resources to be
shut down. Contrast with online
.
offline change. Any change that requires system resources to be shut down. Offline
changes are usually performed during a planned outage. Contrast with online change
.
offline configuration. Configuration performed offline by SYSGENR. If necessary, you edit
the CONFTEXT configuration file to create a new configuration and then run the