IBM

Decoding IBM PVU Licensing

IBM PVU (Processor Value Unit) licensing works as follows:

  • Processor-Based Measurement: PVUs are assigned based on the type and model of the server’s processor cores.
  • Core Count Impact: Licensing cost is determined by the number of cores and their respective PVU value.
  • Sub-Capacity Option: In virtual environments, sub-capacity licensing allows for licensing based on utilized capacity, not total.

How IBM PVU Licensing Works

How IBM PVU Licensing Works

PVU licensing is based on the details of your server’s processor. Each processor core is assigned a specific PVU value, which varies depending on the processor’s type and model.

Processor Technology and Core Count: The number of PVUs required for licensing depends on the processor’s technology and the number of cores it has. Different processors have different PVU values based on their performance characteristics.

PVU Per Core Table: IBM provides a PVU per core table that lists the specific PVU value for each processor core type. To calculate the total PVUs needed for a server, you simply multiply the number of cores by the PVU value assigned to those cores according to this table.

This table is essential for determining how many PVUs you need to license your server properly.

IBM PVU Table (Summary)

Intel x86 Processors

  • Single-core: 50 PVUs per core
  • Dual-core: 50 PVUs per core
  • Quad-core: 70 PVUs per core

Intel Xeon Processors

  • Single-core: 50 PVUs per core
  • Dual-core: 50 PVUs per core
  • Quad-core: 70 PVUs per core
  • Hexa-core (6 cores): 70 PVUs per core
  • Octa-core (8 cores): 70 PVUs per core
  • Deca-core (10 cores and above): 70 PVUs per core

AMD Opteron Processors

  • Single-core: 50 PVUs per core
  • Dual-core: 50 PVUs per core
  • Quad-core: 75 PVUs per core
  • Hexa-core (6 cores): 75 PVUs per core
  • Octa-core (8 cores): 75 PVUs per core
  • Deca-core (10 cores and above): 75 PVUs per core

IBM Power Processors

  • POWER6 and earlier: 120 PVUs per core
  • POWER7: 70 PVUs per core
  • POWER8 and POWER9: 100 PVUs per core

IBM System z (Mainframe) Processors

  • z10 EC: 120 PVUs per core
  • z10 BC: 100 PVUs per core
  • z196 and z114: 120 PVUs per core
  • zEC12 and zBC12: 120 PVUs per core
  • z13 and later: 120 PVUs per core

Oracle SPARC Processors

  • SPARC T3 and earlier: 100 PVUs per core
  • SPARC T4 and later: 120 PVUs per core

Fujitsu SPARC Processors

  • SPARC64 VI and earlier: 100 PVUs per core
  • SPARC64 VII and later: 120 PVUs per core

Important Notes:

  1. PVU values can vary: The PVU values assigned to processor cores can vary depending on the specific model and configuration. Always refer to the official IBM PVU Table for precise values.
  2. Virtual Environments: In virtualized environments, PVU licensing is typically based on the virtual cores allocated to the IBM software rather than the physical cores.
  3. Sub-capacity Licensing: For environments using sub-capacity licensing, organizations must use the IBM License Metric Tool (ILMT) to track and report processor usage accurately.

Example Calculation:

Suppose you have a server with an Intel Xeon processor with eight cores, each with a PVU value of 70.

  • Total PVUs = Number of cores * PVU per core
  • Total PVUs = 8 cores * 70 PVUs per core = 560 PVUs

This total PVU count (560 PVUs) would determine the licensing costs for the IBM software installed on this server.

Processor Cores in PVU Licensing

Processor Cores in PVU Licensing

Core-Based Licensing: PVUs are assigned to each processor core, not the entire processor. For example, if you have a dual-core processor, PVUs are calculated separately for each core, meaning both cores will have PVUs assigned.

Virtualization and Sub-Capacity Licensing: In virtualized environments, IBM allows licensing based on the specific cores used by virtual machines (VMs). This “sub-capacity” approach licenses only the portion of the physical server’s cores that the VM utilizes. Accurate tracking with tools like the IBM License Metric Tool (ILMT) is essential to ensure compliance.

Key Takeaway: Understanding PVU licensing involves understanding how processor cores are licensed individually and how virtualization can impact licensing costs. Properly managing these factors is crucial for staying compliant and optimizing costs in IBM’s licensing framework.

Resource Value Unit (RVU) vs. PVU

When licensing IBM software, understanding the differences between Resource Value Unit (RVU) and Processor Value Unit (PVU) metrics is crucial for effective license management and cost optimization.

Both metrics determine licensing costs based on the hardware resources consumed, but they apply to different contexts and usage scenarios.

Here’s a detailed comparison of RVU and PVU.

Processor Value Unit (PVU)

Overview

  • PVU licensing is based on the processing power of the servers where the IBM software is installed. It measures the number of processor cores used and assigns a value based on the type and number of processors.
  • IBM defines PVU values for different processor technologies, which can vary between vendors and processor generations.

Calculation

  • PVU is calculated by multiplying the number of processor cores by the PVU value assigned to each core.
  • For example, if a server has four processors, each with eight cores, and the PVU value per core is 100, the total PVU count would be four processors x 8 cores x 100 PVUs = 3200 PVUs.

Use Cases

  • PVU licensing is ideal for traditional on-premises environments where software usage is tied to the hardware’s physical or virtual processors.
  • Commonly used for IBM middleware products such as WebSphere Application Server, IBM DB2, and IBM Cognos.

Advantages

  • Scales with processing power allow organizations to align licensing costs with the computing resources used.
  • Provides flexibility for deploying software across different hardware configurations.

Disadvantages

  • Complexity in calculating PVU values due to varying processor technologies and core counts.
  • Requires detailed tracking and monitoring of processor usage to ensure compliance.

Resource Value Unit (RVU)

Overview

  • RVU licensing is based on utilizing specific resources, such as storage capacity, number of users, or data throughput, rather than the processing power of the servers.
  • Each RVU is a unit of measure representing the resource’s value.

Calculation

  • RVU is calculated based on the specific resource being measured. For example, storage capacity might be measured in terabytes, while user-based metrics might count the number of active users.
  • The RVU count is determined by multiplying the resource usage by the RVU value assigned to that resource.

Use Cases

  • RVU licensing is ideal for environments where the software’s value is more closely tied to resource usage than processing power.
  • Commonly used for IBM storage products, user-based software, and network throughput applications.

IBM Products Licensed Under the Processor Value Unit (PVU) License Model

IBM Products Licensed Under the Processor Value Unit

IBM products licensed under the Processor Value Unit (PVU) model include various software offerings, particularly those deployed in server environments where capacity-based licensing is appropriate.

Below is a list of some key IBM products that are commonly licensed under the PVU model:

IBM Middleware and Application Servers

  • IBM WebSphere Application Server
  • IBM WebSphere MQ
  • IBM WebSphere Portal
  • IBM WebSphere Commerce
  • IBM WebSphere Message Broker

IBM Database and Data Management

  • IBM Db2 (various editions including Db2 Advanced Enterprise Server Edition, Db2 Standard Edition)
  • IBM Informix
  • IBM Db2 Connect

IBM Analytics and Business Intelligence

  • IBM Cognos Analytics
  • IBM SPSS Statistics
  • IBM SPSS Modeler
  • IBM InfoSphere DataStage
  • IBM InfoSphere Information Server

IBM Integration and API Management

  • IBM API Connect
  • IBM App Connect Enterprise
  • IBM DataPower Gateway
  • IBM Integration Bus

IBM DevOps and Software Development

  • IBM Rational Team Concert
  • IBM Rational ClearCase
  • IBM Rational DOORS
  • IBM Rational Application Developer

IBM Cloud and Virtualization

  • IBM Cloud Private
  • IBM Cloud Pak for Applications
  • IBM Cloud Pak for Data
  • IBM Cloud Pak for Integration

IBM Security

  • IBM Security QRadar SIEM
  • IBM Security Identity Governance and Intelligence
  • IBM Guardium Data Protection
  • IBM Security Access Manager

IBM Systems Management and Monitoring

  • IBM Tivoli Monitoring
  • IBM Tivoli Netcool/OMNIbus
  • IBM Tivoli Business Service Manager

IBM Artificial Intelligence and Machine Learning

  • IBM Watson Explorer
  • IBM Watson Knowledge Studio
  • IBM Watson Machine Learning

This list includes some of the major IBM products that utilize the PVU licensing model, but it is not exhaustive. IBM regularly updates its product offerings and licensing models, so it’s important to refer to IBM’s official documentation or consult with an IBM licensing specialist for the most up-to-date information on specific products and their licensing requirements.

PVU Licensing in Virtualized Environments

PVU Licensing in Virtualized Environments

In virtualized environments, PVU licensing requires careful management to ensure compliance:

  • Sub-Capacity Licensing: IBM allows you to license only the processor cores allocated to virtual machines (VMs) running IBM software rather than the entire physical server. This can significantly reduce licensing costs.
  • IBM License Metric Tool (ILMT): To use Sub-Capacity licensing, you must deploy and configure ILMT. This tool tracks the usage of processor cores in virtualized environments and ensures accurate reporting.
  • Compliance: Regularly monitor and report usage through ILMT to maintain compliance, especially when resources are dynamically allocated across VMs.

Sub-Capacity licensing in virtualized environments offers cost savings but requires strict adherence to IBM’s tracking and reporting requirements.

Understanding these differences and the application of PVU in various contexts is key to effective software cost management and compliance.

IBM PVU Licensing Calculation Examples

IBM PVU Licensing Calculation Examples

IBM’s PVU (Processor Value Unit) Licensing model determines software costs based on the processing capacity of the hardware on which the software runs.

This approach allows organizations to align licensing expenses with the processing power required for their workloads.

Here’s an in-depth look at how PVU licensing operates:

  1. Processor Value Units (PVUs): PVUs are a metric that IBM uses to quantify the processing capacity of a given hardware environment. Each processor core is assigned a specific number of PVUs based on the type and model of the processor.
  2. Hardware Metrics: PVUs are calculated based on the number of processor cores and the processor type. IBM provides a PVU table that lists the PVU values assigned to different processors.
  3. Licensing Terms: Each IBM software product has specific PVU licensing terms that outline the number of PVUs required per processor core. These terms help calculate the total PVUs needed to license the software on a particular hardware configuration.

Example Calculations

Example 1: Single Server with Quad-Core Processors

Imagine using an IBM software product that requires 50 PVUs per processor core. You have a server with four quad-core processors (16 cores in total). The calculation would be as follows:

  1. Determine PVUs per Core: 50 PVUs per core
  2. Calculate Total PVUs: 16 cores * 50 PVUs per core = 800 PVUs

In this example, you must license 800 PVUs for the IBM software product to run on your server with 16 cores.

Example 2: Dual-Processor Server

Suppose you have a server with two processors, each with six cores, and the IBM software product requires 70 PVUs per core. The calculation would be:

  1. Determine PVUs per Core: 70 PVUs per core
  2. Calculate Total Cores: 2 processors * 6 cores per processor = 12 cores
  3. Calculate Total PVUs: 12 cores * 70 PVUs per core = 840 PVUs

For this scenario, you would need to license 840 PVUs for the IBM software product to cover the dual-processor server with 12 cores.

Example 3: High-Performance Server

Consider a high-performance server with four processors, each having eight cores, and the IBM software product requires 100 PVUs per core. The calculation would be:

  1. Determine PVUs per Core: 100 PVUs per core
  2. Calculate Total Cores: 4 processors * 8 cores per processor = 32 cores
  3. Calculate Total PVUs: 32 cores * 100 PVUs per core = 3200 PVUs

In this high-performance setup, you must license 3200 PVUs for the IBM software product to run on the server with 32 cores.

FAQs

What is IBM PVU Licensing?
IBM PVU Licensing is a model where software costs are based on the processing capacity of the hardware, measured in Processor Value Units (PVUs). Each processor core is assigned a specific number of PVUs based on its type and model.

How are PVUs calculated?
PVUs are calculated by multiplying the number of processor cores by the PVU value assigned to each core. The PVU value depends on the processor type and model, as detailed in IBM’s PVU table.

Why does IBM use PVU Licensing?
IBM uses PVU Licensing to align software costs with the actual processing power utilized by the software, making it more adaptable to various hardware configurations and workloads.

How do I find the PVU value for my processor?
The PVU value for your processor can be found in IBM’s official PVU table, which lists the PVU values for different processor types and models and is available on IBM’s website.

Can you give an example of calculating PVUs for a server?
If you have a server with four quad-core processors (16 cores total) and the PVU value is 50 PVUs per core, the total PVUs would be 16 cores * 50 PVUs per core = 800 PVUs.

What factors influence the number of PVUs required?
The number of PVUs required is influenced by the number of processor cores and the PVU value assigned to each core. The type and model of the processor determine the PVU value.

Is PVU Licensing suitable for virtual environments?
Yes, PVU Licensing can be applied to virtual environments. IBM provides guidelines on calculating PVUs for virtualized resources to ensure accurate licensing.

How can I monitor my PVU usage?
IBM provides tools for monitoring PVU usage. These tools help track processor utilization and ensure you stay within your licensed limits.

What should I do if my PVU usage increases?
If your PVU usage increases, you may need to purchase additional licenses. Regularly reviewing your usage and adjusting your licensing can help manage costs.

How does IBM enforce PVU Licensing compliance?
IBM enforces PVU Licensing compliance through regular audits. Organizations must provide accurate usage reports and may face penalties if found non-compliant.

Are there tools available to assist with PVU calculations?
Yes, IBM offers tools and calculators to help determine the number of PVUs required for your specific hardware configuration, simplifying the licensing process. Also, pay attention to public cloud calculations.

Can I combine PVU Licensing with other licensing models?
In some cases, PVU Licensing can be combined with other licensing models to better suit your organization’s needs. Consulting with an IBM licensing expert can help determine the best approach.

What happens if my hardware configuration changes?
If your hardware configuration changes, you should recalculate your PVU requirements based on the new configuration to ensure you comply with IBM’s licensing terms.

Find out more about our IBM Licensing Services.

Please enable JavaScript in your browser to complete this form.
Author
  • Fredrik Filipsson

    Fredrik Filipsson brings two decades of Oracle license management experience, including a nine-year tenure at Oracle and 11 years in Oracle license consulting. His expertise extends across leading IT corporations like IBM, enriching his profile with a broad spectrum of software and cloud projects. Filipsson's proficiency encompasses IBM, SAP, Microsoft, and Salesforce platforms, alongside significant involvement in Microsoft Copilot and AI initiatives, improving organizational efficiency.

    View all posts