How to start Alarm Manager with a different ParmFile to account for different environment (for example Disaster Recovery)?

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    MainView Infrastructure


    COMPONENT:

    MainView Infrastructure


    APPLIES TO:

    MainView Infrastructure 6.1.01 and higher



    QUESTION:

    How to start Alarm Manager with a different ParmFile to account for different environment (for example Disaster Recovery)?
    In order words how to automate the start of a CAS with a different ParmFile when going into Disaster Recovery mode?


    ANSWER:

    By using a specific symbolic it is easy to automate the starting of a CAS on different machine, for example when going into a Disaster Recovery situation.
    This allow different Alarm Group(s) to be activated which in turn allow for different thresholds to accommodate the different behavior and hardware in effect.

    When a CAS start, it check an Alarm Parameter file that contains a list of groups to start as well as if Alarm Manager need to be started altogether and/or list the Group started in the JobLog of the CAS.

    The CAS check for the Parameter File Name using this order.

       
    1. A file with the same name as the value of the &BBMALPRM system symbol.
    2.  
    3. A file with the same name as the CAS name.
    4.  
    5. A file named DEFAULT
    Suppose you have multiple Parameter File, shown below as an example, you can configure a z/OS PARMLIB member IEASYMxx to have a different value for a symbolic based on the Hardware Name. A CAS running on a machine call DR will use a different Parameter File accordingly. 

    In this example of a IEASYMxx, the CAS will start using Parameter File Name SCDEMO except when (in a DR situation) the symbolic be set DRPARM by z/OS. 

    SYSDEF  SYMDEF(&BBMALPRM='SCDEMO' /* The default */ 
    SYSDEF HWNAME(DR)                /* Identify a DR processor */

           SYMDEF(&BBMALPRM='DRPARM')

    One more comment, the Parameter File can also contain symbolic in the Group List to activate. This help accommodate having different behavior for different LPAR. 
    See further down where Parameter File SCDEMO use the symbolic &SYSNAME for one of the Alarm Group activate. 




     


    Article Number:

    000174463


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles