NET/MASTER Management Services (MS) System Management Guide

Customizing the Event Detail Database
Managing Event Messages
115414 NonStop NET/MASTER MS System Management Guide 8–11
Customizing the Event
Detail Database
NonStop NET/MASTER MS provides detailed information about a selected event
message, including the probable cause of the event and the action recommended to
solve the problem. The message detail screen first displays text, including the message
number.
The event information is followed by advisory text if entries exist for that event in the
event-detail database. The advisory text is displayed under the headings “Cause,”
“Effect,” and “Recovery.” This event-detail database consists of an EMS template file
(EVENTTD) and a key-sequenced file (EVENTCX).
By customizing your advisory text, you can allow users to look up the probable causes
and recommended actions for Tandem subsystem events as they apply to your
particular system or network. For example, an advisory display for an event message
requesting the user to mount another tape could include specific information on tape
mounting procedures at your site. Similarly, you can allow a user to see advisory text
for events reported by an application that was written by someone other than Tandem,
such as a program that starts and shuts down automatic teller machines. Refer to the
NonStop NET/MASTER MS Operator’s Guide for information about scrolling through
event messages in the EVENTTD and EVENTCX files.
There are two ways to customize the event detail database: by customizing the
EVENTTD file; or by creating and installing an EVENTCX file.
Customizing the EVENTTD
File
The EMS template file, EVENTTD, is installed in the $SYSTEM.SYSTEM subvolume.
(You can use the SYSPARMS EMSEVENTTD command to change the location or name
of the file.) The file contains entries supplied by Tandem and can contain user-
supplied entries. The file also allows for multiple-page text for events.
If you want to write customized text for the EVENTTD file, you must write a DDL
dictionary for the template compiler and write EMS templates with cause, effect, and
recovery.
Note Any customized text that you create for the EVENTTD file is overwritten by special releases. If there is an
interim release, be sure to save a copy of your customized text.
The following listing shows one way to write a DDL dictionary for EVENTTD:
? source zspiddl
? source zvptddl (zvpt-tkn-cause, zvpt-tkn-effect,
? zvpt-tkn-action)
definition zpwy-val-ssid tacl ssid.
02 z-filler type character 8 value is zspi-val-tandem
02 z-owner redefines z-filler type zspi-ddl-char8.
02 z-number type zspi-ddl-int. value is zspi-ssn-zpwy
02 z-version type zspi-ddl-uint.
end