TR3271 Management Programming Manual

SECTION 3
ELEMENTS OF SPI MESSAGES FOR THE SUBSYSTEM
The Subsystem Programmatic Interface (SPI) procedures facilitate
the communication between a management application and the TR3271
subsystem. These procedures allow a management application to
build commands in SPI message format to be sent through SCP
to the subsystem. These procedures also allow a management
application to decode the responses from the subsystem that have
been sent through SCP in SPI message format. However, GUARDIAN
90 procedures, not SPI procedures, are used to transport SPI-
formatted commands and responses between a management application
and SCP, and between SCP and a subsystem. For details on message
transport, refer to the Distributed Systems Management (DSM)
Programming Manual .
NOTE
SCP is responsible for the communication between SCP and
the TR3271 subsystem. Your management application needs to
be concerned only with the steps enumerated in Section 2,
"Management Programming for TR3271."
SPI procedures are also used to obtain complete event messages
from the Event Management Service (EMS) distributor process.
The EMS procedure EMSGET is used to extract tokens from event
messages, and the EMS procedure EMSTEXT is used to obtain text
versions of event messages. Like commands and responses sent
through SCP, event messages are sent and received in SPI message
format.
3-1