HP Instant Capacity User's Guide for Versions 8.x

At the same time, the GiCAP software is concerned with the ability to transfer 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 core usage rights seized” and “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.
In order 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 with 3 cores without usage rights, then the total for the
group is 6 cores without usage rights. But if a rights seizure is performed on one member, taking
(for example) 2 core usage rights away from one member, then before the usage rights are used
by another member of the group, those 2 core usage rights are held by the Group Manager.
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.
From this example, you can also see that “counts of cores without usage rights” are adjusted due
to rights seizure operations in order to maintain the contractually required balance of cores
without usage rights. Similar adjustments are made every time a resource (cores, cells, memory)
is borrowed 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, the adjustment may first be seen in the display from icapmanage.
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 multi-byte characters.
LC_MESSAGES determines the language in which messages are displayed.
If any internationalization variable contains an invalid setting, icapmanage behaves as if
all internationalization variables are set to “C” (see environ(5)).
International Code Set Support
Single- and multi-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.
FILES
/var/adm/GiCAP.log
Log file for GiCAP operations and messages.
/etc/opt/iCAP/GiCAP.rules
Encrypted file containing grouping rules used by
the Group Manager.
/etc/opt/iCAP/GiCAP_db
Encrypted file containing information about
Sharing Rights and information about each group
managed by the Group Manager.
/etc/opt/iCAP/GiCAP_keygen
Script file to configure secure communication
between the Group Manager and members of a
group. Needed only if the HP-UX Secure Shell
152