IIRC, 'execution velocity' is rooted in the ratio of the time spent waiting for the CPU and the time actually using the CPU. The 'mean time to wait' metric. But I think the CPU critical attribute pretty much negates the effects of velocity. I seem to recall a display or report somewhere that reported the actual running velocity. Might be an interesting bit of information.
Any task needs three resources: the CPU, main storage, and I/O. Each of the resources have two timers: waiting and using. The wall clock run time is basically the sum of those six timers. There are some top level metrics that can guide our search. For example, if the average CPU is below 100% and the average demand page in rate is zero then we can direct our attention to the I/O subsystem. I think RMF III does a fair job of breaking down what resources a job is using and how long it is waiting for each. When you say: "Overall we are pushing through more work, but our critical path window ran longer." Makes me want to look for a DASD 'hot spot' or some such file contention. HTH and good luck -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of gsg Sent: Tuesday, March 20, 2012 11:05 AM To: [email protected] Subject: Execution Velocity Can someone please explain execution velocity for Workload Manager, I'd really appreciate it. We do not seem to be getting the results we thought we would. On this particular LPAR, we we're running with 3CPs, but when we activated a 4th CP, our critical path ran longer. Overall we are pushing through more work, but our critical path window ran longer. We are stumped on why. We're starting to look at RMF data, but thought I would throw it out to see if anyone has any clues. We have a HOTBATCH service class defined with IMP=1, Execution Velocity of 90, with the CPU Critical flag turned on. This service class has a jobclass assigned to it. At any given time during our batch window, there may be up to two of three of these jobs running. Other service class we have define for batch are PRDBATHI(IMP=2, Execution Velocity of 30) and PRDBATLO(Discretionary). Thanks ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
