How to Use Procedures for Event Processing › About Event Disposition Files › File Syntax of Event Disposition Files

File Syntax of Event Disposition Files

Each line in an event disposition (EventDisp) file is called an event map. Each event map can specify one or more event processing behaviors, such as whether the event is logged, or whether it generates an event. The following syntax is used for an event map:

eventcode E eventseverity processing parameters P procedure S sbgw processing flag

eventcode

Specifies the event code of the CA Spectrum event for which the processing behavior is being defined. The event code is defined in the AlertMap file that maps the trap to the event, or it is specified within the code that generates the event. The event code must be specified for CA Spectrum to process the event.

E

(Optional) Indicates that the Archive Manager logs the event data to the Distributed Data Manager (DDM) database. If the E flag is not used, the event data is temporarily logged, but it is not preserved when the SpectroSERVER is shut down and then restarted.

eventseverity

Specifies the relative severity of the event on a scale of 0 to 100, where 0 is the least severe and 100 is the most severe. If a value for event severity is not specified, CA Spectrum uses a default value of 0.

Note: The event severity parameter is not currently used by the event management system. However, if you are logging the event, you are advised to assign an event severity value. The use of this parameter can be incorporated into event processing in the future. If you are not logging the event, do not assign an event severity value.

processing_parameters

Specifies additional event processing behaviors, such as whether the event generates an alarm, clears one or more alarms, or executes one or more event rules.

P

Specifies the action code that indicates that a procedure follows.

procedure

Specifies the procedure to execute. To specify multiple procedures, use multiple instances of P procedure.

S sbgw processing flag

(Optional) Specifies whether an event should be registered for Southbound Gateway processing. It applies to modeltype specific entries only and to only those modeltypes that are derived from the southbound modeltype fragment.

An event does not require an event map in an EventDisp file, but most events have one. If an event does not have an event map in an EventDisp, the event is logged in the DDM database by default (which means that it is preserved when the SpectroSERVER is shut down and then restarted). However, no additional processing takes place. If an event has an event map, the event is processed according to the event map.

Note the following about EventDisp files:

• Empty lines in the EventDisp file are ignored.
• If a single event map spans multiple lines, include a backslash ‘\’ at the end of each line so that CA Spectrum considers the next line as a part of the event map.