So what can I tell from below ... is WDCB1112 3.0 just for the P00 ILF?
CPU Load Vector Facility Status or PROC <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.001> TYPE <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.006> %CPU <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.011> %CP <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.017> %EMU <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.021> %WT <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.026> %SYS <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.030> %SP <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.035> %SIC <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.039> %LOGLD <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.044> %VTOT <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.052> %VEMU <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.058> REST <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.065> ded. User <http://192.168.32.130:81/03D5A6B0/70B0/HE.03.070> P00 IFL 3 1 3 97 0 0 92 3 .. .. ... Master P01 IFL 4 0 4 96 0 0 93 4 .. .. ... Alternate P02 IFL 3 0 3 97 0 0 93 3 .. .. ... Alternate P03 IFL 4 0 4 96 0 0 92 4 .. .. ... Alternate Total SSCH/RSCH <http://192.168.32.130:81/03D5A6B0/70B0/HE.09.001> 144/s Page rate <http://192.168.32.130:81/03D5A6B0/70B0/HE.09.030> 323.6/s Priv. instruct. <http://192.168.32.130:81/03D5A6B0/70B0/HE.09.056> 466/s Virtual I/O rate <http://192.168.32.130:81/03D5A6B0/70B0/HE.10.001> 38/s XSTORE paging <http://192.168.32.130:81/03D5A6B0/70B0/HE.10.030> 702.3/s Diagnose instr. <http://192.168.32.130:81/03D5A6B0/70B0/HE.10.056> 76/s Total rel. SHARE <http://192.168.32.130:81/03D5A6B0/70B0/HE.11.001> 5475 Tot. abs SHARE <http://192.168.32.130:81/03D5A6B0/70B0/HE.11.030> 0% Queue Statistics: <http://192.168.32.130:81/03D5A6B0/70B0/HE.13.001> Q0 <http://192.168.32.130:81/03D5A6B0/70B0/HE.13.023> Q1 <http://192.168.32.130:81/03D5A6B0/70B0/HE.13.030> Q2 <http://192.168.32.130:81/03D5A6B0/70B0/HE.13.037> Q3 <http://192.168.32.130:81/03D5A6B0/70B0/HE.13.044> User Status: <http://192.168.32.130:81/03D5A6B0/70B0/HE.13.051> VMDBKs in queue <http://192.168.32.130:81/03D5A6B0/70B0/HE.14.001> 13 14 3 4 # of logged on users <http://192.168.32.130:81/03D5A6B0/70B0/HE.14.051> 53 VMDBKs loading <http://192.168.32.130:81/03D5A6B0/70B0/HE.15.001> 0 0 0 0 # of dialed users <http://192.168.32.130:81/03D5A6B0/70B0/HE.15.051> 0 Eligible VMDBKs <http://192.168.32.130:81/03D5A6B0/70B0/HE.16.001> 0 0 0 # of active users <http://192.168.32.130:81/03D5A6B0/70B0/HE.16.051> 42 El. VMDBKs loading <http://192.168.32.130:81/03D5A6B0/70B0/HE.17.001> 0 0 0 # of in-queue users <http://192.168.32.130:81/03D5A6B0/70B0/HE.17.051> 34 Tot. WS (pages) <http://192.168.32.130:81/03D5A6B0/70B0/HE.18.001> 2016k 139479 314535 199276 % in-Q users in PGWAIT <http://192.168.32.130:81/03D5A6B0/70B0/HE.18.051> 1 Expansion factor <http://192.168.32.130:81/03D5A6B0/70B0/HE.19.001> 0 0 0 % in-Q users in IOWAIT <http://192.168.32.130:81/03D5A6B0/70B0/HE.19.051> 0 85% elapsed time <http://192.168.32.130:81/03D5A6B0/70B0/HE.20.001> 5.328 .666 5.328 31.97 % elig. (resource wait) <http://192.168.32.130:81/03D5A6B0/70B0/HE.20.051> 0 Transactions <http://192.168.32.130:81/03D5A6B0/70B0/HE.22.001> Q-Disp <http://192.168.32.130:81/03D5A6B0/70B0/HE.22.019> trivial <http://192.168.32.130:81/03D5A6B0/70B0/HE.22.029> non-trv <http://192.168.32.130:81/03D5A6B0/70B0/HE.22.039> User Extremes: <http://192.168.32.130:81/03D5A6B0/70B0/HE.22.051> Average users <http://192.168.32.130:81/03D5A6B0/70B0/HE.23.001> 3.7 3.5 6.9 Max. CPU % <http://192.168.32.130:81/03D5A6B0/70B0/HE.23.051> WDCB1112 3.0 Trans. per sec. <http://192.168.32.130:81/03D5A6B0/70B0/HE.24.001> 3.5 14.2 5.3 Max. VECT % <http://192.168.32.130:81/03D5A6B0/70B0/HE.24.051> ........ ..... -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Monday, December 08, 2008 11:28 AM To: [email protected] Subject: Re: vm performance tool kit On 12/8/08 11:15 AM, "Ayer, Paul W" <[EMAIL PROTECTED]> wrote: > User which consumed most CPU during the last measuring > interval, and the percentage of total CPU used (based on > one processor) > Can anyone explain the (based on one processor) part please? Eberhard will probably chime in later, but usually that phrase means 100% = 1 CPU worth of capacity. So, if you see a number > 100%, you're using n/100 CPUs worth of capacity. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
