EMS Manual

Standard Events
EMS Manual—426909-005
9-14
Object Name for Event Subject
an automated teller machine (ATM), and the token value contains the actual name
of that ATM.

Should uniquely identify the process, or control point, in the NonStop Kernel
network where management applications can send commands to control or inquire
about the object.
If the name cannot identify the control point, the subsystem or application must
specify the name of a manager process if that is the control point.
The naming scheme for an event subject depends on the type of object. In general,
consider the name of an object a handle to be consistent with the naming philosophy of
the D-series and later operating systems. The ways to name an object are:

Object is an operating system object and defined within a single process.
If the object is an operating system object—addressable, and within the control of
the NonStop Kernel operating system—and defined within a single process of
name \node.$process, you must use one of these formats to uniquely name the
object within the process:
\node.$process.#subdev.#subdev
\node.$process.#subdev
\node.$process
If the $process name is also the control point where commands for the object can
be sent, subsystem and application developers do not need to supply other
information in the event to identify the control point. They could identify a different
control point, such as the name of a manager process, if necessary.

Object is an operating system object but not defined within a single process.
If the object is an operating system object but not defined within a single process—
such as CPU, bus, backplane, fan, and power supply—name the object using
\node.anything.
Subsystem and application developers must specify the entity, providing the name
of the manager process in the event or describing the algorithm used to resolve the
uniqueness of these names or to identify the control point.

Object is not an operating system object.
If the object is not an operating system object, the object can be named using
whatever format best describes the object. The name used must be easily
differentiated from one of the preceding form.
Subsystem and application developers must specify the entity, providing the name
of the manager process in the event or describing the algorithm that is used to
interpret the name.