Use the RMF Workload Report which shows times, with these caveats
(from MXG Documentation on Processor Utilization, ACHAP10):
Barry Merrill
The zIIP/zAAP normalization factors are only provided in the
SMF 30, 72, 79, 89, and 120, and RMF RCD records.
However, the IBM RMF reports present these data quite differently.
This system has the normalization factor, R723NFFS=569/256=2.222,
that is, one second of zIIP is equal to 2.222 seconds of CP time.
====================================================================
MXG Dataset TYPE72GO dataset values:
====================================================================
SERVICE CPUUNITS ZIPUNITS CPUTCBTM CPUZIPTM
3,932,091 1,793,920 2,137,167 178.92 213.16
====================================================================
RMF WORKLOAD REPORT:
====================================================================
Under "SERVICE TIMES", the RMF "CPU" value of 392.9 seconds is the
total of the real CPU time on CP engines, plus the NORMALIZED CPU
time on the zIIP and zAAP engines; it is NOT the CPU "TCB" time.
( 392.9 = 178.92 + 213.16 "RMF CPU" = CPUTCBTM + CPUZIPTM )
But also under "SERVICE TIMES", the RMF "IIP" (zIIP) value of 96.1
seconds is the UN-NORMALIZED, raw, seconds on the zIIP engine.
And the RMF "AAP" value for zAAPs is also the UN-NORMALIZED value.
And under "SERVICE", the RMF "CPU" value of 3931K is the TOTAL
SERVICE units from CPs, zIIPs, and zAAPs.
REPORT BY: POLICY=OWL WORKLOAD=CSSDDF
TRANSACTIONS ---SERVICE---- SERVICE TIMES ---APPL %---
AVG 0.23 IOC 0 CPU 392.9 CP 4.98
MPL 0.23 CPU 3931K SRB 0.0 AAPCP 0.00
ENDED 51 MSO 0 RCT 0.0 IIPCP 0.07
END/S 0.01 SRB 0 IIT 0.0
#SWAPS 0 TOT 3931K HST 0.0 AAP N/A
EXCTD 0 /SEC 1092 AAP N/A IIP 2.67
AVG ENC 0.23 IIP 96.1
====================================================================
IN MXG: All "workload" datasets, i.e., data captured at the service
class (TYPE72GO,RMFINTRV), or at the address space (TYPE30x,STEPS,
JOBS,SMFINTRV), or at the transaction level (101, 110, 120, IMS +)
have zIIP and zAAP CPU times THAT ARE ALWAYS NORMALIZED in MXG.
BUT: All "hardware" datasets, TYPE70, TYPE70PR, ASUM70PR from RMF
70 records have the raw, UNNORMALIZED seconds of CPU Dispatch Time
on the zIIP and zAAP engines.
As an example, then, the total ZIPACTTM recorded in TYPE70 for the
above system for the day was 10,887 seconds, but the total CPUZIPTM
in TYPE72GO for the day was 23,079 seconds.
Those 10,887 raw hardware seconds would be 24,190 normalized seconds
so the zIIP capture ratio at this site is 23079/24190 = 95.4%.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Alex Wang
Sent: Tuesday, June 24, 2014 3:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: CPU Time calculation based on RMF report
Hi Folks,
Is there anyone who knows how to calculate the CPU time in seconds by the data
showing on the RMF "The Processor Usage report"?
E.g.
RMF V1R13 Processor Usage Line 1 of 1
Samples: 900 System: AA03 Date: 06/20/14 Time: 15.00.00 Range: 900 Sec
Service --- Time on CP % --- ----- EAppl % -----
Jobname CX Class Total AAP IIP CP AAP IIP
DP21DIST SO SYSSTC 0.2 0.0 0.0 0.9 0.7
DP31DBM1 S DB2STCB 0.2 0.0 0.0 0.2 1.1
TCPIP SO SYSSTC 0.2 0.0 0.0 0.2 0.0
Let's suppose in the LPAR AA03, there are 20 LCPs. Could I use the following
formula?
CPU time = (EAPPL/LCP numbers) * (interval seconds) /100
Thus, the started task DP21DIST spent 0.36 S CPU time in 15 minutes (900
seconds).
And it spent 1.8 S ZIIP time 15 minutes (900 seconds).
Looking forward to hearing from you.
Thank you! Alex
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
