You probably have discretionary defined and the service class this job is running in is over achieving, has a velocity of less than 30 or a response time goal over 1 min. and is itself not resource capped and ends up giving resources to discretionary but keeps the PI of the giver between 0.71 and 0.81. This is in SG24-6472-03 Systems Programmers Guide to WLM.
--- On Tue, 9/22/09, McKown, John <[email protected]> wrote: From: McKown, John <[email protected]> Subject: WLM question - delayed due to CPUCAPPED To: [email protected] Date: Tuesday, September 22, 2009, 5:00 PM There is a field in Mainview for z/OS which shows me that a slow running job was delayed to "CPUCAP". Does anybody really know exactly what that means? We are using Group Capacity to control our software costs. Is this PRSM and WLM working together to cap the LPAR? Or is this just some WLM delay due to another job in the same service class getting all the allowed CPU? This service class in NOT in a Resource Group. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell [email protected] * www.HealthMarkets.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
