Alarm report (exception)
Alarm reports are commonly called exception reports or exception reporting.
The alarm report is generated when the result of the evaluation of an alarm definition is true. Alarm Management distributes the alarm report as defined in the alarm definition.
Alarm reports include a severity, message ID, message text, and other information that is specified in the alarm definition. An alarm report is just the presentation of information. It does not trigger any actions. Alerts are used to trigger actions based on the information in the reports. Alarm report types indicate trend or movement of the exception. Alarm reports are generated with the alarm types described in following table.
Report type | Description |
|---|---|
START | The previous evaluation, if any, did not indicate an alarm report condition, but the current evaluation did generate an alarm report. |
UPGRADE | The previous evaluation generated an alarm report at a lower severity level than the current alarm report evaluation. |
DOWNGRADE | The previous evaluation generated an alarm report at a higher severity level than the current alarm definition evaluation. |
CONTINUE | The previous evaluation generated an alarm report at the same severity level as the current alarm definition evaluation. |
END | The previous evaluation generated an alarm report, but the current alarm definition evaluation did not produce an alarm report. |
Alarm report distribution
When an alarm report is generated, it is distributed to default and optional destinations as specified in the alarm definition. The following table lists the destinations:
Destination | Destination type | Description |
|---|---|---|
AO IEFSSREQ | Default | A z/OS subsystem event that can be detected by the local BMC AMI Ops Automation Rules Processor when the BMC AMI Ops Automation rules are started. When the required BMC AMI Ops Automation rules are started, BMC AMI Ops Automation creates and deletes BMC AMI Ops Automation alerts based on alarm report START and END types. The BMC AMI Ops Automation rules are not enabled by default. |
Control-O IEFSSREQ | Default | A z/OS subsystem event that can be detected by Control-O. |
MV LOGGER | Default | The alarm report is written to the local Logger, if possible. If the attempt to write to Logger fails, another attempt it not made for ten minutes. The Alarm History views (ALHIST and ALHISTR) display alarm reports written to Logger. |
ALARMS view | Optional | Current alarm reports (Reports with a START type and no corresponding END type alarm report.) are displayed by the ALARMS view. The VIEW=YES|NO attribute of an alarm definition controls if the alarm reports are displayed in the ALARMS view. |
AOAnywhere | Optional | Alerts are created and deleted (only in alert repositories that have ALRTRCVE=YES specified in their BBISSP00 parmlib members) by using the AOAnywhere interface. Because this results in alerts in the ALERTS view, the VIEW=YES|NO attribute of an alarm definition controls if the alarm reports are generated for AOAnywhere. |
WTO (Write to Operator) | Optional | When the WTO attribute of an alarm definition is YES, a WTO message is written that contains the following information:
If the WTO attribute is SET, WTO messages are written without the severity indicator. |
Related topic