EMS Manual

Standard Events
EMS Manual—426909-005
9-25
Object Available Event Tokens
Object Available Event Tokens
An Object Available event must be generated for a subsystem or application object
whenever the object becomes available.
The subsystem or application (or its manager process) that controls the object is
responsible for reporting this event. This event should be reported as soon as the
object becomes available, including at system and application startup time.
The subject of this event is the object that became available. If multiple objects
became available for the same reason, these objects can be represented by lists or
group names.
For more information about the use of this event, see Requirements for Standard
Events on page 9-3 and Object State Monitoring Functions on page 9-4.
These event-specific tokens must be provided in addition to the common-standard
tokens. Unconditional token types are identified with a “U.”
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 cannot 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 the object became available. Standard enumerated
values are:
ZEMS-VAL-OPERATOR-INITIATED
ZEMS-VAL-UNDERLYING-UP
ZEMS-VAL-REASON-UNKNOWN
Subsystems can add their own values, but they must be greater than or
equal to ZEMS-VAL-MIN-USER-VALUE.
ZEMS-VAL-OPERATOR-INITIATED indicates that the operator was made
available. ZEMS-VAL-UNDERLYING-UP indicates that the object has
come up because the underlying object it depends on has become
available.
ZEMS-VAL-REASON-UNKNOWN indicates a the subsystem does not
indicate a cause for the object’s availability or the reason is not listed.
Subsystems should avoid using this reason.