Prevent LPAR definitions that would span CPC drawers

When configuring LPAR definitions for a CEC via the HMC, logic should exist to prevent customers from specifying a configuration of zIIPs, CPs, and weight that would result in an LPAR that spans drawers.

Basically, perform the calculations for the entire CEC and do not allow customer to save the information via the Image Activation Profile. If the combination of zIIP and CP engines and weight exceeds a single drawer, reject the request and then report the maximum number of engines/weight that would fit in a single drawer.

The customer would know and understand their limitations and the maximum allowable allocation per LPAR. The customer would correct the Lpar Image Activation Profile with the proper definitions, save, and then activate the image.

This would prevent an LPAR from exceeding the capacity of one drawer which incurs a performance penalty which is significantly higher on the z16 vs prior generations.

Ownership will fall on the customer to make the necessary adjustments such as moving workload within a SYSPLEX or building more LPARs when facing capacity constraints, which is BAU.

IBM does a similar action with Central Storage on the CEC level by ensuring that the customer cannot over allocate storage.

IBM can also consider what you do today for SOFTCAP weights. Maybe you can do something similar to cap the LPAR that will not exceed a single drawer.