Using HP Integrity Essentials Global Workload Manager 3.0.1 with Global Instant Capacity 8.02.01

5
Operations on GiCAP Group Members Outside an SRD
You are still able to manually execute icapmodify operations in any complex in a GiCAP group,
regardless of whether any of the partitions are in an SRD. However, as gWLM 3.0.1 always tries to
maintain an SRD at the size it had when it was created, the results are not likely to be permanent
within the SRD. Because these operations are not permanent and may cause temporary resource
management errors, you should avoid using icapmodify in a deployed SRD.
Similarly, it was previously described how usage rights can be inadvertently taken from a gWLM
managed system. In such a case, gWLM would try to restore resources by activating usage rights or
TiCAP. If gWLM is unable to automatically restore the resources, it generates error messages to report
failed attempts to activate resources. In this case, you would then manually de-activate cores on a
GiCAP group member outside an SRD. The usage rights would then be available for transfer into the
SRD.
TiCAP Consumption Indicators
gWLM has indicators providing information on the consumption of TiCAP in your SRDs. These
indicators show which gWLM managed workloads are eligible to consume TiCAP and which are
actually consuming TiCAP. These indicators are only approximate though. (The indicators themselves
are updated every resource allocation interval; however, the actual TiCAP consumption is typically
updated less frequently.) In a GiCAP environment, these indicators are likely to be less accurate.
(These inaccuracies occur because the indicators are specific to the managed SRDs. They are not
aware of changes in the usage rights made at the complex level through GiCAP operations. In
addition, the TiCAP consumption depends on the state of all of the complexes in the GiCAP group.)