HP Instant Capacity Version 10.x User Guide (762794-001, March 2014)

Displayed only when the -v option is specified
and only for systems where usage rights were
seized for disaster recovery, if none of the
member partitions could be contacted.
Guidelines for interpretation of usage rights counts
In general, the Instant Capacity software is designed to enforce the concept that a certain number
of resources must remain inactive to stay in compliance with the iCAP contract. For that reason,
many of the display fields for icapstatus and also for icapmanage are negative counts of
usage rights, such as Cores without usage rights and Cells without usage rights.
At the same time, the GiCAP software is intended to allow the transfer of usage rights among
members of the group. So, seizure of usage rights, borrows and loans of usage rights are described
as positive counts of usage rights, such as number of Seized core usage rights and number of
Borrowed core rights. The Group Manager also sometimes holds usage rights during transient
states, so all the Group Manager resources are described as positive counts of core usage rights.
To properly interpret the icapmanage display of usage rights, it is sometimes necessary to total
the usage rights using both positive and negative (subtractive) values. For example, if the group
contains two members, each having three cores without usage rights, then the total for the group
is six cores without usage rights. If rights are seized from one member, for example taking 2 core
usage rights away, then those 2 core usage rights are held by the Group Manager before the 4
are used by another member of the group. During that transitional period, the total for the group
remains 6 cores without usage rights, but the member total for the unreachable member is adjusted
to be 5 cores without usage rights (2 were taken away from the unreachable member) and 3 cores
without usage rights (for the other member). At the same time, the Group Manager holds 2 usage
rights. The total for cores without usage rights is calculated as 6=5+3-2.
In this example, “counts of cores without usage rights” are also adjusted as a result of rights seizure
operations to maintain the contractually required balance of cores without usage rights. Similar
adjustments are made every time a resource (cores, cells, memory) is borrowed from or loaned to
other members of the group. These adjustments are automatically reflected in the icapstatus
output on the member systems; in the case of unreachable members and rights seizure, you might
see the adjustment first in the display from the icapmanage output.
EXTERNAL INFLUENCES
Environment Variables
• LANG determines the locale to use for the locale categories when both LC_ALL and the
corresponding environment variable (beginning with LC_) do not specify a locale. If LANG is
not set or is set to the empty string, a default of C is used (see lang(5)).
• LC_CTYPE determines the interpretation of single- and multiple-byte characters.
• LC_MESSAGES determines the language in which messages are displayed.
If any internationalization variable contains an invalid setting, icapmanage command cannot
behave as if all internationalization variables are set to C (see environ(5)).
International Code setsupport
Single- and multiple-byte character code sets are supported.
RETURN VALUE
icapmanage exits with one of these values:
0 Command succeeded.
>0 Command failed; error message sent to STDERR.
164