HP Instant Capacity Release Notes for Versions 8.x

When icapstatus reports a value of 0 for Intended Active, it means that all configured cores
will be activated. This is normal for a complex which does not include any Instant Capacity
components. If cores are deactivated on one partition of such a system (as described for the new
feature “demo mode”), the Intended Active and Actual Active reported for the partition change
to reflect the deactivations. (Intended Active and Actual Active will be numbers representing
the total configured cores minus the number deactivated.) Other partitions not in demo mode
continue to report a value of 0 for Intended Active (meaning all cores should be activated), but
a value for Actual Active which is the total of the number of configured cores.
In addition, when demo mode is completed, and the appropriate activations are done to bring
the partition back to the original number of activated cores, the Intended Active does not return
to the initial value of 0. It remains at the value equal to the total number of configured cores.
This means that if subsequent processor cores are added to the system (which had once been in
demo mode), icapmodify operations will be required in order to activate the newly added
cores. This would not have been required if the system had never used demo mode.
The output of icapstatus reflects the results of any GiCAP group operations: the borrowing
or loaning of component usage rights or the transfer of temporary capacity. The output does not
take into account any component usage rights or temporary capacity that may be available on
other GiCAP group members. Thus, icapstatus on group member A may report that there
are no additional cores that may be activated with current usage rights even though there is an
inactive core on group member A and an available core usage right on group member B. Use
the icapmanage command on the Group Manager system to get more complete information
about available group resources.
When a group member is using temporary capacity and core usage rights are made available on
another group member through the use of icapmodify -d <n>, there may be a delay between
the time the core usage rights are made available and the time the core usage rights move to the
group member using temporary capacity. This also means that there may be a delay before the
final result is reflected in the output of icapstatus for each group member involved in the
transfer of the core usage rights.
Filename Changes
Various additional filename changes were also made. The Instant Capacity daemon name changed
to icapd (formerly icodd). The Instant Capacity log file changed to /var/adm/icap.log
(formerly icod.log). A file called /var/adm/icod.log is symbolically linked to the new log
file so that you may still reference the previous filename.
The documentation files changed to /usr/share/doc/icapRelNotes.pdf and
/usr/share/doc/icapUserGuide.pdf. A new file, /usr/share/doc/icapOverview.htm
can be used to link to the most up-to-date documentation files on the HP web site. In particular,
if you do not have a pdf reader, this allows you to link to the html versions of the documents on
the web site.
Configuration Change Notification
The e-mail notification that is sent when configuration changes are made (and if notification is
enabled) was enhanced to include more information. The e-mail includes a new line item noting
whether the requested operation was deferred or not.
Miscellaneous Fixes
• A problem with the icapstatus (icod_stat) display in the integrated virtual partition
environment (vPars A.04 or greater) was fixed with this release. Previously, icapstatus
would sometimes reverse the values associated with “Licensed processors that can be
assigned” and “Processors that can be assigned if licensed”. This happened only when the
number of processors assigned to the virtual partition was lower than the “intended active”
number of processors for the partition. Note that with versions 8.x, these two display values
Summary of New Features and Changes 23