NetBatch Management Programming Manual
Glossary
NetBatch Management Programming Manual—522462-003
Glossary-15
SPI standard definitions
SPI standard definitions. Declarations available for use with SPI procedures. There also
are subsystem-specific declarations for each subsystem, and some declarations that
apply to multiple subsystems. An application using SPI needs the SPI standard
definitions and the subsystem definitions for all subsystems with which it
communicates. Names of SPI standard definitions start with ZSPI. See also definition;
definition files; EMS standard definitions; subsystem definitions.
structure. A data item with multiple fields, possibly of different types. This type of data item
corresponds to a DEF in the DDL language, to a STRUCT in the TAL and TACL
languages, and to a RECORD in the COBOL language.
structured token. A token whose value is a structure. Some structured tokens are simple
tokens with fixed structuresfor example, the error token, ZSPI-TKN-ERROR. Other
structured tokens are extensible structured tokens. See structure; simple token;
extensible structured token.
subject. In event management, a device, process, or other named entity about which a
given event message is concerned.
Subsystem Programmatic Interface (SPI). See SPI.
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 management process.
subsystem definitions. The set of declarations available for use with a particular
subsystem that supports a token-oriented programmatic interface. See also definition
files; EMS standard definitions; SPI standard definitions.
subsystem ID. A data structure that uniquely identifies a subsystem (including whether it is
a NonStop subsystem 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 in 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.