EMS Manual
Generating Standard Events
EMS Manual—426909-005
10-14
Incorporating Old Events Into New Events
Change the semantics of the event.
Obsolete the event.
Stop generating the event when the same conditions occur.
Extend the event beyond the original recommended buffer size.
For any external token, you cannot:
Change the semantics and syntax of the token.
Make the token obsolete (or delete it).
Change the token name, literal value, or type of the token.
Delete the literals defined for the values of the token.
Change the offset in the fields of a structured token. Only add fields to the end of
the structure.
You can enhance an event—as long as you do not change its meaning—by adding
tokens (or token values) to the event.
Do not obsolete an event or a token. If you must, follow the policy on discontinuing a
function in your company. You must assess the impact of obsoleting your tokens or
events on operators and existing management applications. For subsystems written by
HP, you must obtain approval from HP Product Management before making tokens or
events obsolete.
Incorporating Old Events Into New Events
If the event you are converting from (old event) has the same meaning (that is, both
events report the same condition for the same subject in type and format) as a
standard event you already defined (new event):
1. If the event number (and the literal for the event number) of your new event is
different from the number of your old event, change the new event number (and its
literal) to the old event number. You must not change an existing event number or
its literal.
2. Add to the new event those tokens present in the old event but not present in the
new event.
3. Use the template of the new event to display your event. Add to the template of
your new event those tokens present in the template of your old event but not
present in the new event template.
Revising Old Events
If your old event does not have the same meaning as any of the new events,
standardize your old event: