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

Glossary
Safeguard Management Programming Manual—422086-028
Glossary-7
event message
event message. In programmatic interfaces based on SPI, a special kind of SPI message
that describes an event occurring in the system or network.
extensible structure. A structure declared for the value of an extensible structured token.
See extensible structured token. Compare to fixed structure.
extensible structured token. A token consisting of a token code and a value that is an
extensible structure. Extensible structures can be extended by adding new fields at the
end in later RVUs. Such structures are typically used to indicate the attributes of an
object being operated on and to return status and statistics information in responses.
They can also be used for other purposes. The token is referenced by a token map
that describes the structure to SPI so that SPI can provide compatibility between
different versions of the structure. See also simple token, structure, structured token,
and token map.
extras. A SCREEN COBOL program unit that you can add to the ViewPoint console
application, possibly as a means of invoking a larger set of program units that you
supply. See also Linkage Section.
filter. A file containing a list of criteria against which incoming event messages can be
compared so as to pass a given message (if it met all criteria) or not pass it (if it failed
one or more criteria).
fixed structure. A structure declared for the value of a simple token that includes several
fields. Fields cannot be added to fixed structures in later RVUs. See also extensible
structure.
flush. To purge something of its contents. There is an SPI control code to flush the buffer
from the current position onward, so that tokens later in the buffer effectively cease to
be present.
forwarding distributor. An Event Management Service (EMS) distributor process that
sends selected event messages to an EMS collector on another network node. See
also compatibility distributor
, consumer distributor, and printing distributor.
generic list. The most general list construct supported by SPI. It consists of a list token that
denotes a generic list (different from the token that starts a data list or an error list),
followed by other tokens and an end-list token. Generic lists can be nested. No
subsystem for the NonStop server uses generic lists, but subsystems you write can do
so. See also data list, error list, and response record.
GETVERSION command. An information command that reports to the requester the server
version of the subsystem server and possibly additional version information about
objects defined by the subsystem. All subsystems with a programmatic command
interface based on SPI have a GETVERSION command.
header. See SPI message header.