HP TACL Programming Manual page 160

Using Programmatic Interfaces
Overview of SPI and EMS
7–2
request for action.) EMS allows you to monitor the status of system and
application components. EMS messages are a type of SPI message; to
communicate with EMS, you use SPI and EMS procedures.
The following diagram shows a sample flow of EMS messages from subsystems to
management applications. An application can also retrieve messages without
involvement of distributor processes.
Operations Environment
Management
Applications
Tokenized Messages
To transport messages between management applications and subsystems, you place
tokens into a buffer. Each token consists of a token type and a token number—known
collectively as a token code—and a token value. For example, a buffer that contains a
Pathway PATHCOM START TCP command would contain the following tokens:
Token code ZSPI-TKN-COMMAND, which signifies an SPI command, with a
token value of ZPWY-CMD-START, indicating a request for a Pathway START
command.
Token code ZSPI-TKN-OBJECT-TYPE, which signifies an object type, with a token
value of ZPWY-OBJ-TCP.
Token code ZPWY-MAP-SEL-TCP, which signifies information about a TCP, with
a token value of ZPWY-DDL-SEL-TCP. The program would assign the TCP name
to the ZTCP field in the ZPWY-DDL-SEL-TCP structure.
107365 Tandem Computers Incorporated
Tokenized
Messages
EMS
EMS
Distributors
Filter
Event
Logs
Subsystem Environment
Objects
Subsystems
or
Applications
Tokenized Messages
EMS
Collectors
323