Using screen definitions to solve problems

If you frequently experience problems in a given area—for example, excessive CPU utilization—you might want to create a screen definition so that you can start debugging the problem immediately.

Related topic

Using-BMC-AMI-Ops-Monitor-for-z-OS-to-solve-performance-problems

Creating a screen definition

  1. Open multiple windows.
  2. Display a different view in each window; for example, JCPU in window 1, CPUSTAT in window 2, and WCPU in window 3.
  3. On the command line, type SAVE Screen.
  4. Assign a unique name to the screen definition; for example, CPUDATA.

  5. The next time you notice that CPU utilization is high, on the command line type SCReen CPUDATA.

    Important

    All three views are displayed in the exact same configuration that you saved. You can divide the display area into a maximum of 20 windows.

    BMC AMI Ops Monitor for z/OS ships several screen definitions to help you get started in solving performance problems: MMRSCR01, MMRSCR02, MMRSCR03, and the default screen definition, MVMVS. These screen definitions should help you form ideas for creating your own definitions. All of them provide a starting point from which you might begin using hyperlinks to explore system performance.

Example

The following example demonstrates how you might use screen definitions.

Suppose you find that you frequently display a particular combination of views, and that you always display the views in the same windows, as shown in the following figure.

 W1 -SYSSTAT-----------SYSE-----*--------10NOVYYYY==HH:MM:SS----MVMVS----D----1
 C SMFID %Util %Util %Util %Util %Util %Util  I/O  %Ut-R %Ut-R %Ut-R %Ut-R  I/O
 - -----    CP  zAAP  zII    Bat   TSO   STC  Intr   CPU   Bat   TSO   STC IntrR
   SYSE   30.5   4.4   0.3         4.2  26.3 101.8  18.8         4.7  14.1  26.3
                                                                               
 W2 -WOBJ--------------SYSE-----*--------10NOVYYYY--10:01:35----MVMVS----D---49
 C Workload Typ #AS       % Service Objective  Tran   Tran   Job  Jobs          
 - -------- --- ---       0.......50......100  Rate  Total Total  /Min          
   TSONRM   SCL  16 250.0  *****************+  0.37     31                      
   STCLOW   SCL   1 100.0  *****************                                    
   SYSTEM   SCL  17 76.00  *************                                        
   STCPAS   SCL   6 48.00  ********                                             
 W3 =WKLIST============SYSE=====*========10NOVYYYY==10:02:13====MVMVS====D===65
 C Workload Type Description                    Istatus Cstatus Obj Begin End   
 - -------- ---- ------------------------------ ------- ------- --- ----- -----
   ALLASCH  ASCH All ASCH Address Spaces        Active  Active  NO  00:00 00:00
   ALLBAT   BAT  All Batch Address Spaces       Active  Active  NO  00:00 00:00
   ALLOMVS  OMVS All Open MVS Address Spaces    Active  Active  NO  00:00 00:00
   ALLSTC   STC  All Started Tasks              Active  Active  NO  00:00 00:00
   ALLTSO   TSO  All TSO Address Spaces         Active  Active  NO  00:00 00:00
   ALLWKLDS COMP All Address Spaces             Active  Active  NO  00:00 00:00
   APPC     WKLD APPC Workload                  Active  Active  YES 00:00 23:59

The screen is divided into three windows, each window containing information about a different performance aspect:

  • Window 1 contains the SYSSTAT view, which displays an overview of the entire system.
  • Window 2 contains WOBJ, which shows how well workloads are meeting their service objectives.
  • Window 3 contains WKLIST, which allows you access to any workload on the system.

Without the ability to create screen definitions, each time that you require this information, you would have to type the commands explicitly to display each view and direct the output to one of the three windows—a rather tedious process, especially if you perform it often.

If you create a screen definition, however (perhaps under a name such as OVERVW), you can type SCReen OVERVW on the command line at any time to display the SYSSTAT, WOBJ, and WKLIST views in the exact same configuration, as shown in Sample window configuration.

Selecting an initial display

After you become experienced with 

OpsM for z/OS

, you might find that you want to see a particular screen definition immediately when you initialize 

OpsM for z/OS

.

You can do this by specifying a screen definition as an initial display. For information about choosing an initial display, type HELP FIRSTSCREEN on the command line.

Important

Only a screen definition can be designated as the initial display; views are not eligible.

Selecting a different screen for each BMC AMI Ops product

Because the Parameters Editors menu affects all 

BMC AMI Ops

 products, the screen definition that you name for one product is displayed the next time that you access any 

BMC AMI Ops

 product.

You can choose to have a unique screen definition for each BMC AMI Ops product—one for BMC AMI Ops Monitor for CMF, one for OpsM for z/OS and so on.

To create different screen definitions

  1. Create a screen definition for a single BMC AMI Ops product—for example, OpsM for z/OS.
    See Creating a screen definition for information about creating screen definitions. Give the screen definition the same name as the product identifier. For OpsM for z/OS, you would name the screen definition MVMVS.
  2. To display the Parameter Editors menu, type MVParms on the command line.
  3. Select 2 – DISPLAY.
  4. Make sure that the Initial screen field is blank.
    This step is important because BMC AMI Ops displays whatever is in the Initial screen field first. So, if you explicitly specify MVMVS, OpsM for z/OS tries to display the MVMVS screen definition for every BMC AMI Ops product, not just OpsM for z/OS.
    When the Initial screen field is blank, BMC AMI Ops looks for a screen definition by the same name as the product that is being initialized. In other words, by leaving this field blank, you implicitly specify that you want MVMVS displayed only when you are entering OpsM for z/OS.

  5. Create screen definitions for your other BMC AMI Ops products by using these identifiers:

    OpsM for z/OS

    MVMVS

    BMC AMI Ops Monitor for CMF

    CMF

    Plex Manager

    PLEXMGR

    MainView VistaPoint

    MVVP

    BMC AMI Ops Monitor for Db2

    MVDB2

    BMC AMI Ops Monitor for CICS

    MVCICS

    BMC AMI Ops Monitor for IMS

    MVIMS

    BMC AMI Ops Monitor for MQ

    MVMQ

 

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