NEW!! SubGroup / SuperGroups for LPAR Controls and capping

.Thanks for your recommendation. This function is being reviewed for future application.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Hardware
Product - z Systems Hardware
Component - General/Miscellaneous

For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - z Systems Hardware
Product - z Systems Hardware
Component - LPAR

Had a phone call with Phil Pinto to discuss this requirement (12/2/16). I described how the nature of the nesting of two software capacity groups would involve a lot of new infrastructure across multiple areas (SE/HMC, architecture, LPAR, and z/OS WLM). Ultimately WLM would have most of the heavy lifting and would have to deal with the complexities of debiting/crediting to multiple groups, dealing with changes to the group memberships as well.

We then discussed an alternate proposal to use the hardware group capacity facility to manage the inner (test) group here. The test group would be assigned a hardware group cap using processor units roughly equivalent to the needed MSU value of the test partitions in the sub group. The outer collective group (production and test) would use the software capacity group for the overall software MSU cap of the partitions.

After he discussed the proposal with his colleague, Phil confirmed this would met the objective of the requirement here.

This means the change needed is to have the SE/HMC allow a given logical partition to appear in one named software group as well as one other hardware group. The important thing here is that the membership of these groups has to be different. In the example originally provided, all 5 of the partitions must be members of the software capacity group while the 3 test partitions out of those 5 must also be allowed to be members of a separate hardware capacity group.

Note the infrastructure for this flowing from the SE/HMC to LPAR and then out to WLM in the partitions is already in place to support separate hardware and software groups. The hardware group cap would be completely managed by LPAR. The software group would be managed by WLM in the logical partitions; invoking capping as needed through LPAR.

It was also pointed out that that the ability to change the hardware group capping values needs to be provided remotely. Ultimately via CPM but at least initially though HMC APIs.

I guess this will get closed at some point. Is there really a purpose in submitting these requirements? I do not see any voting. Does this even work? Is it in the Right queue?

IBM::: please pay attention to the customer's requirement.
Does make any sense to have the requirement here exposed for one year???

This RFE reminds me we (PRODUBAN Santander Bank Group) submitted the requirement 65595 in 2012 (in the previous web site, when RFE was not still available), to have more control in the ProcessorLPAR assignment, and it is under consideration three years later... I hope a better future for this one!

Creating a new RFE based on Community RFE #78964 in product z Systems Hardware.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - z Systems Hardware
Product - z Systems Hardware
Component - LPAR
Operating system - IBM z/OS
Source - zBLC

For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - zBLC family
Product - zBLC
Component - zBLC Requirements
Operating system - IBM z/OS
Source - None