Creating an Alert Manager startup procedure

Use the following procedure to set up a started task procedure for the Alert Manager PAS.

Tip

  • This task is optional for all BMC AMI Ops products.
  • If you want to use Alert Manager, this task is required. For information about Alarm Management and Alert Manager, see Using-Alarm-Management.

Related topics

Alert-Manager-PAS-library-member

Manual-customization

Important

  • BMC recommends that you run only one Alert Manager PAS per system image.
  • The recommended dispatching priority of the Alert Manager PAS is 255.
  • The Alert Manager PAS must have access to an OMVS segment with read/write access to the BMC AMI Ops Infrastructure home directory. The home directory is specified by using the HFSPATH view in PLEXMGR. For more information, see Accessing-the-HFSPATH-view.

To create an Alert Manager startup procedure

Copy BBSAMP member BBHPAS to SYS1.PROCLIB or another system procedure library.To create BBHPAS

  1. Follow the instructions at the top of the member to modify the procedure for your site requirements.

  2. (Optional) Define the Alert Manager started task procedure to your IPL procedure so that the PAS starts at system initialization.BMC recommends that you modify the COMMNDxx member in SYS1.PARMLIB to add a START command for the Alert Manager PAS:

    COM='Sprocname'

    procname is the name of the Alert Manager PAS started task procedure.

    Important

    The START commands are issued in the order that they appear in COMMNDxx. The Alert Manager PAS START command must occur after the CAS START command. For more information about defining the CAS procedure, see Creating-the-CAS-startup-procedure.

Where to go from here

Alert Manager uses the AOAnywhere facility to display product alerts. AOAnywhere, which is packaged with all BMC AMI Ops products, enables certain automation functions to be shared among products. To use AOAnywhere, associate the Alert Manager PAS with a user ID that has READ access to the following resources:

prefix.ssid.BBI.target.ACCESS

prefix.ssid.AAO.target.AOEXEC.ALRTREAD

prefix.ssid.AAO.target.AOEXEC.ALRTUPD

prefix.ssid.AAO.target.EXEC

For information about securing these resources, see Resources-used-by-multiple-products.

In addition, if you run BMC AMI Ops Automation and you plan to launch EXECs from alarm definitions, grant authority to Alert Manager to schedule those EXECs. For information about granting access to specific EXECs, see the discussion of BMC AMI Ops Automation EXECs in BMC-AMI-Ops-Automation-advanced-security.


 

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