Issuing one notification for multiple conditions(1)

In the real-time analysis examples you’ve seen so far, CICSPlex® SM has monitored one or more instances of a resource in one or more CICS® systems, and each occurrence of a notifiable condition has caused an external message or an event notification to be issued. So, for example, if the CDSA falls too low in three AORs, you see three sets of notifications. However, there are occasions when a single notification for a group of CICS systems, or even for the entire CICSplex, would be preferable.

To implement this "consolidated" reporting, you create an analysis point specification, in which you identify a single CMAS as the primary CMAS for analysis point monitoring (APM). The primary CMAS consolidates results from all the systems being checked to give a single result.

In this example, you will see how to monitor the number of current tasks throughout the CICSplex PLXPROD1. When the average number of current tasks in PLXPROD1 goes above a specified number, a single event notification will be issued, and an alert will be issued to NetView®. The checking will occur from 09:30 through 11:30, for which period a time-period definition (PDFEARLY) has already been created. Also, the CICS system group CSGPLX01, which contains every CICS system in PLXPROD1, has been created.

  1. If the current context isn’t PLXPROD1, issue the command CON PLXPROD1 from the current view.
  2. Create an evaluation definition.

    From the current view, issue the command EVALDEF. From the EVALDEF view, issue the command CRE. Complete the first Create Evaluation Definition panel as shown here, and press Enter:

     ------------------- Create Evaluation Definition for PLXPROD1------------------
     COMMAND  ===>
     
     Name                  ===> RTEPAY10
     Description           ===> Current tasks in PLXPROD1
     
     Sample Interval       ===> 60            Interval between samples in seconds
     TableName             ===> CICSRGN       Resource Table Name or *
     Instance Pattern      ===> *             Specific or generic pattern
     Result Set Action     ===> AVG           Operation(ALL,ANY,SUM,MIN,MAX,AVG,CNT)
     Separate Task         ===> NO            Run as a separate task (YES, NO)
     
     Evaluation Column     ===> CURRTASKS     Column name to evaluate or *
         either Operator   ===>               (EQ,NE,LT,GT,LE,GE)
                Value      ===>
                Severity   ===>               (VLS,LS,LW,HW,HS,VHS)
         or set Thresholds:     Provide 3 low and/or 3 high values, N=Normal
     
    VLS          LS          LW   (N)    HW          HS         VHS
                                         50          65          70
     
     View                  ===> CICSRGN       View invoked for this Evaluation
     
     Type DOWN or UP to view other Evaluation Definition screens.
     Press Enter to create Evaluation Definition.
     Type END or CANCEL to cancel without creating.

    The current number of tasks is to be checked every 60 seconds. An average of 50 or higher will be notified, and the severity of the notification will increase as the average number of current tasks increases.

    Note:
    This example does not make use of the second Create Evaluation Definition panel. For a complete description of the EVALDEF view and the panels you use to create one, see EVALDEF (Evaluation definitions).
  3. Create an action definition.

    From the current view, issue the command ACTNDEF. From the ACTNDEF view, issue the command CRE. Complete the Create Action Definition panel as shown here, and press Enter:

     -------------------- Create Action Definition for PLXPROD1 --------------------
     COMMAND  ===>
     
     Action Name   ===> RTAPAY10
      Description  ===> High task load in PLXPROD1
     
      Event        ===> YES          Generate Event (Yes/No)
       Event View  ===> CICSRGN      View for Event
       Priority    ===> 255          Event Priority (1 to 255)
       Event Text  ===> High task load in PLXPROD1
     
      External Msg ===> NO           Generate External Message (Yes/No)
       Enter Msg   ===>
       Exit Msg    ===>
     
      Alert        ===> YES          Generate Alert (Yes/No)
       CMAS Name   ===> CMSSYS1      CMAS to Issue Alert
       Enter Text  ===> Task load climbing in PLXPROD1
       Exit Text   ===> Task load falling in PLXPROD1
     
       Restart     ===> NO           Cancel for ARM Restart (Yes/No)
     
     Press Enter to create the Action Definition.
     Type END or CANCEL to cancel without creating.

    The ACTNDEF view is redisplayed.

    Note:
    For a complete description of the ACTNDEF view, see ACTNDEF (Action definitions).
  4. Create an analysis definition.

    From the current view, issue the command RTADEF. From the RTADEF view, issue the command CRE. Complete the Create Analysis Definition panel as shown here, and press Enter:

     ------------------------ Create Analysis Definition for PLXPROD1 --------------
     COMMAND ==>
     
      Name             ===> RTDPAY10
      Description      ===> Average current tasks
      Perform Ops      ===> NO        Perform EVALDEF operations changes (YES, NO)
      Sample Interval  ===> 60        Interval between samples in seconds (1-86400)
      Action Name      ===> RTAPAY10  Action definition name or generic
     
                             VLS    LS    LW    HW    HS   VHS
     Entry Intervals   ===> 0001  0001  0001  0004  0003  0002
     Exit  Intervals   ===> 0001  0001  0001  0002  0002  0002
     
     Evaluation expression:
     ===> RTEPAY10
     ===>
     ===>
     ===>
     ===>
     ===>
     ===>
     
     Press Enter to create the Analysis Definition.
     Type END or CANCEL to cancel without creating.

    CICSPlex SM will sample the results of its evaluations every 60 seconds. An HW condition will be flagged when a severity of at least HW has been seen in four successive samples. An HS condition will be flagged when a severity of at least HS has been seen in three successive samples. A VHS condition will be flagged when a severity of VHS has been seen in two successive samples. Each of the conditions will be cleared only when two, less severe samples are seen in succession.

    Note:
    For a complete description of the RTADEF view, see RTADEF (Analysis definitions).
  5. Create an analysis group.

    From the current view, issue the command RTAGROUP. From the RTAGROUP view, issue the command CRE. Complete the Create Analysis Group panel as shown here, and press Enter:

     ------------------------- Create Analysis Group for PLXPROD1-----------
     COMMAND  ===>
     
      Group Name          ===>  RTGPAY10
      Description         ===>  AP - CICSplex health checks
     
     
     
     
     
    Press Enter to create Analysis Group.
    Type END or CANCEL to cancel without creating.

    The RTAGROUP view is redisplayed.

    Note:
    For a complete description of the RTAGROUP view, see RTAGROUP (Analysis groups).
  6. Add the analysis definition to the analysis group.

    From the current view, issue the command RTADEF. In the RTADEF view, tab to the entry for RTDPAY10, and issue ADD from the line-command field. The Add RTADEF to Analysis Group panel is displayed. In the Analysis Group field, type RTGPAY10. In the Time Period field, type PDFEARLY. Press Enter. The RTADEF view is redisplayed.

    You can check that this step has worked by looking at the RTAINGRP view.

  7. Create an analysis point specification.

    From the current view, issue the command APSPEC. From the APSPEC view, issue the command CRE. Complete the Create Analysis Point Specification panel as shown here, and press Enter:

     ----------------------- Create Analysis Point Specification for PLXPROD1 ------
     COMMAND  ===>
     
      AP SpecName        ===> RAPPAY10
      Description        ===> Analysis point for PLXPROD1
     
     
    Press Enter to create AP Specification.
    Type END or CANCEL to cancel without creating.
     

    The APSPEC view is redisplayed.

    Note:
    For a complete description of the APSPEC view, see APSPEC (Analysis point specifications).
  8. Add the analysis group to the analysis point specification.

    From the current view, issue the command RTAGROUP. In the RTAGROUP view, tab to the entry for RTGPAY10, and issue AAP from the line-command field. The Add Analysis Group to AP Specification panel is displayed. In the Specification Name field, type RAPPAY10. In the Scope field, type CSGPLX01. Press Enter. The RTAGROUP view is redisplayed.

    You can check that this step has succeeded by looking at the RTAINAPS view.

  9. Identify the primary CMAS.

    From the current view, issue the command APSPEC. In the APSPEC view, tab to the entry for RAPPAY10, and issue ADD from the line-command field. The Add APSPEC CMAS Association panel is displayed. In the CMAS Name field, type CMSSYS1. In the Type field, type PRIMARY and press Enter. The APSPEC view is redisplayed.

    When you identify the primary CMAS, the analysis point specification, and any analysis groups and analysis definitions associated with it, are installed automatically. For this reason, you should create the analysis definitions and analysis groups before you identify the primary CMAS.

  10. Identify a secondary CMAS (optional).

    In the APSPEC view, tab to the entry for RAPPAY10 again, and issue ADD from the line-command field. The Add APSPEC CMAS Association panel is displayed. In the CMAS Name field, type CMSSYS2. In the Type field, type SECONDARY and press Enter. The APSPEC view is redisplayed.

    When you identify a secondary CMAS (which is optional), that CMAS assumes the role of the primary CMAS if it ever loses contact with the primary CMAS. That is, the secondary CMAS monitors resources in those CICS systems it can communicate with until its contact with the primary CMAS is restored.

    You can check that primary and secondary CMASs have been successfully identified by looking at the APCMAS view.

[[ Contents Previous Page | Next Page Index ]]