Unexpected real-time analysis results

This section uses two sample problems to discuss ways to approach unexpected real-time analysis results. One problem deals with system availability monitoring (SAM), the other with MAS resource monitoring (MRM).

An example SAM problem

A CICS® system is known to be running and short on storage, yet the condition does not show up in the EVENT view.

  1. Verify that the MAS view shows an active status for that CICS system.
    Figure 58. MAS view showing active CICS system
    27FEB2005  02:57:49 ----------- INFORMATION DISPLAY ---------------------------
    COMMAND  ===>                                                 SCROLL ===>
    CURR WIN ===> 1        ALT WIN ===>
     W1 =MAS===============EYUPLX01=EYUMAS1A=27FEB2005==02:57:49=CPSM====1=========
    CMD Name     Type   CMAS     Status   MON RTA WLM Description
    --- -------- ------ -------- -------- Act Act Act ----------------------
        EYUMAS1A LOCAL  EYUCMS1A ACTIVE   YES YES YES TOR1 - SYSA
     

    If the MAS view does not show an active status, see Incomplete operations data returned.

  2. Verify that the RTA Active field on the MAS view indicates YES. This is required for CICSPlex® SM to perform system availability monitoring for any of the predefined conditions (SOS, SYSDUMP, TRANDUMP, MAXTASK, STALL). You can make real-time analysis active immediately by using the UPD line command, and setting the RTA Active field on the first panel to YES. To make the change permanent, you must update the CICSSYS definition. For more information about the CICSSYS view command, see CICSPlex System Manager Administration.
  3. Determine which action definition controls what happens for the short-on-storage (SOS) condition. To do this, use the BRO line command to browse the MAS information. Scroll down to the Browse Analysis panel.
    Figure 59. Example of the Browse Analysis panel for the MAS view
    ------------------------------- Browse Analysis for EYUPLX01 ------------------
    COMMAND ===>
     
    MAS      EYUMAS1A  RTA Active      YES
     
    Primary CMAS            EYUCMS1A  CMAS Name
    Active Period           PRIME     Period Def
     
     System availability management:
     
                          Action         Severity
      SAM
      SOS                 SOSPRI1        VHS
      SYSDUMP
      TRANDUMP
      MAXTASK
      STALL
     
    Type DOWN or UP to view other MAS screens.
    Type END or CANCEL to terminate browse
     

    In the example shown in Figure 59, the SOS condition is controlled by an action definition called SOSPRI1, and the other conditions assume the default actions. The default action is to issue a CICSPlex SM EVENT and to send condition entry and condition exit WTO messages.

  4. Use the ACTNDEF command to see which type of external notification is supposed to be issued for an SOS condition.
    Figure 60. Example of the ACTNDEF view
    27FEB2005  16:00:54 ----------- INFORMATION DISPLAY ---------------------------
    COMMAND  ===>                                                 SCROLL ===>
    CURR WIN ===> 1        ALT WIN ===>
     W1 =ACTNDEF===========EYUPLX01=EYUPLX01=27FEB2005==16:00:54=CPSM====1=========
    CMD Name      Event    View    Msg  Alert  ARM  Description
    --- --------  -----  --------  ---  -----  ---  ------------------------ -------
        SOSPRI1   NO               YES  YES    NO   Critical SOS on production
     

    In the example shown in Figure 60, no CICSPlex SM event is to be viewable from the EVENT view.

An example MRM problem

MAS resource monitoring (MRM) can be used to generate an event whenever any of a particular group of transactions is disabled in a particular MAS. The LOCTRAN view (with scope set to that MAS) shows that one of the transactions is disabled, yet no event shows up in the EVENT view.

  1. Verify that the real-time analysis definition is active. Set the scope to the MAS in question and issue the RTAACTV view command.
    Figure 61. Example of the RTAACTV view showing active analysis definitions
    27FEB2005  04:53:08 ----------- INFORMATION DISPLAY ---------------------------
    COMMAND  ===>                                                 SCROLL ===>
    CURR WIN ===> 1        ALT WIN ===>
     W1 =RTAACTV===========EYUPLX01=EYUMAS1A=27FEB2005==04:53:08=CPSM====6=========
     CMD Name     System   Status    Period   Rate  Action   Def
     --- -------- -------- --------- -------- ----- -------- Type---
         DSAGETMN EYUMAS1A PENDING   TVSHIFT2    60 DSAGMACT RTADEF
         TRANDIS  EYUMAS1A ACTIVE                60 DSALWACT RTADEF
         LFILEDEL EYUMAS1A PENDING   TVSHIFT2   300 LFILDACT RTADEF
         LFILEOPN EYUMAS1A ACTIVE               300 LFILOACT RTADEF
         PGMUSE   EYUMAS1A ACTIVE                60 PGMUSACT RTADEF
         PGM1     EYUMAS1A PENDING   TVSHIFT2    60 PGMUSACT RTADEF
     

    If the analysis definition is not in the list, or is in the list with a PENDING status, that explains why nothing shows up in the EVENT view. The PENDING status indicates that the analysis definition is not within the Period shown. Absence from this active list indicates the analysis definition was either discarded (by use of the DSC line command on the RTAACTV view) or never installed.

  2. Examine the analysis definition and related evaluation definitions and action definitions. If the analysis definition is listed in the RTAACTV view, you should reexamine the analysis definition, the evaluation definitions that make up the analysis definition’s evaluation expression, and the associated action definitions.

    Here are some points to consider:

    1. Sample Interval

      The sample interval affects how soon the occurrence of a particular condition (such as a transaction becoming disabled) results in a real-time analysis notification. Also keep in mind that there are two sample intervals: the evaluation definition has a sample interval, which determines how often a resource is sampled, and the analysis definition has a sample interval, which determines how often an evaluation expression is evaluated.

    2. Entry and Exit Intervals

      An analysis definition’s entry and exit intervals have an effect on when a real-time analysis notification follows the occurrence of a certain condition.

    3. Action definitions

      You should ensure that the action definition associated with an analysis definition is set up to deliver the action that you expect. It is possible that a notification results in an SNA generic alert and not in an external message or a CICSPlex SM event.

[[ Contents Previous Page | Next Page Index ]]