SPI Common Extensions Manual

Glossary
SPI Common Extensions Manual427508-001
Glossary-12
SPI procedures
SPI procedures. The procedures used to build and decode SPI messages. These
procedures are SSINIT, SSNULL, SSPUT, SSPUTTKN, SSGET, SSGETTKN,
SSMOVE, and SSMOVETKN. Corresponding TACL built-ins are also available.
SPI standard definitions. The set of declarations available for use with the SPI procedures
regardless of the subsystem. A set of subsystem-specific declarations is available for
each subsystem, and some sets of declarations apply to multiple subsystems. An
application using SPI needs the SPI standard definitions and also the subsystem
definitions for all subsystems with which it communicates. See also definition files and
subsystem definitions.
statistics token. A response token providing performance data about an object.
status token. A response token whose value indicates the status (current state) of an
object.
structure. A data item with multiple fields, possibly of different types. This kind of data item
corresponds to a DEF in DDL, to a STRUCT in TAL and TACL, and to a RECORD in
COBOL.
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 structure, simple token, and
extensible structured token.
subject. In event management, a device, process, or other named entity about which a
given event message is concerned.
subordinate names option. In extended SPI subsystems, the designation that the object
name given in the command stands not just for itself but for the names of all objects at
the next-lower level in a hierarchy. (The given object name can stand both for itself and
for the subordinate objects, or it can stand only for the subordinate objects, depending
on the value of the SUB token.) When this option is present in a command, the
subordinate names are implied even though they are not given explicitly.
subsystem. A program or set of processes that manages a cohesive set of objects. Each
subsystem has a manager process (in some cases, this process is the entire
subsystem) through which applications can request services by issuing commands
defined by that subsystem. See manager process.
Subsystem Control Facility (SCF). The interactive interface for configuring, controlling,
and collecting information from Compaq subsystems. SCF provides many of the same
functions as CMI, CUP, and PUP, plus more functions not available in CMI, CUP, or
PUP.