NonStop Operating System Event Management Programming Manual
Disk Process Event Messages (ZDSK)
HP NonStop Operating System Event Management Programming Manual—520372-020
11-19
Information in Event Description Messages
Descriptions of individual event messages (for a linked list, see Table 11-1 on
page 11-1)
Information in Event Description Messages
Each description contains the following information:
A header showing the numeric value and symbolic name for the event number.
A paragraph describing the event message.
A list:
Identifying the subject of the event message.
Indicating whether the event is channel-related, device-related, or controller-
related.
Indicating whether the message identifies a potentially critical event (whether
ZEMS-TKN-EMPHASIS has the value ZSPI-VAL-TRUE).
Indicating whether the message identifies an action-attention event (whether
ZEMS-TKN-ACTION-NEEDED has the value ZSPI-VAL-TRUE).
Identifying the sender of the event message to the EMS collector ($0 process).
Indicating whether the event message is sent to the TMDS collector (D-series
NonStop operating system RVUs) or OSM/TSM collector (G-series and H-
series NonStop operating system RVUs).
A box contains the list of tokens that can appear in the event message. Header
and other common tokens are not included in the list but are described in
Section 2, Header and Common Tokens
. The tokens might not necessarily appear
in the message buffer in the same order that they are listed in the box. The tokens
in the list are either:
Unconditional (always present in the message).
Conditional (present in the event message only under certain conditions).
The box also contains the event-message text, which is taken from a template file
by the EMSTEXT procedure.
A description of each token follows the box.
The cause describes what might have caused the event.
The effect describes the implication (if any) of the generated event.
The recovery describes the action (if any) to be taken.
Note. Each event message also contains the header tokens listed in Section 2, Header and
Common Tokens, and the tokens listed in the Common Definitions on page 3-5.