NET/MASTER Network Control Language (NCL) Programmer's Guide

The Standard Map $SPI
Standard and User-Defined Maps
106160 Tandem Computers Incorporated 11–11
The Standard Map
$SPI
The standard map $MSG is used by the message verbs. Event Management Service
(EMS) event messages arriving at NonStop NET/MASTER MS, from Tandem
subsystems such as Expand, Pathway, and SNAX/CDF, always contain SPI tokens.
When an event message arrives at NonStop NET/MASTER MS, NonStop
NET/MASTER MS creates two structures. It creates one structure containing the text
of the message that Mapping Services can interpret using the map $MSG, and it
creates another structure containing the NonStop NET/MASTER MS equivalent of SPI
tokens that Mapping Services can understand using the map $SPI.
Both structures are present in the same MDO variable after it is created, but NonStop
NET/MASTER MS uses the map $MSG to interpret the text part of the MDO variable
and the map $SPI to interpret the SPI part of the MDO variable.
This subsection does not present the map $SPI in a figure because it would be too
large—many Tandem subsystems use SPI tokens. Rather, this subsection presents the
general rules you can use to detect and interpret messages that contain SPI tokens and
the rules you can use to construct messages that contain SPI tokens.
Refer to the Introduction to Distributed Systems Management (DSM) and the Distributed
Systems Management (DSM) Programming Manual manuals for initial information on
SPI tokens. Refer to the manuals that describe individual subsystems for detailed
information on the SPI tokens used by each subsystem.
Note Some NonStop NET/MASTER MS messages are EMS events that contain SPI tokens. These messages
are listed in the NonStop NET/MASTER Messages Manual.