Event Management › Implementation Process › Message Traps and Actions

Message Traps and Actions

Identify important messages and define the processing to be performed through Event Management message record and message action profiles.

These components, programs, and utilities generate Event messages:

• CCS components
• System components
• Utilities (such as cawto)
• User programs

All of these messages are sent to an event daemon for processing. The default processing, in the absence of any policy, is to write the messages to the Event Console log file.

To define a message processing policy to filter the messages that the Event daemon receives and to define specific actions to be taken, first define message records that describe which messages need processing.

A message record defines the matching criteria. Each field in the event message has a corresponding field in the message record. Message record fields can contain wildcards to match a wider range of event messages.

A message record has associated message action records that describe the action to take when a message matches the message record.

Note: For step‑by‑step procedures for defining message records and actions, see Enterprise Management in the online help.