This report shows performance data for queries including their average CPU time consumed and number of times run. It is sorted in descending order to highlight those queries with the largest CPU consumption. Queries that are frequently run and have high average CPU time consumption are the best candidates for converting to static SQL programs with Program Generator because they present the greatest opportunities for cost savings.
The following is an online example of the Performance Summary Based on Average CPU report:
RAAMR04T ---------------------------------- LINE 0000000 -- COLUMNS 031 079 Command ===> Scroll ===> PAGE ****************************** TOP OF REPORT ******************************* QMF QUERIES | AVERAGE CPU AND RUN COUNT | SORTED BY CPU SECONDS (DESC)| | | QUERY QUERY | AVERAGE NUMBER OF DATE OWNER NAME | CPU (SECONDS) TIMES RUN FIRST RUN ------- ---------------- | --------------- --------------- ---------- USER01 RUNAWAY | 27.63 2 2099-10-05 DBPUSR XKQ1 | 12.46 14 2099-10-05 USER01 XENDH | 5.83 2 2099-10-05 USER01 GGVEEMO | 1.11 5 2099-10-05 TSO01P XAAAR02Q | 0.30 1 2099-10-19 USER01 QTEST507Q | 0.28 2 2099-10-05 USER01 QTEST501Q | 0.24 1 2099-10-21 XND1XY XAAAR06Q | 0.22 3 2099-10-20 USER01 XAAAR011Q | 0.21 1 2099-10-21 USER01 QTEST505Q | 0.21 2 2099-10-21 USER01 QTEST502Q | 0.19 2 2099-10-21 XND1XY QTEST505Q | 0.19 1 2099-10-19 USER01 QTEST506Q | 0.14 4 2099-10-12 |
This report requires no input variables.
You can invoke this report by selecting option 4 from the Object Manager Reports Selection Menu.
Edit the sample JCL member RAAMR04J in QMFHPO.SRAASAMP. See the comments in this JCL member for instructions on what modifications are necessary before submitting the batch job.