A processor value unit (PVU) is a unit of measure that is assigned to each processor core for software licensing purposes. For each DB2® database product, you need to acquire the appropriate number of processor value units for the level or tier of all processor cores activated and ready for use on which the software is deployed.
On 25 July 2006, IBM announced a processor pricing strategy based on processor value units. All existing part numbers have been converted to the new PVU-based part numbers. A single processor-based entitlement has been converted to 100 PVUs.
For example, a single System p® processor with a single core requires 100 value units. An Intel or AMD dual-core processor also requires 100 value units. This is in keeping with existing announcements on multicore pricing. To determine the total cost of deploying an individual software program, you multiply the program's price per PVU by the total number of PVUs required.
PVU pricing is explained in detail on the Passport Advantage® home page. Announcement letters, value unit conversion tables, a terminology glossary, presentations, and other external resources are available online. Refer to http://www.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_customers.html. There is also a PVU calculator to help you calculate the total number of PVU in your environment: http://www.ibm.com/software/howtobuy/passportadvantage/valueunitcalculator/vucalc.wss.
Processor value units enable subcapacity licensing at the processor core, which allows you to cost-effectively use logically partitioned hardware. Read the full details of the IBM subcapacity strategy at www.ibm.com/software/lotus/passportadvantage/subcaplicensing.html.
On 7 April 2009, IBM announced enhancements to subcapacity licensing for PVU-based products available in Passport Advantage. DB2 database products that are offered under the PVU charge metric are available for subcapacity licensing. Refer to www.ibm.com/software/lotus/passportadvantage/subcapacity_licensing_announcement_summary.html.
Ensure that the machine on which the DB2 database product resides does not exceed it's licensed PVU limits.