evmtemplate.4 (2010 09)

e
evmtemplate(4) evmtemplate(4)
i18n_msg_id i18n_msg
Identifies the I18N catalog message to be used in place of the
format data item when the
event is formatted for display. This item is ignored if no i18n_cat is supplied. If an i18n_set
has been specified, the i18n_msg must refer to a message identifier within the given set. If the
catalog is missing, or if the i18n_set or i18n_msg values do not refer to a message in the cata-
log, the event’s
format data item is used.
reference reference_string
This text string is intended to be used by an event channel’s explanation function to retrieve
explanation text for the event. The format of the string is defined by the event channel.
var This keyword introduces a variable group, with the body of the group being delimited by
braces. An event may include any number of variable groups.
Although actual variable values are most likely to be included in the posted version of an
event, and will override the values specified in the template version, it is usually helpful to
include the variables in the template event as well, specifying dummy values such as zero, to
provide documentation of the expected contents. For example, the template version will be
seen if the results of an
evmwatch -i
command are piped into evmshow -d.
The following keywords are recognized in a variable group:
name variable_name
The name must be made up of alphanumeric and underscore characters.
type variable_type
The type of the variable item. See the EvmEvent (5) manpage for a list of types. All
EVM variable types may be specified except for OPAQUE. If this keyword is omitted
a type of STRING is assumed.
value variable_value
Value for the variable. A value must be specified in the template, but usually
should be overridden by the value in the posted version of the event. Values sup-
plied in the template should be default or nonnormal values that will be recognized
as incomplete when the event is interpreted.
i18n_msg_id i18n_msg
For STRING variables, the i18n_msg identifies the I18N catalog message to be used
in place of the variable_value when the event is formatted for display. This item is
ignored if no i18n_cat is supplied for the event. If an i18n_set has been specified,
the i18n_msg must refer to a message identifier within the given set. If the catalog
is missing, or if the i18n_set or i18n_msg values do not refer to a message in the
catalog, the variable_value is used.
Any items specified outside an
event group are global items, which will be included in each following
template that does not include them explicitly.
Notes
If you are concerned with allowing your file to be used on other systems that support EVM in the future,
you should use the built-in macro
@SYS_VP@ in place of the first two components (sys.unix) of the
name of any system event. This will make it unnecessary to change the file if the other system uses a
different event name prefix.
EXAMPLES
The following file is an example of an event template file.
# My example event file
priority 200
event {
name myco.myapp.env.humid
format "myapp: Humidity is $humidity"
var { name humidity type INT16 value 0 }
}
event {
name myco.myapp.env.temp.normal
format "myapp: Temperature is normal ($temp)"
var { name temp type FLOAT value 0.0 }
HP-UX 11i Version 3: September 2010 3 Hewlett-Packard Company 3