Viewing workload performance with other BMC AMI Ops products
BMC AMI Ops Monitor for CICS, BMC AMI Ops Monitor for Db2, and BMC AMI Ops Monitor for IMS provide additional views when they work with VistaPoint. Each product has a set of similar views. These views give you the capability to display performance data collected from multiple regions or subsystems across multiple OS/390 images.
The top shaded area of the following figure shows Product Views Integrated with VistaPoint figure the initial five views available to these BMC AMI Opsproducts when they work with VistaPoint. Based on the BMC BBI-3 environment, these views give you the capability to present data gathered across a sysplex with multiple windows from a single screen. Normally, you shift to these views after using VistaPoint to narrow the data you want to display to a single product.
The bottom shaded area of the following figure represents the views that show data from a single region or subsystem for a particular product. These views use the BMC BBI-2 environment to present full-screen panel displays. After narrowing product problems to specific regions or subsystems with the integrated VistaPoint views, you shift to these views to get details about transactions.
Product Views Integrated with VistaPoint
Product views integrated with VistaPoint follow a common naming convention. The X prefix of each name identifies the product to which the view belongs by the first letter of the product name. For example, IMON is a BMC AMI Ops Monitor for IMS view. CMON and DMON are equivalent views of BMC AMI Ops Monitor for CICS and BMC AMI Ops Monitor for Db2, respectively.
In Figure Product Views Integrated with VistaPoint, the views are arranged in order, top to bottom, from the most general to the most specific. As in the case of VistaPoint views, hyperlinks associate views together. Typically, each successive hyperlink displays another view that expands the information that you selected from the previous view.
Starting at the top of Figure Product Views Integrated with VistaPoint, both the xSOVER and xMON views give a performance overview. Both views show the status of monitors collecting data from the workloads within your view's context. xSOVER lists all active monitors from the workloads within your view's context. xMON summarizes monitor performance of a single region or subsystem. You start with either view, depending on whether you have already narrowed your focus to a single target or not.
The xSOVER view, shown in the following figure, summarizes the performance of similar monitors that are collecting data from all workloads within your view's context. The number of monitors of a specific type are shown in the Count field at the right of the following figure.
xSOVER View
COMMAND ===> SCROLL ===> PAGE
CURR WIN ===> 1 ALT WIN ===>
W1 =DSOVER============DB2P=====*========08NOV2000====13:47:31====MVDB2========26
CMD Serv Parm Avg % Warning Avg Avg Area Count
--- ----- -------- 0.....50...100 Value-- Warning- ---- -----
DSUT ECDSA 94.4 ************* 85.00 90.00 STOR 3
DSUT CDSA 64.4 ********* 58.00 90.00 STOR 4
@ELTD FINANWRK 57.4 ******** 60.05 0.20 WKLD 2
@ELTD DB2PTEST 48.2 ******* 45.05 0.30 WKLD 1
@ELTD TOUGH2DO 40.9 ******* 40.05 0.50 WKLD 4
MXTC 27.1 **** 25.71 80.00 TASK 1
@RSTM PAYROLL 5.5 * 5.05 1.00 WKLD 4
@RSTM ACCTRET 5.5 * 5.05 1.00 WKLD 3
@RSTM ACCTRECV 5.0 * 5.05 1.00 WKLD 2
The graph shown in figure xSOVER View displays how close each monitor's average performance is to the warning threshold set for the monitor. The higher the percentage, the closer the monitor's data is to meeting or exceeding its warning threshold.
The xMON view, shown in the following figure, summarizes monitor performance by target. The two graphs shown in the following figure show the number of monitors that are exceeding their warning threshold and the average percent warning value for all monitors in the listed target.
xMON View
COMMAND ===> SCROLL ===> PAGE
CURR WIN ===> 1 ALT WIN ===>
W1 =DMON=============(PRODUCTN=*=======)08NOV2000====13:48:47====MVDB2=========2
CMD Target Actv Number in Warn Avg % Warning Maximum
--- -------- Mntrs 0.....10....20 0.....50...100 % Warning
DB2A 6 0 32.5 ***** 32.5
DB2T 7 3 ** 30.5 **** 2170.5
The xSERV view, shown in the following figure, is the default view you see after hyperlinking from xSOVER or xMON. The xSERV presents monitor data from different sources, depending upon whether you hyperlinked from xSOVER or xMON. In the case of the hyperlink from xSOVER, xSERV expands the summary performance of the monitor you selected.
The following figure shows the xSERV view that results from a hyperlink from the xMON view. In this case, the xSERV view lists all monitors that are active in the target you selected from xMON.
xSERV View
COMMAND ===> SCROLL ===> PAGE
CURR WIN ===> 1 ALT WIN ===>
W1 =DMON=====DSERV===(PRODUCTN=*=======)08NOV2000====13:51:03=====MVDB2========13
CMD Serv Parm % Warning Curr Warn Area Target
--- ----- -------- 0.....50...100 Value--- Value--- ---- --------
@ELTD JEBA08 426.8 *************+ 2.13 0.50 WKLD DB2T
@ELTD WORK2 426.8 *************+ 2.13 0.50 WKLD DB2T
@ELTD ACCTRECV 213.4 *************+ 2.13 1.00 WKLD DB2T
DSOPN 32.5 ***** 65.00 200.00 DSYS DB2A
DSOPN 30.5 **** 61.00 200.00 DSYS DB2T
SQLAC 0.0 1.47 3000.00 USER DB2T
SQLAC 0.0 0.00 3000.00 USER DB2A
COMSY 0.08 USER DB2T
THDAC 4.00 USER DB2T
COMSY 0.02 USER DB2A
@ELTM DB2AWORK 0.00 0.50 WKLD DB2A
@ELTM JEBA08 0.00 0.50 WKLD DB2A
THDAC 3.00 USER DB2A
Although the xSERV view resulting from a hyperlink from xSOVER is not shown, it presents the same format and data shown in Figure xSERV View. This example shows the xSERV view resulting from a hyperlink from xMON.
Each line represents the performance of a single monitor named in the Serv field at the left of the view. The Parm field immediately to the right of the Serv field displays the name of the VistaPoint workload or a specific monitor parameter.
Looking at figure Product Views Integrated with VistaPoint again, notice the xOBJ views that seem to be out of the normal hyperlink pathways of other product views. The xOBJ view is a specialized xSERV view. It restricts monitor performance to the monitors VistaPoint uses to measure workload performance.
COBJ View
COMMAND ===> SCROLL ===> PAGE
CURR WIN ===> 1 ALT WIN ===>
W1 =COBJ==============CICSP01==*========08NOV2000====13:53:31====MVCICS=======10
CMD Workload Avg % <= Resp Goal Resp Goal Tran Composite Target
--- Name---- Resp--- 0.....50...100 Goal- % Count Workload- --------
ACCTRECV 2.001 35.7 ***** 0.85 95 163 FINANCE CICSP01
PAYROLL 1.567 74.3 ************ 1.00 90 52 PAYROLL CICSP01
ACCTPAY 0.596 88.8 ************* 0.85 95 222 FINANCE CICSP01
CICSP01T 1.588 98.4 ************** 2.00 90 410 TESTP01 CICSP01
BILLING 0.877 105.7 **************+ 1.00 90 662 PAYROLL CICSP01
COBJ is a hyperlink destination from the VistaPoint WKOVER view. This view extends VistaPoint views to a product’s workloads. COBJC shows transaction performance of individual CICS workloads.
The % Resp field shows the percentage of transactions completing within the response-time goal set in the workload definition. The higher the percentage, the larger the number of transactions that are completing within the response-time limit.
If you look at figure Product Views Integrated with VistaPoint again, you see that both hyperlink paths and the xOBJ view converge at the plot views integrated with VistaPoint. A plot view displays a 10-line graph of monitored performance over the previous 10 data-collection periods.
The following figure shows a graph of a Db2 elapsed time monitor (@ELTD). Looking at the fields shown in the right column of the following figure, you can see that his plot shows the elapsed time of transactions occurring in the WORK2 workload that is part of the PAYROLL application. Each line represents the average elapsed time of transactions in one-minute data-collection intervals.
Plot View
COMMAND ===> SCROLL ===> PAGE
CURR WIN ===> 1 ALT WIN ===>
>W1 =DMON=====@ELTD==(PRODUCTN=DB2T====)08NOV2000====14:46:04====MVDB2=========1
>>USERS |.....|......| Response Events Parm..... WORK2
14:46:00 *********** 5.44 8 Appl..... PAYROLL
14:45:00 *** 1.48 16 Warning.. 0.50
14:44:00 *********** 5.78 6 Max/Min.. Maximum
14:43:00 **** 2.24 19 Value... 68.87
14:42:00 ** 1.28 18 Time.... 14:22:00
14:41:00 * 0.63 7 Graph Max 7.19
14:40:00 ***** 2.68 4 Target... DB2T
14:39:00 ************ 6.11 20 Descript. work only on db2l
14:38:00 ****** 2.97 10
14:37:00 * 0.68 9 Samples.. 60
|.....|......| Response Events Period... 00:10:00
Total ************** 7.19 498 Samp Int. 00:01:00
Prev Pd ********* 4.43 91 Start.... 13:46:00
Curr Pd ****** 2.91 117 Elapsed.. 01:00:00
A hyperlink field is located in the upper left corner of plot views . In the plot view, shown in Plot View, the USERS field links you to BMC AMI Ops Monitor for Db2 users view. When you use this hyperlink, you can look at individual product views. The hyperlink to individual product views lets you use BMC AMI Ops products to get the most detailed information about your target's performance.
The following figure summarizes a typical sequence of views that you might use to monitor the performance of the regions or subsystems at your site. You begin with VistaPoint to identify the product and possibly the target that needs attention by examining the performance of transaction response times. Starting with the APOVER view, each successive view narrows the focus of transaction performance until you have reached the WKDETL view. At this point, you should have a good idea about which target and product are experiencing problems.
Typical Diagnostic Sequence of VistaPoint Views
After you tentatively identify the product and target that are experiencing problems, you shift to the product views integrated with VistaPoint. These views allow you to identify the source of the problem by the type of monitors that are exceeding their warning thresholds. Again, you follow a sequence of views until you reach the plot views. When you have reached a plot view, you should be able to identify the product, target, and type of problem you are experiencing. Finally, you hyperlink to individual product views to find the source of a problem.
Section Viewing Performance over Different Periods explains the common features of the BMC AMI Ops Window Interface used by VistaPoint. Section Creating VistaPoint Workloads explains the different classes of VistaPoint views.
Related topics