NonStop Operating System Event Management Programming Manual

System Clock Event Messages (ZCLK)
HP NonStop Operating System Event Management Programming Manual—520372-020
8-7
Recovery Action Requiring Vendor Support

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.
Recovery Action Requiring Vendor Support
Contact your service provider or the Global Mission Critical Solution Center (GMCSC),
as directed by your local operating procedures. Provide relevant information, such as:

The system number

Descriptions of the problem and accompanying symptoms

Details from the message or messages being generated

Supporting documentation such as EMS logs

Trace files or saveabend files, if generated

Processor memory dumps, if the problem has resulted in a halted processor
Messages
100: ZCLK-EVT-TIMERESETDST
System time was automatically reset because of a DST change.
Subject: ZCLK-TKN-SYSCLOCK
Potentially critical event: No
Action event: No