NET/MASTER Management Services (MS) System Management Guide

Mapping UserDefined Tokens to MDOs
Maintaining the Map File
115414 NonStop NET/MASTER MS System Management Guide 12–7
Mapping User-Defined
Tokens to MDOs
The tokens for Tandem subsystems are already mapped to mapped data objects
(MDOs). If you have your own subsystem, however, you can use the MDMAINT
program to map the user-defined tokens in the subsystem to MDOs.
The syntax of the TACL RUN command used to invoke the MDMAINT program to
map user-defined tokens to MDOs is the following:
RUN MDMAINT / run-options / map-file owner-file
run-options
specifies TACL RUN command options, separated by commas (,). Refer to the
TACL Reference Manual for more information.
map-file
specifies the name of the map file, as described by the PARAM MDSMAPFILE
command. See Section 3, “Configuring NonStop NET/MASTER MS,” for a
discussion of the MDSMAPFILE operand. Refer to the NonStop NET/MASTER MS
Command Reference Manual for more information on the PARAM command.
owner-file
specifies a SPI-to-MDO conversion edit file created in Step 5, described in the
following steps.
Note You cannot name the conversion file ADD or DEL.
To map user-defined tokens to MDOs, follow these steps:
1. Define your subsystem and its tokens in DDL. You must use the SSID clause in
each token you define. Build your dictionary.
For instructions on using the SSID clause, refer to the DSM Template Services
Manual. For instructions on building your dictionary, refer to the Data Definition
Language (DDL) Reference Manual.
2. Create a template source file describing at least one message, and include on the
SSNAME line a three-character subsystem name:
SSNAME: "SUBSYSA", "SSA"
where SUBSYSA is the full subsystem name and SSA is the three-character
subsystem name. NonStop NET/MASTER MS uses the three-character subsystem
name and the event number to build the message ID for an event (for example,
SSA0001).