Al, Thanks for the reply and the confirmation that there GCL and IRD don't cooperate when the really should. We have sufficient CPU capacity in the boxes, so in a non softcapped situation, IRD has nothing to do, while in a softcapped situation it does nothing.
The solution I am thinking of is splitting the Capacity Group, but this results in less optimal (i.e. higher) MSU consumption, so higher monthly bills, which could have been prevented by IRD, but IRD is not allowed to do so. Weird situation... Another point: in a Capacity Goup, WLM distrubutes resourses over the LPARs, based on the needs of the LPARs. If the LPARs are softcapped, PR/SM can only apply the Weights, but WLM will ensure its caculated MSUs go to each LPAR, by either applying 'phantom load' or 'pattern capping'. I suppose this moves resources from LPARs that need less than their (weight)share to LPARs that need more than their share. But I suppose this will not move resources from lo-prio batch in LPAR1 to hi-prio CICS in LPAR2. This is what IRD does and what I need. Kees. "Al Sherkow" <[email protected]> wrote in message news:<[email protected]>... > Kees -- > > IRD Weight Management is used at some of my client sites. I think it is very useful. For a review that capabilities this feature enables to WLM to shift "weight" between LPARs in the same SYSPLEX on a single CPC based on importance. For example if importance=3 work in LPAR A is exceeding it's goal, and importance=2 work in LPAR B is missing it's goal then WLM will move some "weight" from LPAR A to LPAR B to help out the importance=2 work. > > Seems very useful to me, but I'm a consulting and I'm not running a data center. > > On to LPAR Group Capacity Limit. Another nice feature, requested by customers for a long time and introduced with z/OS 1.8. LPAR GCL is also "managed" by WLM. This capability manages the 4 hour rolling average of a group of LPARs to not exceed a customer set limit. This capability uses the LPAR's weight settings as the indication of how the LPARs should participate in the group. > > However as Kees wrote in the original post: > > The docs mention "As WLM is responsible for > both WLM LPAR Weight Management and > soft-capping, it will be aware when an LP is > being soft-capped, and will not make any > further adjustments to the weight of the LP > until the soft-cap is removed." > > This is a problem, it is when the GCL is being enforced that a site would most like IRD LPAR Weight Management to kick in and start redistributing the limited CPU resource based on importance of the workloads rather than the initially set weights of the LPARs. > > IBM does not want to fix this issue. I think it has been entered as a "SHARE requirement". > > So some sites have decided not to use GCL because they view "IRD LPAR Weight Management" as more useful. Other sites have made the decision the other way. Still other sites are using both while understanding this limitation. > > Al Sherkow, I/S Management Strategies, Ltd. > Consulting Expertise on Capacity Planning, Performance Tuning, > WLC, LPARs, IRD and LCS Software > Seminars on IBM SW Pricing, LPARs, and IRD > Voice: +1 414 332-3062 > Web: www.sherkow.com > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** 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
