Filter
Top Products
List of Events Generated
submitted transaction submitted
started transaction being executed
complete transaction completed successfully
failed transaction failed to execute
error transaction completed but there were errors
In the case of a transaction completing with errors (a link error test or
boundary scan, for example), details of the failures are added to the
transaction outputs table.
class = event type = escalation
The name contains the name of the event being escalated and the
description contains did not complete. If a handler is registered,
it is called with a description of the event that was not handled. The
handler should pass the event to an external management agent.
class = server type = status
The description contains information on errors that occurred when
starting the server.
8.3.1 Extending the RMS Event Handling Mechanism
The RMS event handling mechanism is open and extensible. New event types and
handlers for them can be added on a site-by-site basis. For example, you might run a
periodic file system status check on each node, execute a local cleanup script and post a
file system event to RMS if the free space in the file system dropped below a prescribed
level. The handler script could perform partition-wide or machine-wide cleanup and post
a notification of the problem via email or an SNMP message.
8-6 Event Handling