EMS Manual

Generating Standard Events
EMS Manual—426909-005
10-8
Task 3.2: Customize Your Standard Events
Task 3.2: Customize Your Standard Events
As needed for your subsystem, you can customize your standard events:
For event
type... Customize as follows: (page1of2)
Object
Unavailable
Identify which errors make the subject unavailable and where they originate
(use ZEMS-TKN-FAILURE-CAUSE values).
If the subject is unavailable because of errors in your subsystem (ZEMS-
TKN-FAILURE-CAUSE = ZEMS-VAL-INTERNAL-FAILED):

Define tokens describing error and diagnostic information that caused the
subject to be unavailable.

If errors warrant, define the format of a symptom string to include in the
event message (ZEMS-TKN-SYMPTOM-STRING token).
If the subject is unavailable because the underlying subsystem failed (ZEMS-
TKN-FAILURE-CAUSE = ZEMS-VAL-UNDERLYING-FAILED):

Define tokens describing error or diagnostic information returned by the
underlying subsystem.

Provide the name in the ZEMS-TKN-UNDERLYING-OBJ-NAME token. If
different than the name the underlying subsystem uses in its event
subject for this error:
1. Provide information to help management applications locate the
events.
2. Design your interface so management applications do not need
additional subsystem-specific information.
3. Define tokens for the additional name and describe how to locate the
events reported by the underlying subsystem.
Object
Available,
Object
Other State
Change
1. Define previous states (for ZEMS-TKN-STATE-PREVIOUS) and current
states (for ZEMS-TKN-STATE-CURRENT) for all subjects that generate
these types.
2. Define change reasons (for ZEMS-TKN-CHANGE-REASON) for all valid
state transitions of these subjects.