DCI: Wrong Capping decisions and incorrect R4HA values reported after CG name reuse
search cancel

DCI: Wrong Capping decisions and incorrect R4HA values reported after CG name reuse

book

Article ID: 398664

calendar_today

Updated On:

Products

Dynamic Capacity Intelligence

Issue/Introduction

A Capacity Group name (e.g. CG01) was used for a CPC (e.g. CPC1) and for some LPARs (e.g. LPAR1 and LPAR2) until last week.

Now the old GC definition has been deleted from HMC and the same name (CG01) has been reused for a different CPC (e.g. CPC2) and for other LPARs (e.g. LPAR3 and LPAR4). Dynamic Capacity Intelligence (DCI) policies and definitions have been modified accordingly.

However DCI is now reporting incorrect values for R4HA on the WebUI Status panel and on the main panel of the ISPF Interface. Moreover DCI is taking wrong capping decisions for the LPARs under the CG01 capacity group.

Cause

DCI, as a safety feature, retains the settings for a CG for the whole billing month. But in this way, the last R4HA value for the "old" CG  is summed with the current R4HA value, which can drive to incorrect decisions.

Resolution

When changing the CPC, the GC name must be different, even if the LPARs in the CG are the same. This can occur when installing a new CPC or in a DR situation.

In such cases, define a new CG name and do NOT reuse the old one.