This measurement is based on system states which are continuously collected. The system states describe when a work request uses a system resource and when it must wait for it because it is used by other work. The latter is named a delay state. The quotient of all using states to all productive states (using and delay states) multiplied by 100 is the execution velocity.
http://en.wikipedia.org/wiki/Workload_Manager --Phil Sevetson -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Staller, Allan Sent: Tuesday, March 20, 2012 12:15 PM To: [email protected] Subject: Re: Execution Velocity Try here: http://www-03.ibm.com/systems/resources/servers_eserver_zseries_zos_wlm_ pdf_velocity_pdf_velocity.pdf <snip> 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). </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
