SCRT should be changed to honor AbsoluteGroupCapping / AbsoluteCapping setup on the HMC

We've licenced HW TFP. To prohibit to peak into the TFP corridor, we set up AbsoluteGroupCapping on the HMC for a Capacity Group that includes all LPARs on the CEC to limit the number of CPs used.

This was fine for 3 months. Afterwards we recognized from SCRT that the AbsoluteGroupCapping limit was raised and the machine peaked so that we got a bill that wasn't expected.

According to PR/SM Planning Guide, this is well known for SoftCapping and the limits could be raised by 3.6%. This is currently NOT documented for AbsoluteCapping/AbsoluteGroupCapping. Instead, it's documented that the ABSOLUTE capping limits the capacity ABSOLUTELY. According to an HW PMR, this is Works-As-Designed and the algorithm behind is secret and not every detail will be documented. At least, it will be documented that AbsoluteCapping could be raised by 3.6% like for SoftCapping.

So, if this is Works-As-Designed, SCRT have to be changed to honor the AbsoluteCapping/AbsoluteGroupCapping specification, as this is a feature for controlling pricing. For Softcapping, it's already honored that for example the SoftCapping is used if the R4HA would raise the SoftCap limit. The same have to be implemented for AbsoluteCapping regarding the MSU rate in section i5/v9.

There are SMF70 fields available, that specify the limit setup on HMC for AbsoluteCapping. Also, there is e.g. RMF that reports the limit based on the capacity specified on the AbsoluteCapping, so the details are definitly there.