Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

What ALERTs are


An 

BMC AMI Ops Automation

 ALERT consists of a number of components both textual (visible) and user-specified (machine accessible). 

BMC AMI OpsA

 ALERTs are messages that 

BMC AMI OpsA

 creates to notify operators of exceptional situations that might require manual intervention and attention.

BMC AMI OpsA ALERTs can originate from

  • BMC AMI OpsA Rule Processor
  • BMC AMI OpsA REXX (or CLIST) EXECs
  • IBM NetView address spaces issuing the NAIEXEC ALERT command
  • ALERTs created by other products and alarms. For more information, see the ALRTRCVE=YES parameter in BBPARM member BBISSPxx.   

The way an ALERT looks and functions depends on what you specify when the ALERT is created from any of these sources.

For documentation about how ALERTs are generated from these sources, refer following table:

Where to find more information about ALERTs

To read about

See

Creating ALERTs based on various system events with BMC AMI OpsA Rules

Using-BMC-AMI-Ops-Automation-basic-applications: Using Rules contains information about how to create Rules and how to create ALERTs from Rules

Creating ALERTs from BMC AMI OpsA REXX (or CLIST) EXECs

Creating ALERTs from the NetView address space

In addition, BMC AMI OpsA maintains information about the following ALERTs attributes:

  • The date and time ALERTs originated
  • Where the ALERTs originated from
  • The ALERT's priority and color
  • The ALERT's queuing characteristics
  • Target user information
  • Any user-specified data associated with a particular ALERT


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*