HP-UX I/O Subsystem EVM Events

4 Components of an EVM Event
An EVM event consists of the following fields.
1) The standard data or the fixed data component:
The value of the standard data remains constant across different instances of the event.
2) The variable data:
Variable data items vary from event to event.
A typical EVM event looks as follows.
Event Full Name:
sys.unix.io.state_change.new_state._class.ccc._instance.iii.
_cim.HP_EVMEventIndication
Standard Data:
Event Name: sys.unix.io.state_change.new_state
Priority: 200
Format "An I/O node(name = $node_name) at hardware
path($hw_path) has changed state"
Variable Data:
node_name type STRING value “”
class type STRING value “”
_instance type UINT64 value 0
_cim type STRING value “”
hw_attr type EvmTYPE_OPAQUE value
hw_path type STRING value “”
The fields of the EVM event are explained below.
4.1 Standard Data
The standard data of an EVM event consists of the following:
Name The name of an event indicates the origin of an event and the reason for which the event
was generated. An event name is a series of one or more components separated by
dots. There is no restriction on the number of components in an event.
For example consider the event name:
sys.unix.io.state_change.suspended._class.ext_bus._instance.5
sys.unix Indicates that the event is a system generated event.
io Indicates that the event is generated by the I/O subsystem.
state_change Indicates that the event is generated because the I/O node has
changed its state.
4