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

The Standard Map $SPI
Standard and User-Defined Maps
11–12 106160 Tandem Computers Incorporated
SPI to MDO Conversion
Rules
When an event message containing SPI tokens arrives at NonStop NET/MASTER MS,
NonStop NET/MASTER MS converts the SPI tokens to a structure that Mapping
Services can understand using the map $SPI. It converts the SPI tokens using a series
of rules.
SPI to MDO Conversion Rule 1
NonStop NET/MASTER MS makes an EMSTEXT system call. The text of the message
preceded by the message number is placed in the text part of the MDO variable,
&$EMS.TEXT.
SPI to MDO Conversion Rule 2
NonStop NET/MASTER MS assumes that all SPI token names—across all Tandem
subsystems that use SPI tokens—are unique, and converts each SPI token in turn
according to the following conversion rules:
SPI to MDO Conversion Rule 2a. NonStop NET/MASTER MS converts all hyphens (-) in a
SPI token name to underscores (_) in an MDO variable name. The following table lists
some SPI token names before conversion and their corresponding MDO variable
names after conversion in a message that is read by the MSGREAD verb:
SPI Token Name
MDO Variable Name
(&$MSG.SPI.TANDEM. begins all variable names.)
ZSPI-TKN-SSID ZSPI_TKN_SSID
ZEMS-TKN-CPU ZEMS_TKN_CPU
ZEMS-TKN-CRTPID ZEMS_TKN_CRTPID
ZEMS-TKN-EMPHASIS ZEMS_TKN_EMPHASIS
ZEMS-TKN-TEXT ZEMS_TKN_TEXT
ZEMS-TKN-SUBJECT-MARK ZEMS_TKN_SUBJECT_MARK
SPI to MDO Conversion Rule 2b. NonStop NET/MASTER MS qualifies all converted SPI
tokens by the owner of the subsystem that defines the token and groups together with
all tokens owned by a specific owner in an MDO variable. The following table lists
some SPI token names before conversion and their corresponding MDO variable
names after conversion in a message that is read by the MSGREAD verb:
SPI Token Name
MDO Variable Name
(&$MSG.SPI. begins all variable names.)
TANDEM.EMS.D30 ZEMS-TKN-TEXT TANDEM.ZEMS_TKN_TEXT
USER.0.0 USER-TKN-ABC USER.USER_TKN_ABC