Safeguard Management Programming Manual (G06.29+, H06.08+, J06.03+)

Glossary
Safeguard Management Programming Manual—422086-028
Glossary-17
subsystem-control token
subsystem-control token. A parameter token that influences how a subsystem performs a
command. For instance, the standard SPI token ZSPI-TKN-ALLOW-TYPE, supported
by some subsystems, is a subsystem-control token. It determines under what
conditions the subsystems continue command processing on the next object in a
sequence if errors or warnings occur. See also response-control token.
subsystem definitions. The set of declarations available for use with a particular
subsystem that supports a token-oriented programmatic interface. See also definition
files, data communications standard definitions, EMS standard definitions, and SPI
standard definitions.
subsystem ID. A data structure that uniquely identifies a subsystem (including whether it is
a subsystem provided by HP or a subsystem you write). It consists of the name of the
owner of the subsystem (the company that provides it), a subsystem number that
denotes the subsystem within the scope of its owner, and a subsystem version
number. The subsystem ID is an argument to most of the SPI procedures.
subsystem number. An integer that identifies a subsystem within the context of its owner.
The subsystem owner, the subsystem number, and the subsystem version number
make up the subsystem ID that uniquely identifies a subsystem.
subsystem owner. A value identifying the company that supplies a particular subsystem. It
consists of a name of up to eight characters, blank-filled on the right. The owner for all
subsystems supplied by HP is “TANDEM”. The subsystem owner, the subsystem
number, and the subsystem version number make up the subsystem ID that uniquely
identifies the subsystem.
Subsystem Programmatic Interface. A set of procedures and associated definition files
used to define common message-based interfaces for communication between
requesters and servers—for instance, in a management application. It includes
procedures to build and decode specially formatted messages (as described under SPI
message); definition files in TAL, C, COBOL, and TACL for inclusion in programs,
macros, and routines using the interface procedures; and definition files in DDL for
programmers writing their own subsystems.
subsystem version number. A 16-bit integer representing the software release version of
a subsystem. The subsystem version number is a field of the subsystem ID. If its value
is null (zero), the subsystem ID refers to any and all versions of the subsystem. See
version number.
summary state. In data communications subsystems, one of the generally defined possible
conditions of an object with respect to the management of that object. A summary state
differs from a state in two ways. First, a summary state pertains to the management of
an object, whereas a state can convey other kinds of information about the object.
Second, the set of summary states are a common list defined the same way for all data
communications subsystems, whereas the set of possible states differs from
subsystem to subsystem. The token-oriented programmatic interfaces to data
communications subsystems for NonStop servers refer to summary states rather than