The IBM Product Licensing Reference Guide.

Why this reference exists.

The IBM portfolio runs to several hundred discrete licensed products across a dozen product families. The licensing treatment varies materially by product, by edition, and by platform. This pillar is the product first reference. For the metric first reference, see the IBM Licensing Complete Guide. For the sub capacity reference, see Sub Capacity Explained. For single point questions, see the IBM Licensing FAQ.

The product reference is the document the deployment team and the procurement team use when a new IBM product enters the environment, when an edition migration is on the table, or when a renewal decision turns on a per product line item. The view that follows is from the chair of an independent advisor.

1. WebSphere family.

WebSphere Application Server is the canonical IBM application server family. The licensing is PVU based across the editions (Base, Network Deployment, Liberty Core, Hypervisor edition). All editions are sub capacity eligible. The edition decision turns on the clustering and management requirements rather than on raw application functionality. Liberty Core is sized for the smaller, modern, container friendly footprint and carries materially lower PVU consumption per workload. The WebSphere licensing reference covers the edition tree. The white paper companion is the WebSphere Licensing Deep Dive.

WebSphere Application Server for z/OS is a distinct product and is licensed under the mainframe stack. It is not interchangeable with the distributed WebSphere entitlements.

2. MQ family.

MQ is the IBM messaging family. The licensing is PVU based for MQ on distributed and is split across MQ, MQ Advanced, and MQ Advanced for Multiplatforms. The edition gap is consequential. MQ Advanced includes Advanced Message Security, Managed File Transfer, and the High Availability replication features. A buyer running those features on the base MQ entitlement has consumed Advanced edition without the corresponding licence. This is the single most common middleware compliance gap. The MQ licensing reference covers the feature mapping. The MQ and Tivoli Licensing white paper documents the operational position.

The MQ Appliance is a hardware appliance and is licensed per appliance. It is not part of the PVU envelope and does not draw down PVU entitlement.

3. Db2 and database.

Db2 is the IBM relational database family. The distributed editions are Advanced Server, Standard, Workgroup, and the free Db2 Community Edition. The licensing is PVU based for the enterprise editions and Authorized User for the user metric variants. The edition decision drives the feature inclusion (Db2 Advanced Recovery, Db2 Advanced Security, Federation, Replication) and the underlying compute entitlement. A buyer running Federation or Replication on the Standard edition has consumed Advanced edition. The Db2 licensing reference walks through the feature gating. The white paper companion is the Db2 Licensing Explained.

Db2 for z/OS is a distinct product and is licensed under the mainframe MLC envelope. Informix and the broader database family carry their own licensing rules and are referenced in the database expertise page.

4. Cognos and analytics.

Cognos Analytics is the IBM enterprise reporting and analytics platform. The licensing is split between server side (PVU) for the platform components and user side (Authorized User, Concurrent User, Mobile User) for the human consumption. The buyer side discipline is the reconciliation of named user records to the actual reporting consumption pattern. A user that signs in once a quarter and a user that runs daily reports both count as one Authorized User. The Cognos licensing reference covers the licence model. The broader analytics treatment, including SPSS and Watson Studio, is in the SPSS licensing reference.

5. Cloud Pak portfolio.

The Cloud Paks are the modern IBM platform offerings. Each Cloud Pak bundles a defined set of products, a defined entitlement of Red Hat OpenShift, and a unified VPC based metric. The current portfolio includes Cloud Pak for Applications, Integration, Data, Watson AIOps, Security, Business Automation, and Network Automation. The buyer side calculus is the bundle versus standalone decision. The bundle is the right answer when the buyer consumes at least two of the bundled products at sufficient scale. The bundle is the wrong answer when the buyer consumes only one product or when the OpenShift bundled entitlement is already covered by a standalone OpenShift subscription. The Cloud Pak strategy reference walks through the bundle calculus. The white paper companion is the Cloud Pak Licensing Guide.

6. Red Hat and OpenShift.

Red Hat is licensed by subscription. The defining Red Hat products in the enterprise IBM estate are Red Hat Enterprise Linux (RHEL), Red Hat OpenShift Container Platform (OCP), Red Hat Ansible Automation Platform, and the broader middleware stack inherited from JBoss. RHEL is sold by subscription per socket pair on physical hosts and per VM on virtual hosts. OCP is sold by node subscription on bare metal and on virtual deployments. The bundled OpenShift entitlement that ships with the Cloud Paks is the same OCP, but the entitlement is sized to the Cloud Pak workload. The Cloud Pak strategy reference covers the overlap. The Red Hat Enterprise Strategy white paper documents the full position. The OpenShift Licensing Deep Dive covers the OCP detail.

7. Tivoli and observability.

The Tivoli family is the legacy IBM monitoring and operations management portfolio. The licensing is PVU based. The defining trap is the agent inventory. A buyer that has propagated Tivoli monitoring agents across a large estate without an agent inventory typically discovers the agent count is many multiples of the entitlement at audit. The remediation is the agent inventory, the agent retirement, and the harvest of the unused entitlement. The MQ and Tivoli Licensing white paper covers the operational position. The middleware expertise page covers the broader frame.

8. watsonx family.

watsonx is the AI native product family. The portfolio is watsonx.ai (foundation model inference and training), watsonx.data (the open data lakehouse), and watsonx.governance (model governance and risk). The licensing is largely Resource Unit based with token consumption components for the foundation model use. The pricing model is materially different from the rest of the IBM portfolio and the buyer side discipline at the deployment design stage matters more than at any other IBM product. The watsonx licensing reference covers the metric structure. The white paper companion is the watsonx Licensing Primer.

9. Mainframe stack.

The mainframe stack is licensed under the Monthly License Charge (MLC) for the foundational products (z/OS, CICS, IMS, Db2 for z/OS, MQ for z/OS) and the International Program License Agreement (IPLA) for most additional software. MLC charges scale on the four hour rolling peak MSU consumption captured by the Sub Capacity Reporting Tool (SCRT). IPLA charges are typically a fixed entitlement. The discipline of capping the peak is the highest yield cost lever on the mainframe estate. The mainframe expertise page covers the position. The white paper companions are the Mainframe MLC and IPLA Guide and the z/OS Cost Optimization deep dive.

10. The product matrix.

Where to go next.

For the metric first reading continue to the IBM Licensing Complete Guide. For the sub capacity reading continue to Sub Capacity Explained. For single point questions continue to the IBM Licensing FAQ. The white paper library covers each product family in book length. The insights blog covers the day to day operational topics.

For a scoped advisory conversation, the contact page is the entry point. The license consulting service covers the operational compliance frame. The negotiation service covers the commercial frame.