HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

101

102

103

104

105

106

107

108

109

110

evmtemplate(4) evmtemplate(4)

i18n_msg_id i18n_msg

Identiﬁes 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

speciﬁed, the i18n_msg must refer to a message identiﬁer 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

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 deﬁned 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 speciﬁed 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 docu-

mentation 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 speciﬁed 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 speciﬁed in the template, but usually should

be overridden by the value in the posted version of the event. Values supplied 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 identiﬁes 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 speciﬁed, the

i18n_msg must refer to a message identiﬁer 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 speciﬁed outside an

event group are global items, which will be included in each following tem-

plate that does not include them explicitly.

Notes

If you are concerned with allowing your ﬁle 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 ﬁrst two components (sys.unix

) of the

name of any system event. This will make it unnecessary to change the ﬁle if the other system uses a

different event name preﬁx.

EXAMPLES

The following ﬁle is an example of an event template ﬁle.

# 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 }

102 Hewlett-Packard Company − 3 − HP-UX 11i Version 3: February 2007