Oh, yes, Uwe! Jan On Thu, Aug 30, 2012 at 8:29 AM, Uwe Oswald <[email protected]>wrote:
> This behaviour is described in the WLM Redbook I believe. I can find the > document if someone is interested to understand the capping mechanism in > more detail. > > -----Ursprüngliche Nachricht----- > Von: IBM Mainframe Discussion List [mailto:[email protected]] Im > Auftrag von Ron Hawkins > Gesendet: Mittwoch, 29. August 2012 18:52 > An: [email protected] > Betreff: Re: WLM Resource Group not working. > > Kees, > > I've just done some trial and error setup for a service unit based > resource group. This one is running about 300 jobs at once. > > We've noticed the behavior when submitting all these jobs after some > inactivity is the work in the resource group will run unconstrained for a > few minutes, and then gradually be throttled back to service unit limit > specified. After approx. ten minutes the resource group cap is working > perfectly. We've tested this for 8-10 hours continuous running. > > The service unit limit we used was arrived at through trial and error. I > noticed the above behavior late in the piece. I have not checked the > accuracy of the SU consumption of the resource group as we arrived at the > PCTCPUBY we needed more out of luck then design, but we stopped toying with > it once we got what we needed. > > Ron > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Vernooij, CP - SPLXM > > Sent: Wednesday, August 29, 2012 6:51 AM > > To: [email protected] > > Subject: [IBM-MAIN] WLM Resource Group not working. > > > > Hello list, > > > > > > > > I implemented a Resource Group to limit the CPU consumption of our > > CICS Devl and Acc systems, but I can't get the RG to do what I want. > > > > > > > > I want to limit the group to 2 MSU, so I gave the RG a max of > > 2000000/3600=555 SU/sec (Option 1, sysplex wide) and started a CPU > > looper > > (iefbr15) in the SC connected to the RG. In Mainview I see that WLM is > > capping the looper, but it is still allowed to consume 2000 SU/sec. > > If I > start a > > second looper, the RG starts consuming even more CPU. > > > > > > > > Why does this not work as I expected and how do I limit the group to > > 555 SU/sec? > > > > > > > > Thanks for your help, > > > > Kees. > > > > > > > > ******************************************************** > > For information, services and offers, please visit our web site: > > http://www.klm.com. This e-mail and any attachment may contain > > confidential and privileged material intended for the addressee only. > > If > you > > are not the addressee, you are notified that no part of the e-mail or > > any attachment may be disclosed, copied or distributed, and that any > > other action related to this e-mail or attachment is strictly > > prohibited, and > may be > > unlawful. If you have received this e-mail by error, please notify the > sender > > immediately by return e-mail, and delete this message. > > > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or > > its employees shall not be liable for the incorrect or incomplete > > transmission > of > > this e-mail or any attachments, nor responsible for any delay in receipt. > > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal > > Dutch > > Airlines) is registered in Amstelveen, The Netherlands, with > > registered number 33014286 > > ******************************************************** > > > > ---------------------------------------------------------------------- > > 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 > > ---------------------------------------------------------------------- > 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
