Enhance Capacity Provisioning Manager to better handle 10 second and lower RMF Intervals

CPOSERV is unable to complete its observation cycle while monitoring multiple systems/sysplexes where some of those sysplex are set with an RMFIII MINTIME of 10 seconds or lower.

There is a business requirement to have the RMF MINTIME set at 10 seconds and was set based on a recommendation from IBM. CPOSERVE not being able to complete its observation cycle means that it will not take action if/when those systems are in need of capacity adjustments.

We would like CPOSERV to be enhanced to allow the user to specify the range of RMF data being retrieved or at least the observation length CPOSERV is using. Ideally it would be set somewhere like in the Domain Config so it could be set for each individual system/sysplex. The default could be MINTIME as it is now so it doesn't impact any customers by accident.

The RMFGAT API has the ability to specify a range on queries sent to it. This would allow us to have 10 second intervals but allow CPOSERV to request something like a 20 or 60 second metric instead, effectively CPOSERV would be requesting a 20 or 60 second average of the 10 second intervals. Alternatively setting the observation length would allow us to keep our 10 second RMF intervals but allow CPOSERV to be set to something like 12 or 15 seconds giving it time to get through its cycle.

Specifying the API range would be the more ideal implementation. Only being able to set the observation length could, depending on CPOSERVs implementation of it, end up with only grabbing a single 10 second interval every say 60 seconds leaving 50 seconds of unobserved intervals.


We also request that the CPOSERV documentation be updated to include notes on how the RMF MINTIME and the number of systems being monitored can impact CPOSERVs ability to complete its observation cycle and what the ramifications are of not completing that cycle i.e. autonomic capacity adjustments not being performed.