EMS Manual

Collector Event Messages
EMS Manual—426909-005
20-8
Tokenized Text Messages (512)
ZEMS-TKN-SUBJECT-MARK (shared)
is the standard EMS token that immediately precedes each subject token. This
event message has one subject token:
ZEMS-TKN-XSYSPID
is private to HP. It contains the system number and PID of some process
associated with the event message.
ZEMS-TKN-TEXT (nonshared)
is the text that was sent to the collector through the call to the WRITE procedure. If
the original text is more than 102 bytes, it is truncated to 102 bytes.
Cause. The cause of the event varies with the contents of the text written to the
collector. The primary and alternate collectors generate an event message (ZEMS-
EVT-WRITE-TO-0) when any process calls the WRITE procedure, rather than the
WRITEREAD procedure, to write a text message to the collector. Each text message
written to a collector becomes an ZEMS-EVT-WRITE-TO-0 event message. In this
way, text messages that come from programs written before EMS are available in
event-message form. Before EMS, the WRITE procedure was the usual mechanism for
reporting events.
Effect. The effect depends on the reported text.
Recovery. The action recommended depends on the reported text.
Programming Notes

HP recommends that you not write text messages to the primary or alternate
collector in new programs unless you are doing it as part of a transition to the EMS
system. This method of reporting events is currently supported only for
compatibility with older programs and is increasingly obsolete.

In its original form, a critical nontokenized operator message contains a BEL
character to attract the operator’s attention. In its tokenized form, the message
contains an EMPHASIS token set to TRUE (see Section 14, EMS Definitions), and
the formatted display text contains a BEL character.

When a process writes text to a collector using the WRITE procedure, the collector
is the generator of the resulting event message. In this case, the EMS event
message header tokens used to identify the reporting process describe the
collector as the reporting process. The header tokens defining the reporting
process are ZEMS-TKN-SYSTEM, ZEMS-TKN-CPU, ZEMS-TKN-PIN, ZEMS-
TKN-PROC-DESC, and ZEMS-TKN-USERID. You cannot use these header
tokens to identify the process sending the text to the collector.

When obtaining the name of the reporting process, for the best results, pass the
ZEMS-TKN-SENDERID token to the EMSGET (or EMSGETTKN) procedure.