HP-UX Event ManagerProgrammer's Guide
NOTE: You must still include the text within the event, if the catalog file is not available when
the event text is viewed.
The catalog file must be located according to normal I18N rules, and you must include the name
of the file in your event specifications. You can provide different versions of the catalog file for
different language locales. For more information, see the System Administration document.
You can optionally break the catalog file in to multiple message sets, and specify the message
set ID in your events.
NOTE: All messages pertaining to a particular event must belong to the same set.
The data items I18N_catalog and I18N_msgset_id define the catalog name and, if applicable,
the message set for the format text and any string variables contained in the event with an
associated message ID. The I18N_format_msg_id data item provides the message ID for the
format text. If no catalog or message ID is supplied, the format text specified in the format data
item is used to display the event summary.
For information on how to establish translations for event text, see “Establishing Translations
for Event Text (I18N)” (page 28) .
Reference Data Item
The reference data item is used to find the event explanation text for a detailed display of the
event. The value of this item is passed to the event channel's explain script, along with the name
of the event, to enable it to identify the explanation text associated with the event. The format
of the field may be different for each channel, because each channel can have its own explain
script. However, for events that are stored in and retrieved from the EVM log (the evmlog
channel), this item must contain a string of the following form:
cat:catalog_name[:set_number]
Where:
catalog_name is the name of an I18N catalog containing the explanation text for the event.
To enable the explain script to locate the appropriate message, each explanation message in the
catalog must begin with the name of the event enclosed in braces.
set_number is the number of the catalog message set containing the explanation. If no set
number is supplied, the whole catalog is searched.
Third-party product vendors and local applications must not add explanations to the explanation
catalog, evmexp.cat, but must provide separate catalogs. The value of this item must be set as
a global data item in the template file.
For information about how to write event explanation text, see “Writing Event Explanation Text”
(page 24).
Variable Data Items
You can use the variable data items in your events to provide any information that is different
for each instance of an event. For example, if you are posting an event because you have detected
a high temperature, you can include the actual temperature as a floating-point value in a variable
data item.
Following are the properties of variable data items:
• Name
• Type
• Value
• Size (implicit for most types)
• I18N message ID (optional — applies to string variables only)
EVM Event Content 21