HP Instant Capacity release notes for Version 10.x (March 2011)

2 Major Changes, New Features, and Requirements of
Instant Capacity Version 10.x
This chapter covers the following topics:
• “Program Requirements” (page 15)
• “Summary of New Features and Changes” (page 15)
• “Known Problems” (page 22)
• “Software Requirements” (page 27)
• “Usage Rights Requirement” (page 29)
• “GiCAP Requirements” (page 30)
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.03 from Version 10.02 (HP-UX)
TiCAP warning period fix for HP Integrity Superdome 2
A problem was fixed where the temporary capacity warning period did not default to 15 days
after installing iCAP software on HP Integrity Superdome 2.
GiCAP member seizure fix
A problem was 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 was fixed. This problem occurred for specific configurations
while transferring the GiCAP database from the active GiCAP manager to the standby GiCAP
manager.
Program Requirements 15