NonStop Operating System Event Management Programming Manual

Introduction
HP NonStop Operating System Event Management Programming Manual—520372-020
1-3
Variable Naming Rules
In addition, use the file that is specific for the component and programming language
you are using. These components are identified by a four-character component ID. For
example, if you are writing an application in COBOL for the system monitor, use the
ZSPIDEF.ZMONCOB file.
Variable Naming Rules
All definitions and component fields of structures in the token-definition files begin with
the letter Z. To avoid conflicts, do not begin any of the variable names you define in
your applications with an uppercase or lowercase Z.
Message Subsystem and Number
Two syntax elements uniquely identify an EMS event message:
Message Subject
Each operating system event message contains a subject token, which immediately
follows a ZEMS-TKN-SUBJECT-MARK token. The subject token identifies the subject
of the event message. An example of a subject token is ZIPB-TKN-BUS, which
identifies the bus (X bus or Y bus) for the interprocessor bus event messages.
Usually only one subject token is present in each operating system event message.
Some event messages, however, contain two subject tokens. For example, the low-
level I/O (ZGIO) event messages contain ZGIO-TKN-CONTROLLER and
ZGIO-TKN-CHANNEL as subject tokens. In this case, a ZEMS-TKN-SUBJECT-MARK
token precedes each subject token.
Note. All definitions are shown in DDL format using hyphens (-) as separators. If you are
programming in TAL or TACL, substitute the circumflex symbol (^) for the hyphens. If you are
programming in Pascal or C, substitute the underscore symbol (_) for the hyphens. For a quick
explanation of DDL, see the SPI Programming Manual.
Syntax Element Description
Symbolic component and event name Has the form Zcomponent-EVT-name, where
component is the three-character abbreviation for
the component, and name identifies the event that
caused the event message to be generated. For
example, ZIPB-EVT-BUSUP is the symbolic name
for the interprocessor bus event message that is
generated when a bus to a processor is brought up.
Event number ZEMS-TKN-EVENTNUMBER token contains the
event-number value.