ViewPoint Manual
Glossary
ViewPoint Manual—426801-001
Glossary-7
Status Configuration screen
of status configuration files; operators specify on the Profile screen which file 
ViewPoint uses to display status at their terminals.
Status Configuration screen. The ViewPoint screen on which the operator can specify 
configuration information to control the display of status items on the Network Status 
Summary screen.
status item. A measurable condition in a system or network that is displayed on one line of a 
Network Status Summary display screen. Each such item is separately chosen and 
configured for display by use of the Status Item Configuration screen.
Status Item Configuration screen. The ViewPoint screen on which individual operators can 
modify existing items or add new items to a status configuration file for display on their 
Network Status Summary screen.
status server. A server that collects data for the ViewPoint Network Status Summary screen. 
Compaq provides a default status server; the user can write and configure additional 
status servers to augment or replace the functions 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. A status server can also be called a status collection server.
subject. In event management, a device, process, or other named entity about which a given 
event message is concerned.
subsystem. A program or set of processes that manages a cohesive set of objects. Each 
subsystem has a management process through which applications can request services 
by issuing commands defined by that subsystem. See management process.
subsystem ID. A data structure that uniquely identifies a subsystem (including whether it is a 
Tandem subsystem or a user subsystem). 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 Programmatic Interface. A common, message-based interface that can be used 
to build and decode messages used 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, 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.
token. In SPI, a distinguishable unit in an SPI message. Programs place tokens in an SPI 
buffer using the SSPUT procedure (except for header tokens, which are a special case) 










