OVNM 5.3 - Operations Agent for NonStop Event Management Guide for UNIX

HP NonStop Event Management System 24
2-2-7 Text Formatting Tools
When passed an event message, the EMSTEXT procedure returns text in DSM display format.
EMSTEXT performs these steps when it generates text for an event message:
1. If the event message points to a format template or contains a TEXT token:
a. EMSTEXT checks first for a template.
For many HP NonStop and user-written subsystems, EMSTEXT generates display text from an event
message by applying a format template found in a template file installed at system generation. The
subsystem ID and event number of the message uniquely identify its template. For information on format
templates and template files, see the DSM Template Services Manual.
b. If no template is invoked for this message, EMSTEXT checks for the TEXT token.
If EMSTEXT finds ZEMS-TKN-TEXT, it generates displayable message text from the token’s contents. This
token appears in the tokenized messages that the collector generates from the pre-EMS-style messages
issued by HP and user-written subsystems.
2. If there is no template for the message and it does not contain a TEXT token, but it was formerly a pre-EMS
style (console) message, EMSTEXT assigns a subsystem ID of EMS and an event number between 1 and
512, and produces text based on what it was before EMS.
3. Finally, if it cannot produce any text, EMSTEXT returns one of four error messages:
EMSTEXT—No template and no TEXT token for event.
SSID = subsystem-ID Event number = event-msg-ID
[Subject = first-subject-value]
This message means no format template exists for the event message, it lacks the token ZEMS-TKN-TEXT,
and it is not identifiable as one of the pre-EMS messages. first-subject-value is the formatted
representation of the first subject token in the event message. This part of the error message does not
appear if the data type of the first subject is one that EMSTEXT cannot format.
EMSTEXT—Bad event buffer: buffer-contents
This message means that the event message buffer contains invalid data. Some of it is displayed to help
you diagnose the problem. buffer-contents is up to the first 60 words of the buffer in hexadecimal
notation.
EMSTEXT—Template file problem (extstat1,extstat2): File
[open] error - filename - problem-reason. SSID = subsystem-ID
Event number = event-msg-ID [Subject = first-subject-value]
This message means an error occurred in opening or reading the template file. extstat1 and extstat2
are the two halves of the EMSTEXT extended-status code that defines the error. They are followed by “File
open error,” or “File error” if the problem was a READ error, and then the template file name and a brief
description of the reason for the error.
first-subject-value is the formatted representation of the first subject token in the event message.
This part of the error message does not appear if the data type of the first subject is one that EMSTEXT
cannot format. (EMSTEXT can format most token types, such as file, device, string, and integer.)
NOTE: Applications should retry a call to open or read a template file if a timeout message is returned. A
timeout is not a fatal error.
EMSTEXT error—(extstat1,extstat2) prevented display of event.
SSID = subsystem ID Event number = event-msg ID [Subject =
first subject value]
This message covers any case in which EMSTEXT cannot produce text from the event message. extstat1
and extstat2 are the two halves of the EMSTEXT extended-status code that defines the error. first
subject value is the formatted representation of the first subject token in the event message. This part of
the message does not appear if the data type of the first subject is one that EMSTEXT cannot format.
A printing distributor or compatibility distributor calls EMSTEXT to create text for an output device and the
ViewPoint application to create the text it displays. Any user application can call EMSTEXT. Applications
that call EMSTEXT should have a minimum of five data pages (stack).