You have to consider the Group capacities and the LPAR weights. 1.Within a Group, the Group is capped to the Group capacity. If the 4hra of the Group exceeds its max, the Group will be capped. 2.When LPARs have a demand for CPU, the LPAR weights determine how much the LPAR receives, considering the amount of unused capacity in the machine and the weight of the LPAR.
So, in your example, if the A-LPARs spike, their Group is not capped, the B-LPARs are not capped either, so you just have 7 LPARs (where are LPARs 4 and 5) competing for the machine capacity, without Group interference, and PR/SM will distribute the CPU according to the LPAR weights. HTH, Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Veryl Ellis > Sent: 29 March, 2017 17:51 > To: [email protected] > Subject: 4HRA With Defined Capacity & Group Capacity > > This is for those out there who have an understanding on the subject and > how it might apply to a non-production service provider environment. > > Scenario Example > > 2964-605 processor > Rated MSU = 577 > 5 CPs are shared among all LPARs > > Customer-A has LPARs 1,2 & 3 Grouped with a MSU cap of 300 (contracted > MIPS converted to MSUs). > Customer-B has LPARs 6,7,8 & 9 Grouped with a MSU cap of 250 (contracted > MIPS converted to MSUs). > > > Is the 4HRA at the CEC level or the LPAR level? > > If the Customer-A LPAR Group spikes above its Group MSU cap while the > Customer-B LPAR Group is in low usage, what happens when the Customer-B > LPAR Group now needs resources? > Does it have to wait on Customer-A’s 4HRA to complete or does it get > what it needs by taking back the overage given to the Customer-A LPAR > Group? > > These may be juvenile questions, but I’m not a capacity planner and I’m > trying to gain some understanding of how this works by reading manuals. > > Any insight will be appreciated. > > Thanks, > > S. Veryl Ellis > > ---------------------------------------------------------------------- > 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
