LICENSEWARE
Contribute

IBM Passport Advantage licensing

From the LICENSEWARE WikiLast edited 20 ReferencesCited

This article is about IBM Passport Advantage software licensing metrics (PVU, VPC, RVU, UVU, Authorized User, Concurrent User, Install, Virtual Server, Managed Virtual Server, Terabyte, Resource Unit), container counting, and Cloud Pak topology. It does not replace existing IBM white-paper galleries.

On This Page

IBM Passport Advantage is IBM’s volume-licensing program for software. Programs acquired under Passport Advantage are measured by the unit of measure named in the program License Information (LI), commonly Processor Value Unit (PVU), Virtual Processor Core (VPC), Resource Value Unit (RVU), User Value Unit (UVU), Authorized User, or Concurrent User. Contractual terms are the International Program License Agreement (IPLA), the program LI, and the International Passport Advantage Agreement (IPAA). Passport Advantage educational pages retrieved 2026-08-31 are labeled informational only.

Editions

Passport Advantage is a commercial program, not a product edition family. IBM names two enrollment wrappers on Passport Advantage materials: Passport Advantage and Passport Advantage Express. Program-level commercial editions (for example DB2 editions) live in each program’s License Information, not on this page.

IPLA Z125-3301-14 defines Authorized Use as the specified level at which Licensee is authorized to execute or run the Program, which “may be measured by number of users, millions of service units (“MSUs”), Processor Value Units (“PVUs”), or other level of use specified by IBM,” and License Information as the document with terms specific to a Program, available at IBM’s software SLA site.[8] Passport Advantage / Passport Advantage Express Revision 12 FAQs: changes effective 1 August 2024 (new IPAA/IPAEA) and 1 November 2024 for existing IPAA sites. IBM describes v12 as support-term consolidation, license-verification clarification, base-agreement alignment, and restructure — not a metric rename.[10]

The IPLA PDF cited here is v14 Z125-3301-14. IBM licensing guides also cite IPLA v15 (i125-3301); that PDF was not retrieved. Current IPAA v12 full text on IBM Terms / CSOL was not retrieved (JS portal). See the Nov 2017 IPAA gap in the callout above.

Metrics

The catalog has eleven rows for IBM, each under IBM’s own name; definitions are on the linked rows. RVU MAPC is an alias of RVU, not a separate row.

# IBM name Catalog row Unit What IBM says 
1 PVU Processor Value Unit (PVU) PVU Core-based; PVUs per core come from the PVU table, not a universal formula. Full Capacity vs Virtualization Capacity (Sub-Capacity). Container PVU is a separate 70 PVU per vCPU rule; the PVU table does not apply to Container Licensing. 
2 VPC Virtual Processor Core (VPC) VPC Core-based. Sub-capacity: IBM states 1 VPC equals 1 virtual CPU (vCPU). Container: 1 vCPU = 1 VPC. No global VPC-to-PVU table for traditional VM licensing. 
3 RVU Resource Value Unit (RVU) Other Resource-based; conversion is program-specific (LI RVU table). Sub-capacity eligible when IBM names RVU MAPC (Managed Activated Processor Core). No Passport Advantage global RVU table comparable to the PVU table. 
4 UVU User Value Unit (UVU) User User-based; program-specific UVU table in the LI. Not a core-based sub-capacity metric. 
5 Authorized User Authorized User User Unique person given access; multiplexing still requires an entitlement; reassignment only for permanent transfer. IBM does not list “Named User” as the PA metric name. 
6 Concurrent User Concurrent User User Person accessing the Program at a point in time; one person accessing multiple times counts as one Concurrent User; license the maximum simultaneous users. 
7 Install Install Other Installed copy on a physical or virtual disk made available to be executed. One entitlement per Install. ILMT can track Install; that is a tool rule, not a metric. 
8 Virtual Server Virtual Server Other Entitlement for each virtual server made available to the Program, regardless of cores or copies. 
9 Managed Virtual Server Managed Virtual Server Other Entitlement for each virtual server managed by the Program. Distinct from Virtual Server. 
10 Terabyte Terabyte Other IBM: “A Terabyte is 2 to the 40th power bytes.” Entitlement per Terabyte available to (or managed by) the Program. 
11 Resource Unit (RU) Resource Unit (RU) Other Cloud Pak metric named alongside VPC. Conversion is in the Cloud Pak License Information, not on the common-metrics page. Distinct from RVU. 

IBM License Metric Tool (ILMT) is a tool, not a metric. IBM Cloud Pak is a bundle topology, not a metric (typically VPC or Resource Unit with conversion ratios in the Cloud Pak LI).

Counting / floors

Effective dates on this page: PVU tables 08 May 2024 (x86) and 25 September 2024 (RISC/z); VPC sub-capacity ILMT policy 10 May 2022; PA v11 VPC reporting 1 February 2023 (new customers) / 1 May 2023 (existing); prior v10 manual-exception end 1 January 2024; container and Cloud Pak guides effective January 2022, last update August 2026; retrieved 2026-08-31.[2][3]

Activated processor core. IBM: a processor core that is available for use in a physical or virtual server, regardless of whether the capacity of the processor core can be or is limited through virtualization technologies, operating system commands, BIOS settings, or similar restrictions.[1]

Full Capacity (PVU). Entitlements sufficient to cover all activated processor cores in the physical hardware environment made available to or managed by the Program, except servers from which the Program has been permanently removed.[1]

Sub-capacity (PVU / VPC / RVU MAPC). Entitlements for activated processor cores made available to or managed by the Program per Virtualization Capacity License Counting Rules. Lower of: maximum virtual cores available to the Eligible Product at any time, or physical capacity of the host when virtual capacity exceeds physical. Then, for PVU, multiply cores by PVUs/core from the PVU table; for VPC, IBM states 1 VPC equals 1 vCPU; for RVU MAPC, use the Principal Program LI to convert cores to RVUs.[3][12] Catalog proof: PVU sub-capacity — lower of virtual vs physical (backs PVU sub-capacity — lower of virtual vs physical).

SMT / hyperthreading (traditional sub-capacity). IBM: “SMT/hyperthreading ratios are not adjusted for with sub-capacity licensing.” Catalog proof: Sub-capacity — no SMT/hyperthread adjustment (backs Sub-capacity — no SMT/hyperthread adjustment). Peak / high-water: IBM FAQs — no averaging, no true-up grace period; license the maximum (peak) processor core capacity (“at any given time”). Catalog proof: Peak / high-water mark (no averaging) — at any given time (backs Peak / high-water mark (no averaging)). ILMT regions: Region 1 Americas; Region 2 Europe & Africa; Region 3 Asia & Australia — counting materials apply to servers in the same ILMT Region.[3][11]

Floor (core-based). “The minimum requirement for software licensing is the appropriate number of license entitlements for one processor core” / “one whole processor core.” Fractional PowerVM cores: IBM aggregates fractions, applies shared-pool capping, and rounds up at the server level to the next whole processor core.[11] Catalog proof: Minimum one whole processor core (backs Minimum one whole processor core).

PVU table examples IBM prints (not a complete reprint; look up the live table by processor vendor, brand, type, and model). RISC/z as of 25 September 2024: POWER IFL / POWER Linux = 70 PVUs/core; POWER11 E1180 >4 sockets = 120; E1150 = 100; scale-out S11xx = 70. x86 as of 08 May 2024: Intel post-Nehalem Xeon including Xeon 6 and Xeon Scalable: 70 / 100 / 120 PVUs/core for max sockets 2 / 4 / >4; AMD EPYC = 70; AMD Opteron = 50; Intel Core i3/i5/i7/i9 = 70 (newest generation using Performance Hybrid Architecture with two core types excluded); “Any / All others” = 100. IBM worked example: 2-socket × 6 cores = 840 PVUs (70×12); 4-socket × 6 cores = 2400 (100×24); 8-socket × 6 cores = 5760 (120×48). Connected sockets forming SMP raise the “maximum sockets per server” bucket.[2] Catalog proof: PVU table application — socket buckets (examples, not full reprint) (backs PVU table application (not a reprint of every CPU)).

Only IBM-stated conversions. Sub-capacity: 1 VPC = 1 vCPU. Containers: 1 vCPU = 1 VPC and 70 PVU / vCPU. IBM does not publish a global PVU↔VPC conversion for traditional (non-container) licensing. The 70 PVU per vCPU rate does not apply to VM sub-capacity.[3][4][7]

Virtualization & partitioning

Virtualization Capacity (Sub-capacity) Licensing is limited to the three core-based metrics IBM lists on the sub-capacity page: PVU, VPC, and RVU MAPC. Counting-rule PDFs for named hypervisors (x86, Power Systems, IBM i, Linux on System z, Sun/Fujitsu, OS/BIOS) are published on IBM DHE under public.dhe.ibm.com/software/passportadvantage/SubCapacity/. Eligible processor and virtualization technology exhibits on that index are dated 2025-10-02. The Sub_Capacity_Eligible_Programs.pdf listing on DHE is dated 2018 on the directory — likely incomplete versus IBM’s “all core-based Products” statement; the 2018 PDF is not a current list.[3][12]

ILMT (tool). Mandatory for sub-capacity; recommended for full capacity. Install within 90 days of first eligible sub-capacity deployment. PA v11 (February 2023): exceptions for sub-capacity reporting removed. Prior v10 manual reporters: allowed until 1 January 2024 if still compliant with v10 exceptions. “Starting January 1, 2024 all prior exceptions are no longer applicable.” Reports at least quarterly; retain at least two years. Failure to generate/provide reports → full capacity charging. Approved alternatives IBM names: HCL BigFix Inventory (validated versions); Flexera One and Flexera One Select with IBM Observability IT Asset Management, and Flexera One / Flexera One Select IT Asset Management. HCL BigFix Inventory is not accepted for Red Hat OpenShift / Kubernetes. Flexera One can report OpenShift/Kubernetes through IBM License Service integration, not stand-alone. ILMT Lite + Disconnected Scanner pre-approved if target VMs/LPARs in scope < 5000. ILMT order (educational): P/N D561HLL; S&S renewal E027NLL; licensed “per establishment.”[5][11] Catalog proof: ILMT mandatory for sub-capacity (PVU / VPC / RVU MAPC) (backs ILMT mandatory for sub-capacity (PVU / VPC / RVU MAPC)).

Unreconciled conflict: the cited IPAA Z125-5831-10 11/2017 still lists ILMT exceptions (ILMT unsupported; <1000 employees and <1000 PVUs; full-capacity servers). Current educational pages say those exceptions ended. Current contractual text is IPAA v12 on IBM Terms, not retrieved.[9]

Power WPAR. IBM counting-rule PDF: ILMT required; manual calculation not available.

VPC sub-capacity ILMT (policy dates). With Passport Advantage v11, sub-capacity reporting that applied to PVU/RVU now applies to VPC for new customers 1 February 2023 and existing 1 May 2023. Effective 10 May 2022, VPC sub-capacity requires ILMT or an approved tool; “Manual capacity counting will no longer be permitted.” Failure → full capacity of activated physical cores. Container licensing is not included in that VPC policy change.[3]

Cloud / BYOL

IBM publishes an Eligible Public Cloud BYOSL Policy for deploying IBM software in an eligible public cloud under Passport Advantage. Related program: Eligible Public Cloud BYOSL. IBM states no public-cloud vCPU mapping beyond the footnotes on that policy and the separate container conversions.[13]

BYOSL Note 1 — only where IBM footnotes it. Licensing footnotes on the BYOSL page “apply only where specifically noted within the Cloud provider sections” and “do not apply universally to all offerings.” Where footnoted, IBM prints: 1 vCPU = 1 Core = 1 VPC = 70 PVUs; for containers with Hyperthreading enabled: 2 vCPUs = 1 Core = 1 VPC = 70 PVUs (see Container Licensing). Note 1 does not apply to traditional VM sub-capacity or to every BYOSL offering.[13] Catalog proof: BYOSL Note 1 — only where IBM footnotes it (not universal) (backs BYOSL Note 1 — only where IBM footnotes it).

BYOSL Note 3 — Oracle Cloud OCPU. “An Oracle Compute Unit (OCPU) corresponds to two hardware execution threads, known as vCPUs. PVU licensing requires 1 OCPU = 2 vCPU = 140 PVU.”[13] Catalog proof: BYOSL Note 3 — Oracle Cloud OCPU = 2 vCPU = 140 PVU (backs BYOSL Note 3 — Oracle Cloud OCPU).

BYOSL exclusivity. “When you use a license entitlement according to this policy, you may not use such entitlements for any other purpose or in any other place at the same time.” Policy does not apply to IBM z/OS software, software sublicensed by a third party, or IBM Business Partner hosted-solution deployments as IBM states.[13] Catalog proof: BYOSL — entitlements not used elsewhere at the same time (backs BYOSL — entitlements not used elsewhere at the same time).

Container environments (Kubernetes / Red Hat OpenShift) use Container Licensing, not traditional VM sub-capacity. IBM: Container Licensing is a separate licensing policy to Sub-Capacity. Sub-Capacity is used for licensing traditional virtual machines.[4][7]

Containers

Source class: Passport Advantage Container Licenses page (retrieved 2026-08-31) and Container Licensing — Virtualization Capacity licensing rules for IBM programs deployed in container environments (effective January 2022, last update August 2026; educational). Eligible container metrics IBM names: PVU and VPC. Related program: Container Licenses.[4][7]

IBM-stated conversions (container licensing only). “For the purposes of this guidance, 1 VPC is equal to 1 vCPU and 70 PVUs is equal to 1 vCPU.” FAQ: “The PVU table does not apply to Container Licensing. … the PVU rate is set at a single value of 70 PVUs per Virtual Processor Core (VPC) or virtual CPU (vCPU).” Ratio IBM prints: 1 vCPU = 70 PVU; 1 vCPU = 1 VPC. Those ratios do not apply to traditional VM sub-capacity.[4][7] Catalog proof: Container — 70 PVU = 1 vCPU (1 VPC = 1 vCPU) (backs Container — PVU table does not apply; 70 PVU = 1 vCPU).

vCPU capacity counting. Pod vCPU = sum of Kubernetes CPU limits for containers in the pod; fractions allowed; capped at worker-node capacity; cluster aggregate rounded up to nearest whole integer; a pod/container without a CPU limit = worker node capacity. IBM License Service is the only accepted tracking tool; “There are no exceptions to this rule.”[4] Catalog proof (methodology): Container vCPU Capacity Counting Methodology (backs Container vCPU Capacity Counting Methodology). Catalog proof (License Service mandatory): Container Licenses — IBM License Service mandatory (backs Container Licenses — IBM License Service mandatory).

SMT/HT is adjusted for container licensing (unlike traditional sub-capacity): SMT2/HT → 2 vCPU per 1 core as 1 VPC or 70 PVUs; SMT4 → 4:1; SMT8 → 8:1; mixed SMT in a cluster → lowest factor. Identification of HT/SMT “to be done manually and assigned at a cluster level” until License Service automates it. Polling: available vCPU capacity polled at intervals ≤ 30 minutes; maximum of intraday values = daily available vCPU capacity (high-water mark).[4]

Addendum — Special Option for Container Licensing is referenced from the PA container page as downloadable from IBM Terms; that PDF was not retrieved, so its terms are not described here.

Cloud Paks

IBM name: IBM Cloud Paks. Not itself a metric. A bundle licensed under a metric (typically Virtual Processor Core (VPC) or Resource Unit) with conversion entitlement ratios in the Cloud Pak License Information document. Cloud Paks Licensing Guide (effective January 2022, last update August 2026; educational).[6]

IBM: “While the Cloud Pak itself is licensed under a single [metric], each Bundled Program is licensed under separate metrics with associated conversion …” Example IBM prints (illustrative of how IBM writes ratios, not a universal table): “Bundled Program A: Conversion Entitlement Ratio: 1 VPC/5 VPCs” meaning “every 1 VPC of use of IBM Program A requires 5 VPC licenses of the Cloud Pak.”[6]

Worked example in the same guide for Cloud Pak for Integration: MQ Advanced 2:1, App Connect Enterprise 1:3, DataPower Gateway 1:1, API Connect 1:1. IBM shows combining those converted VPC contributions against Cloud Pak VPC entitlements. The example is not the current LI for any named version. Current ratios require the LI for the entitled Cloud Pak version. IBM: “You are not required to license the peak use of each individual Bundled Program but the peak use of the IBM Cloud Pak as a whole.”[6]

Tracking: non-container Cloud Pak programs — ILMT. Container Cloud Paks — License Service × conversion ratio. Container Licenses page: “If the ratio is not specified, it is assumed to be 1:1.” “For all IBM Cloud Paks deployed in containers, you must acquire entitlements equal to the license requirements (as derived in the vCPU Capacity Counting Methodology for IBM Programs section) and measured by the IBM License Service multiplied by the required Cloud Pak conversion ratio.”[4] Catalog proof (default 1:1 when LI unspecified): Cloud Pak conversion ratio — LI; default 1:1 if unspecified (backs Cloud Pak conversion ratio (LI; default 1:1)). Product-specific Cloud Pak VPC/RU ratios are set in each program’s LI; only the 1:1 default is stated here.

Programs

Related programs: Passport Advantage; Container Licenses (License Service / container proof Container Licenses — IBM License Service mandatory); Eligible Public Cloud BYOSL (Note 1 / Note 3 / exclusivity proofs BYOSL Note 1 — only where IBM footnotes it (not universal), BYOSL Note 3 — Oracle Cloud OCPU = 2 vCPU = 140 PVU, BYOSL — entitlements not used elsewhere at the same time).

Passport Advantage / Passport Advantage Express is the commercial wrapper. IBM names IPAA (International Passport Advantage Agreement) and IPAEA. PA v12 FAQs: new IPAA/IPAEA effective 1 August 2024; existing IPAA sites 1 November 2024. v12 is not a metric rename.[10]

Contractual stack. IPLA (cited version Z125-3301-14; guides also cite v15 i125-3301) + program License Information (IBM states 30,000+ LIs; portals https://www.ibm.com/terms/?cat=software-license and https://www.ibm.com/software/sla ) + IPAA. Current IPAA is on IBM Terms (Z125-5831); live CSOL body was not retrieved. The IPAA PDF cited here is Z125-5831-10 11/2017 (see the Nov 2017 IPAA gap); that v10 PDF is not the current Passport Advantage definition.[8][9][14]

IBM License Metric Tool (ILMT) is a tool, not a metric. Mandatory for sub-capacity; recommended for full capacity. See Virtualization & partitioning for install window, report retention, approved alternatives, and the IPAA v10 vs educational-page conflict. Containers use IBM License Service, not ILMT.[5]

Client Relationship Agreement (CRA). August 2026 updates to the Cloud Paks and Container Licensing guides state they were updated based on replacement of Passport Advantage Agreement (PA/PAE) to Client Relationship Agreement (CRA). The CRA text was not retrieved, so its metric terms are not described here.[6][7]

Out of scope

  • ILMT / IBM License Service / HCL BigFix Inventory / Flexera One — tools, not metrics. Tracking rules are summarized above; they are not Vendor License Metrics rows.
  • IBM Cloud Pak as a metric — it is bundle topology; ratios live in each Cloud Pak LI.
  • MSU / z/OS IPLA metrics — IPLA mentions MSUs; this page stays on Passport Advantage distributed metrics.
  • Program License Information UVU/RVU tables and Cloud Pak conversion ratios — 30,000+ LIs; not individually retrieved. Look up the entitled program version.
  • IPAA v12 full text and IPLA v15 (i125-3301) — not retrieved.
  • Addendum — Special Option for Container Licensing — not captured.
  • Sub_Capacity_Eligible_Programs.pdf (2018 DHE listing) — likely stale.
  • No IBM-published global PVU↔VPC conversion for traditional (non-container) licensing. 70 PVU = 1 vCPU is container guidance only.
  • Existing IBM white papers in this wiki (including IBM DB2 Licensing White Paper) are archives. This page sits alongside them and does not overwrite them.
  • Hardware-only, services-only, and third-party commentary.

Catalog rows

Sample catalog rows for this article, grouped by table.

References

  1. Passport Advantage / Passport Common License Types & DefinitionsLive educational page; IBM disclaimer: informational only. IPLA + LI + PA Agreement governRetrieved 2026-08-31.
  2. Processor Value Units (PVUs) and PVU tablesRISC/z table publish date 25 September 2024; x86 table 08 May 2024Retrieved 2026-08-31.
  3. Virtualization Capacity (Sub-capacity) LicensingVPC/ILMT policy 10 May 2022; PA v11 Feb/May 2023; manual-exception end 1 Jan 2024Retrieved 2026-08-31.
  4. Container Licenses (Passport Advantage)Live educational page; container conversions 1 vCPU = 1 VPC and 70 PVU/vCPU container-onlyRetrieved 2026-08-31.
  5. IBM License Metric Tool informationLive educational page; ILMT is a tool, not a metricRetrieved 2026-08-31.
  6. IBM licensing guides portal (Cloud Paks Licensing Guide)Guides effective January 2022; last update August 2026 (educational; CRA note)Retrieved 2026-08-31.
  7. IBM licensing guides portal (Container Licensing Guide)Guides effective January 2022; last update August 2026 (educational; CRA note)Retrieved 2026-08-31.
  8. International Program License Agreement (v14)PDF Z125-3301-14. Guides also cite IPLA v15 i125-3301 (not retrieved)Retrieved 2026-08-31.
  9. International Passport Advantage Agreement (v10 PDF)Form Z125-5831-10 11/2017 (PA v10). Stale vs IBM Terms IPAA v12 (not retrieved); not Cited as current PA definitionRetrieved 2026-08-31.
  10. Passport Advantage / Passport Advantage Express Revision 12 FAQsChanges effective 1 August 2024 (new IPAA/IPAEA); 1 November 2024 existing IPAA sitesRetrieved 2026-08-31.
  11. Sub-Capacity FAQs OverviewEducational FAQ; whole-core minimum; peak capacity; ILMT exceptions end 1 Jan 2024Retrieved 2026-08-31.
  12. Virtualization Capacity License Counting RulesPoints to DHE counting-rule PDFs (index last-modified dates through 2025)Retrieved 2026-08-31.
  13. Eligible Public Cloud BYOSL PolicyChange log March 2024; Notes 1/3/exclusivity Cited in Cloud/BYOLRetrieved 2026-08-31.
  14. IBM Terms, IPAA (current)Current IPAA on IBM Terms; JS portal, v12 full text not retrievedRetrieved 2026-08-31.
  15. IBM Terms, License Information repositoryContractual per-program LI; 30,000+ documents, not individually retrievedRetrieved 2026-08-31.
  16. Virtualization Capacity (Sub-capacity) LicensingCatalog: Virtualization Capacity (Sub-capacity) LicensingEffective 2022-05-10. Retrieved 2026-08-31.
  17. Processor Value Units (PVUs)Catalog: Processor Value Units (PVUs)Effective 2024-05-08. Retrieved 2026-08-31.
  18. Sub-Capacity FAQs OverviewCatalog: Sub-Capacity FAQs OverviewEffective 2026-08-31. Retrieved 2026-08-31.
  19. Container LicensesCatalog: Container LicensesEffective 2026-08-31. Retrieved 2026-08-31.
  20. Eligible Public Cloud BYOSL PolicyCatalog: Eligible Public Cloud BYOSL PolicyEffective 2024-03-01. Retrieved 2026-08-31.

See also

Esc