Event Management › Implementation Process › Message Traps and Actions › How Message Activity Is Distributed

How Message Activity Is Distributed

CA Common Services for z/OS lets you distribute message and action activity across multiple servers and their clients. This capability enables you to do the following:

• Create a central event log from which all servers can be monitored.
• Send selected messages to another server for processing.
• Manage special functions such as security or tape management on dedicated consoles.

Whenever the event database is loaded, it checks the Eval node of every message record against its own node name. If its node name matches the Eval node of the message record, the record and all associated message actions are read into memory. If there is no match, the message record is ignored. The set of message and message action records read into memory constitute the event policy for the current execution of the event daemon until the policy is reloaded from the CA Datacom/AD database by a restart or the opreload command.