Working with the DBRM View - Documentation for BMC AMI Strobe 21.01
You can also focus your examination of measurement session history on a specific DBRM. This approach can reveal the overall effect on performance that can be traced to a specific DBRM.
Examining the DBRM Summary View
To focus your analysis on DBRMs:
- Select the H - HISTORY option from the Strobe Options menu.
- Press Enter to display one of three summary view panels (job step, DBRM, or Transaction), depending on the view you last selected.
- If necessary, type DBRM at the command line to display the Strobe
- History - DBRM Summary panel.
Each summary row on this panel represents a set of measurement session history records that have information on the DBRM indicated in the DBRM NAME column. The HISTORY RECORDS column indicates the number of measurement sessions in the set. Information relating to the most recent measurement session in the set is displayed to the right of the HISTORY RECORDS column.Strobe - History - DBRM Summary Panel
- Type an S to the left of the row for which you want to examine the measurement session history records.
- Press Enter to display the Strobe - History - DBRM Detail panel.
Examining the DBRM Detail View
Strobe - History - DBRM Detail Panel
As shown in the preceding figure, the Strobe - History - DBRM Detail panel provides the following information without additional scrolling:
STMT-EXEC COUNT | Number of times SQL statements were executed in this DBRM during the measurement session |
TOTAL CPU% | Total percentage of all CPU time used within the address space by this DBRM |
In the preceding figure, you can examine the measurement session history records associated with a particular DBRM, focusing on the number of SQL statements Strobe observed during the measurement session or on the total percentage of all CPU time used within the address space by this DBRM. The date and time of the measurement session are fixed columns and appear on all of the DBRM detail panels.
As shown in the following figure, scrolling to the right provides the following additional information:
STMT-EXEC AVG TIME | Average amount of elapsed time per SQL statement that Strobe observed during the measurement session. |
AVG CPU SECS/STMT | Average number of CPU seconds per statement used to execute one SQL statement during the measurement session. |
AVG SERV UNITS/STMT | Average number of service units per SQL statement that Strobe observed during the measurement session. A service unit is a machine-independent unit of work consisting of a fixed number of instructions. |
DBRM CREATE DATE | Date and time that the database request module was created. |
Strobe - History - DBRM Detail Panel (One Scroll Right)
As shown in the following figure, scrolling to the right twice provides the following information:
COST | Whether the program is assigned a prime (PR) or non-prime (NP) cost designation. |
SYSTEM | System on which the measurement session took place. |
CPU MODEL | CPU model on which the measurement session took place. |
HISTORIAN | Job name or the TSO user ID of the person who created the measurement session history record. |
Strobe - History - DBRM Detail Panel (Two Scrolls Right)
Scrolling to the right three times displays the comments associated with the measurement session history records.
Examining Trends in DBRM Activity
To examine the changes in the performance of a DBRM, relative to other measurement sessions, complete the following steps:
- On the Strobe - History - DBRM Detail panel, specify a baseline measurement session history record by typing a B to the left of the record.
- Select one or more records to compare to the baseline selection by typing O to the left of the record.
- Press Enter to display the Strobe - History - DBRM Comparison panel.
Strobe - History - DBRM Comparison Panel
The Strobe - History - DBRM Comparison panel provides the following DBRM-specific information:
STMT-EXEC COUNT | Number of times SQL statements were executed in this DBRM during the measurement session |
TOTAL CPU% | Total percentage of all CPU time used within the address space by this DBRM |
As shown in the following figure, scrolling to the right once provides the following additional information:
STMT-EXEC AVG TIME | Average number of times an SQL statement was executed during the measurement session. |
AVG CPU SECS/STMT | Average number of CPU seconds used to execute one SQL statement during the measurement session. |
AVG SERV UNITS/STMT | Average number of service units used to execute one SQL statement during the measurement session. |
DBRM CREATE DATE | Date and time that the database request module was created |
Strobe - History - DBRM Comparison Panel (One Scroll Right)
Scrolling to the right again displays the comments associated with the measurement session history records.
Calculating Changes in DBRM Operating Costs
From the Strobe - History - DBRM Cost Comparison panel, you can quickly see changes in the cost per run and the cost per year (total annualized savings) for the selected DBRMs, as compared to the baseline DBRM. To view the changes in operating costs:
- Type CC at the command line of the Strobe - History - DBRM Comparison panel.
- Press Enter to display the Strobe - History - DBRM Cost Comparison panel.
Strobe - History - DBRM Cost Comparison Panel
To see the annualized costs for this DBRM, you must enter the annual frequency in the ANNUAL FREQUENCY field in the top center portion of the panel. Annual frequency is the estimated number of times per year that the DBRM is executed.
On the Strobe - History - DBRM Cost Comparison panel, you can examine the following DBRM-specific information:
COST | Whether the program is assigned a prime (PR) or non-prime (NP) cost designation. |
AVG CPU SECS/STMT | Average number of CPU seconds used to execute one SQL statement during the measurement session |
AVG SERV UNITS/STMT | Average number of service units used to execute one SQL statement during the measurement session |
COST/STMT | Estimated cost to execute one SQL statement. This amount is based on the dollar value per CPU hour or per 1000 service units for the particular system and CPU model on which the measurement session was executed. |
COST/YEAR | The estimated cost to execute the SQL statement over the course of one year. This amount is based on the specified dollar value per CPU hour or per 1000 service units for the particular system and CPU model on which the measurement session was executed. |
Scrolling to the right once displays the comments associated with the measurement session history records.
