OVNM 5.3 - Operations Agent for NonStop Event Management Guide for UNIX

HP NonStop Event Management System 25
2-2-8 Definition Files
Like all subsystems that support SPI interfaces, EMS has its own DDL (Data Definition Language) file that defines
the tokens, values, and data types used in event messages and in command and response messages relating to
EMS. The DDL file is called ZEMSDDL, and its language-specific derivative files are called ZEMSTAL, ZEMSTACL,
ZEMSCOB, and ZEMSC.
These files are of particular importance to EMS because they include definitions for some widely used tokens. For
example, all subsystems that report event messages use the token ZEMS-TKN-EVENTNUMBER, and all programs
that need to extract the event number from any event message also use the ZEMS-TKN-EVENTNUMBER token.
Thus, the EMS definition files pertain to many subsystems besides EMS.
2-2-9 EMS Object Programs
HP provides two object programs for starting EMS components:
• EMSACOLL (EMS Alternate Collector) starts an alternate collector by invoking the TACL RUN command.
Several command parameters are available to customize an alternate collector, including:
• SUPPRESS, which enables burst detection and suppression (BDS)
• FILTER, which identifies the compiled filters, filter tables, and up to one burst filter that can be added to
the collector to implement pre-log filtration
• EMSDIST (EMS Distributor) is the object program for starting printing distributors, forwarding distributors, or
consumer distributors. Like EMSACOLL, the EMSDIST program provides a number of command parameters,
including the FILTER parameter.
2-2-10 EMS Utility Programs
HP NonStop provides three utility programs as part of EMS that provide an interactive means for controlling and
inquiring about collectors and distributors:
• EMSCCTRL (EMS Collector Control) lets you change the values of options controlling the primary collector
($0), alternate collectors, and the compatibility distributor ($Z0). Among other things, these options control
how a collector maintains its log files.
• EMSCINFO (EMS Collector Information) displays the current settings of the primary and alternate collector
options, information about the status of the compatibility distributor, and statistics describing file operations
and occurrences of event messages.
• EMSDINFO (EMS Distributor Information) displays the current settings of the distributor options, the status of
event message sources and destinations, and statistics about filter operations and errors.
2-2-11 EMS Procedures
Several EMS-related procedures are available as part of the procedures library:
• Retrieve information from event messages
• Create event messages
Several procedures build event messages:
• EMSINIT initializes an event-message buffer, creating the correct header format for event messages and
inserting standard information it derives from parameters and from other sources.
• EMSADDTOKENS and EMSADDSUBJECT put additional tokens and event message subjects in the buffer.
Subsystems that report events use these procedures to create their event messages.
HP NonStop Event Management System