NonStop Operating System Event Management Programming Manual

Introduction

HP NonStop Operating System Event Management Programming Manual—520372-020

1-2

Programmatic Event Message Management

Using the EMS programmatic interface, you can write an application in C/C++,

COBOL, Pascal, Transaction Application Language (TAL), or TACL that uses a

consumer distributor to read events from the EMS log file. The application can take

appropriate action in response to a particular event.

Your application can be presented with a subset of the event messages by

implementing a filter with the consumer distributor used by the application.

Programmatic Elements of Event Messages

An EMS event message consists of Subsystem Programmatic Interface (SPI) tokens.

Each token represents a unit of information that describes the event.

For more information about SPI tokens, see the SPI Programming Manual.

Topics:



Source Files for Token Definitions on page 1-2



Variable Naming Rules on page 1-3



Message Subsystem and Number on page 1-3



Message Subject on page 1-3



Potentially Critical or Noncritical Event Designation on page 1-4



Action Events on page 1-4



Other Tokens on page 1-4

Source Files for Token Definitions

If you write an application in C/C++, COBOL, Pascal, TAL, or TACL, each source

module must include the token-definition files described in Table 1-1:

Table 1-1. Token Definition Source Files

Language

SPI Token Definition

File

EMS Token Definition

File

Operating System

Token Definition File

C/C++ ZSPIDEF.ZSPIC ZSPIDEF.ZEMSC, ZSPIDEF.ZGRDC

COBOL ZSPIDEF.ZSPICOB ZSPIDEF.ZEMSCOB ZSPIDEF.ZGRDCOB

Pascal ZSPIDEF.ZSPIPAS ZSPIDEF.ZEMSPAS ZSPIDEF.ZGRDPAS

TACL ZSPIDEF.ZSPITACL ZSPIDEF.ZEMSTACL ZSPIDEF.ZGRDTACL

TAL ZSPIDEF.ZSPITAL ZSPIDEF.ZEMSTAL ZSPIDEF.ZGRDTAL