Additional Verifications for some HMC operations.

Normally, Z HMC infrastructure requires password verification when the performed operation is disruptive. For example if you are deactivating a running LPAR, the system warns you well and says that this is a disruptive operation and asks for your password. I believe this verification should also be in place for the following operations:

•  Absolute Capping Definitions in both LPAR Controls and LPAR Group Controls: Someone can easily cause a sysplex-wide outage by applying a wrong cap value on a wrong sysplex-group and this would be quite disruptive. Here, I believe, a password asking verification or an intelligent verification that can check (for example) the LCP numbers of group or the LPAR and if the applied absolute cap value is less than %25 of the total LCP numbers the system can issue additional warnings.
•  The second one is related to the "Managed System Time" application. If I remember it correct the former "System Time" application was asking a last verification screen summarizing the action and comparing before/after situations however the new app is not doing this. As an example when you try to "adjust time" it starts applying the adjustment amount as soon as you click the "Apply" button without asking additional verification. This is not consistent with HMC's restrictive and sure-footed behavior. Additional verifications on the new "Manage System Time" application would make Z more reliable.

Thanks