HP-UX 11i Version 2 June 2006 Release Notes
Table Of Contents
- HP-UX 11i Version 2 June 2006 Release Notes
- Legal Notices
- Publication History
- Typographic Conventions
- 1 Overview of the Release Notes
- 2 Introduction to HP-UX 11i Version 2
- 3 What is New at a Glance
- What is in This Chapter?
- What is New in the June 2006 Release?
- What is New in the March 2006 Release?
- What is New in the December 2005 Release?
- What is New in the May 2005 Release?
- What is New in the September 2004 Release?
- What is New in the March 2004 Release?
- What is New in the Initial (October 2003) HP-UX 11i v2 Release?
- 4 Hardware-Specific Information
- What is in This Chapter?
- Hardware Enablement Patch Bundle for HP-UX 11i v2
- HP Instant Support Enterprise Edition
- Networking and Mass Storage Drivers
- Always-Installed Networking Drivers
- Selectable Networking Drivers
- Always-Installed Mass Storage Drivers
- Supported Systems
- Finding Firmware Information
- Utility Pricing Solutions
- 5 General System Administration
- What is in This Chapter?
- Feature Enablement Patch Bundle (FEATURE11i)
- HP Integrity Virtual Machines Provider
- HP Integrity VM Support Library
- HP Partitioning
- HP Serviceguard WBEM Providers
- HP System Management Homepage
- HP WBEM Services for HP-UX
- HP-UX Kernel Configuration
- Ignite-UX
- Online Diagnostics
- Quality Pack Patch Bundle
- Software Distributor
- Update-UX
- Utilization Provider
- 6 Disk and File Management
- 7 Internet and Networking
- 8 Security
- 9 Commands and System Calls
- 10 Libraries and Programming
- 11 Internationalization
- 12 Other Functionality

Hardware-Specific Information
Utility Pricing Solutions
Chapter 4
101
iCAP components on the backup servers. Without GiCAP, the only way to provide this
failover scenario is to provision each server with an adequate amount of temporary
capacity in case of potential failures.
A similar scenario exists for load balancing. Rather than using temporary capacity
whenever a server is overloaded (peak profiles for all workloads on a server), usage
rights (RTUs) can be transferred from other servers in the GiCAP group that have extra
capacity, enabling new activations for the overloaded system.
Compatibility
Previous command names such as icod_stat, icod_modify, and icod_notify still
work, but are now just filenames symbolically linked to the new command names.
References to the old command names will see the new terminology as detailed above.
You may also reference the older manpages such as man icod, but these references give
the exact same output as the new man commands. All manpage references use the new
terminology as detailed above.
A filename called /var/adm/icod.log is symbolically linked to the new log filename
/var/adm/icap.log so that you may still reference the previous filename.
Performance
While the size of GiCAP groups is not specifically restricted, performance of
group-related functions is affected by the number of group members and the number of
partitions for each member server, as well as the types of hardware involved.
Documentation
For further information, see the following:
•Manpages:
— icap (5)
— icapmanage (1M)
— icapmodify (1M)
— icapnotify (1M)
— icapstatus (1M)
•Web Sites:
— HP Software Depot: http://hp.com/go/softwaredepot
— HP Technical Documentation: http://docs.hp.com
•Documents:
For details on the HP Instant Capacity software product, see the Instant Capacity
User’s Guide and Release Notes located on the HP Web site http://docs.hp.com
(under Network and Systems Management -> Utility Pricing Solutions)
Obsolescence
The previous commands of icod_stat, icod_notify, and icod_modify are now
deprecated; users can still invoke these commands but they are symbolically linked to
the new commands of icodstatus, icodnotify, and icodmodify, respectively.
The icodd daemon has been replaced by the icapd daemon.