×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Limited support

 

BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 Open link .
MainView Infrastructure 6.3 ... Customizing after installation Manual customization

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 MainView products except MainView FOCAL POINT, to which it does not apply.

  • If you want to use Alert Manager, this task is required. For information about MainView Alarm Management and Alert Manager, see Using Alarm Management.

Note

  • 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 MainView 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.

    Note

    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 MainView 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 MainView AutoOPERATOR 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 MainView AutoOPERATOR EXECs in MainView AutoOPERATOR advanced security.

Was this page helpful? Yes No Submitting... Thank you
Last modified by Mary Cameron on Aug 14, 2020
customization task

Comments

Log in or register to comment.

Allocating Alert Manager DIV data set
Verification of MainView Logger data sets
© Copyright 2013 - 2020 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.