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

Glossary
Safeguard Management Programming Manual—422086-028
Glossary-16
status server, status collection server
status server, status collection server. A server that gathers data. HP provides a default
status server. You can write and configure additional status servers to augment or
replace the functionality of the default status server. Typically, a status server issues
programmatic commands to subsystems to find out how many or how much of some
resource is available—for example, how many network nodes are available or how
many terminals are up. A status server is defined to Pathway as a server class.
status token. A response token whose value indicates the status (current state) of an
object. A status token is a kind of information token.
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 data communications subsystems for NonStop servers, 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 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 Control Facility. The new interactive interface for configuring, controlling, and
collecting information from data communications subsystems for the NonStop server.
The Subsystem Control Facility provides many of the same functions as CMI, CUP,
and PUP, plus additional functions not available in CMI, CUP, or PUP.
Subsystem Control Point. The management process for all data communications
subsystems for the NonStop server. 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 process pairs. See manager process.