EMS Manual

Standard Events
EMS Manual426909-005
9-27
Object Unavailable Event Tokens
The subject of this event is the object that has became unavailable. If multiple objects
went out of service for the same reason, these objects can be represented by lists or
group names.
For more information about the use of this event, see Object State Monitoring
Functions on page 9-4 and Reactive Problem Management Functions on page 9-5.
These event-specific tokens are to be provided in addition to the common-standard
tokens. Unconditional token types are identified with a “U.” Conditional token types are
identified with a “C.”
Current
State
ZEMS-TKN-STATE-CURRENT (ZSPI-TYP-ENUM,U)
Indicates the new state of the object. Subsystems and applications should
provide the state information specific to their environments. After a state value
is reported in the event, its meaning is not allowed to change.
Previous
State
ZEMS-TKN-STATE-PREVIOUS (ZSPI-TYP-ENUM,U)
Indicates the previous state of the object. Subsystems and applications
should provide the state information specific to their environments. After a
state value is reported in the event, its meaning cannot change.
Change
Reason
ZEMS-TKN-CHANGE-REASON (ZSPI-TYP-ENUM,U)
Indicates the reason that the object is not available. Standard enumerated
values are:
ZEMS-VAL-NORM-TERMINATION indicates the object was terminated
normally.
ZEMS-VAL-OPERATOR-INITIATED indicates the operator has taken the
object out of service.
ZEMS-VAL-INTERNAL-FAILED indicates an error was encountered
inside the subsystem that caused the subsystem to take the object out of
service. The error could be an internal error like program logic or invalid
data, or it could be an external error like disconnected by remote network
services. If external errors are from another subsystem that this object
communicates with directly, ZEMS-VAL-UNDERLYING-FAILED should
be the change reason value.
ZEMS-VAL-UNDERLYING-FAILED indicates that the underlying service
this object depended on failed. Underlying service is the service provided
by another subsystem or application.
ZEMS-VAL-REASON-UNKNOWN indicates the change reason is not
known or not listed. Avoid use of this as much as possible because it
significantly complicates the operator's task of isolating the cause of the
problem.