EMS Manual
Standard Events
EMS Manual—426909-005
9-16
Object Name for a Group of Objects
If non-File System FILE_OPEN_ is used to establish communication with the
underlying object (for example, using the operating system Message System), all
the names used should be the name for the underlying object. One or more tokens
in the event can represent the names.
If the subsystem uses non-File System FILE_OPEN_ names for the underlying
object name, it must also describe how a management application can find the
Object Unavailable events generated for the underlying object by the provider of
the underlying object.
For the subsystem or application providing service for the failed underlying object, the
name that the subsystem used to define this service for other subsystems and
applications should be the name of the object in the event subject. If the name is not a
File System name or the name requires other internal names besides the File System
name, the subsystem must provide additional tokens in the event to describe the non-
File System names or the additional internal names. The subsystem should also
describe how a management application can find the Object Unavailable events
generated by subsystems that use this object.
Object Name for a Group of Objects
The object name in an event can represent a single object or multiple objects. A single
name that represents multiple objects is a group name. A group name can be used for
any objects in an event. If it is used as an event subject, it can reduce the number of
events a subsystem generates. If it is used to replace a list of objects in an event, it
can reduce the size of an event message.
A group name in an event must meet these criteria:
All objects in the group are of the same type.
The group must include all subordinate objects of a parent that are of the same
type.
The command and control interface must support commands that operate on all
group names supplied in the events.
The event recipient must be able to take the group name from the event and ask
the subsystem to return a list of the individual members. The subsystem must be
able to answer such a query regardless of the state of any of the objects in the
group or of the state of other objects in the subsystem.
An event recipient must be able to tell the difference between a group object name and
an individual object name. Differentiation can be done in two ways:
Token identification, which refers to having group object name tokens that are
different from individual object name tokens. For example, the token identifier
ZXXX-TKN-LINEGROUP would contain a group name whereas the token identifier
ZXXX-TKN-LINE would contain an individual line name.
Using a name with a wild-card character; for example, onw with an asterisk (*)
appended to the end. The presence of the wild-card character indicates that the