Distributed Name Service (DNS) Management Programming Manual

Glossary
Glossary–16 46958 Tandem Computers Incorporated
Starting state. The state in which a piece of software or a device is being prepared for
operation. In the case of DNS, the operational state in which named DNS processes
are being created.
Startup message. A specific message sent by the creator to a newly created process.
Startup sequence. The steps required to initiate a process.
Statistics token. A response token providing performance data about an object. A
statistics token is a kind of information token.
Status token. A response token whose value indicates the status (current state) of an
object. A status token is a kind of information token.
Stopped state. The state in which a process or a device is absent or unavailable; in the
case of DNS, the operational state in which none of the named DNS processes are
currently active.
Stopping state. The state in which a process or device is being shut down in an orderly
way; in the case of DNS, the state in which an orderly shutdown of DNS is in progress.
Structure. A data item with multiple fields, possibly of different types. This kind of
data item corresponds to DEF in DDL, to STRUCT in TAL and TACL, and to RECORD
in COBOL85.
Structured token. A token whose value is a structure. Some structured tokens are
simple tokens with fixed structures—for example, the error token ZSPI-TKN-ERROR.
Other structured tokens are extensible structured tokens. See also Structure, Simple
token, and Extensible structured token.
Subsystem. A program or set of processes that manages a cohesive set of objects. Each
subsystem has a process (in some cases, this process is the entire subsystem) through
which applications can request services by issuing commands defined by that
subsystem. See also Management process.
Subsystem Control Facility. The interactive interface for configuring, controlling, and
collecting information from Tandem data communications subsystems. The
Subsystem Control Facility provides many of the same functions as CMI, CUP, and
PUP, but provides additional functions as well.
Subsystem Control Point. The management process for all Tandem data communications
subsystems. There can be several instances of this process. Applications using SPI
send all commands for data communications subsystems to an instance of this process,
which in turn sends them on to the manager processes of the target subsystems. The
Subsystem Control Point also processes a few commands itself. It provides security
features, version compatibility, support for tracing, and support for applications
implemented as NonStop process pairs. See manager process.
Subsystem-control token. A parameter token that influences how a subsystem performs
a command. For instance, in the START PATHWAY programmatic command, the
parameter ZPWY-TKN-DEF-PATHWAY is a subsystem-control token, since it
determines whether a cold start or a cool start will be performed. Likewise, the
standard SPI token ZSPI-TKN-ALLOW-TYPE, supported by some subsystems, is a