HP Instant Capacity Version 10.x Release Notes (5900-1580, March 2011)

2 Major Changes, New Features, and Requirements of
Instant Capacity Version 10.x
This chapter covers the following topics:
• “Program Requirements” (page 11)
• “Summary of New Features and Changes” (page 11)
• “Known Problems” (page 19)
• “Software Requirements” (page 23)
• “Usage Rights Requirement” (page 26)
• “GiCAP Requirements” (page 26)
The following sections provide only a summary of the Instant Capacity Version 10.x major changes
and features. For in-depth information about a specific topic, see the HP Instant Capacity user’s
guide for Version 10.x, which is available on the BSC website:
www.hp.com/go/hp-icap-docs
Program Requirements
To participate in the Instant Capacity version 10.x program, you must comply with the following
conditions of the HP Utility Pricing Solutions program:
• Maintain the HP Instant Capacity software on each HP-UX or OpenVMS partition in the system.
The Instant Capacity software is a nonintrusive, low-overhead software module that resides
on the partition.
• Migrate to later Instant Capacity software versions as they become available.
For specifics about your individual program requirements, see the Utility Pricing Solutions contract
from HP or your authorized channel partner.
IMPORTANT: Participants in the Utility Pricing Solutions program who do not meet these
requirements might be in breach of contract. This can result in unnecessary expense for both the
program participant and HP.
Summary of New Features and Changes
This section summarizes the new features and changes of the Instant Capacity product.
Changes in version 10.00.01 from 10.00 (HP-UX 11i v2 only)
GiCAP member seizure fix
The problem has been fixed where seizure from a member in a GiCAP group followed by a restore
operation resulted in a corrupted GiCAP database.
GiCAP provider fix
A memory leak in the GiCAP provider has been fixed. This problem occurred while transferring
the GiCAP database from the active GiCAP manager to the standby GiCAP manager.
TiCAP debit fix
The problem has been fixed where the temporary capacity balance was erroneously debited in a
GiCAP group. The problem occurred only under unusual timing circumstances.
Program Requirements 11