Editorial photograph of an enterprise data center with high availability server hardware and structured cabling
Article · IBM · AIX

IBM Power Systems AIX licensing. A buyer side guide.

AIX on Power Systems is licensed by processor entitlement against the active LPAR or partition. Capacity on demand, micropartitioning, and PVU rules drive the real cost. This guide unpacks the mechanics and the procurement playbook.

Read the Framework IBM Hub
AIXProcessor entitlement
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

AIX on IBM Power Systems is licensed by processor entitlement against the active partition. The entitlement count drives the license fee and the support stream. Capacity on demand and micropartitioning sit at the heart of the model and shape real customer cost.

Most AIX estates carry overprovisioned entitlements set during the original deployment. A structured rebaseline at refresh or renewal typically reduces the entitlement count by ten to thirty percent without service impact.

Read this alongside the IBM knowledge hub, the IBM services page, the IBM audit defense landing, and the Vendor Shield subscription.

Key Takeaways

What a CIO and procurement leader need to know in 90 seconds

  • Processor entitlement. AIX licensed against the active processor entitlement in the LPAR.
  • Capacity on demand. Activated and inactive processors carry different commercial postures.
  • Micropartitioning matters. Sub processor allocation lets customers right size the entitlement.
  • PVU history persists. Legacy PVU contracts still in force in many estates.
  • ILMT remains the mandate. IBM License Metric Tool must be deployed and current.
  • Audit pressure ongoing. IBM audit cadence rose through 2025 and continues into 2026.
  • Refresh reset. Each Power generation refresh is the moment to rebaseline entitlements.

AIX licensing model

AIX licenses by processor entitlement, not by physical core count. The entitlement is the number of processors allocated to the AIX partition through the Hardware Management Console.

Key concepts

  • Processor entitlement. The committed processor count assigned to an LPAR.
  • Virtual processor. The number of virtual processors visible in the partition.
  • Entitled capacity. The guaranteed share of physical resource.
  • Uncapped LPAR. Allowed to use spare capacity beyond entitlement.
  • Capped LPAR. Limited strictly to entitlement.

Capped versus uncapped

LPAR modeEntitlement licensedUses spare capacityAudit risk
CappedYesNoLow
UncappedYes plus measured peakYesHigher
DedicatedYes (whole core)NoLowest

Capacity on demand

Capacity on Demand (CoD) lets customers activate processors temporarily or permanently. The commercial posture varies by activation type.

CoD activation types

  • Permanent. Activated permanently with full license entitlement.
  • On Off CoD. Day passes for short term activation.
  • Trial CoD. Thirty day free activation for evaluation.
  • Reserve CoD. Prepaid pool of activation days.
  • Utility CoD. Pay per processor minute.

Three rules of thumb

  • Inactive processors do not need AIX licenses. Until activated.
  • On Off CoD activates the AIX requirement. For the activated days.
  • Trial CoD counts as activated. Audit treats it as production use.

Micropartitioning rules

Micropartitioning is the IBM Power feature that lets customers allocate sub processor entitlements to a partition. AIX entitlement counts the allocated processor entitlement, not the whole physical core.

The mechanics

  1. Define the entitlement. Allocate fractional processor entitlement, in increments of 0.05.
  2. Set virtual processor count. Number of virtual processors visible in the LPAR.
  3. Set cap mode. Capped or uncapped, depending on workload tolerance.
  4. Allocate memory. Memory tied to LPAR, separate from processor entitlement.
  5. Track in HMC. All changes logged in the Hardware Management Console.

Right sizing patterns

  • Capped at 1.0. Single processor entitlement for predictable workloads.
  • Uncapped at 0.5 plus burst. Variable workloads that need headroom.
  • Capped at 4.0 for batch. Heavy nightly processing on a dedicated entitlement.
  • Dedicated whole core. Mission critical with predictable peak demand.

Most AIX estates carry overprovisioned entitlements

The original deployment usually set entitlements with safety margin. Real workload measurement after twelve months typically shows ten to thirty percent of entitlement is unused. A structured rebaseline at refresh or renewal recovers that headroom and reduces the license footprint.

PVU posture

The PVU (Processor Value Unit) model still applies to many legacy AIX contracts. Newer Power generations carry their own PVU values published in the IBM PVU table.

PVU values by Power generation

Power generationPVU per coreYear released
Power91202018
Power101202021
Power111202024

ILMT mandate

  • Deploy ILMT. IBM License Metric Tool deployed within ninety days of contract signature.
  • Run quarterly reports. Standard subcapacity quarterly reports retained for two years.
  • Reconcile against contract. Deployed PVU matches the contracted PVU on file.
  • Subcapacity rules. ILMT is the mandatory mechanism for subcapacity licensing.
  • Audit defense. Missing or stale ILMT reports flip the entitlement to full capacity at audit.

Procurement playbook

The procurement playbook for AIX runs across the refresh cycle, the renewal cycle, and the audit cycle. Each cycle is an opportunity to right size and rebenchmark.

Six step playbook

  1. Baseline the estate. LPAR by LPAR entitlement, virtual processor, cap mode.
  2. Reconcile against ILMT. Quarterly reports match contracted PVU.
  3. Measure real utilization. Twelve months of actual processor use.
  4. Right size the entitlement. Cap to measured peak plus twenty percent buffer.
  5. Run the refresh model. Power11 refresh with reduced entitlement count.
  6. Negotiate the contract. Term, support hold, audit definitions, renewal cap.

Three procurement traps

  • Refresh creep. IBM adds entitlement count on the refresh quote without baseline justification.
  • Capacity on Demand attach. CoD activations added to the standard support stream.
  • Software Subscription and Support uplift. Annual S and S uplift compounds across multi year terms.

AIX licensing rewards careful baselining. Every refresh and every renewal is the opportunity to rebaseline the entitlement against measured workload. Most AIX customers find ten to thirty percent of entitlement is unused in production. That headroom is the negotiation lever.

What to do next

The eight step checklist below sets the buyer side starting point for any AIX licensing review at refresh or renewal.

  1. Baseline LPARs. Entitlement, virtual processor, cap mode by LPAR.
  2. Measure utilization. Twelve months of real processor use.
  3. Reconcile ILMT. Quarterly reports match contracted PVU.
  4. Right size entitlements. Cap to measured peak plus buffer.
  5. Model the refresh. Power11 with rebaselined entitlement count.
  6. Run the discount benchmark. Against three prior IBM Power deals.
  7. Negotiate the contract. Term, support hold, S and S cap.
  8. Document audit clauses. ILMT mandate, subcapacity rules, audit definitions.

Frequently asked questions

Does AIX require a license for inactive Capacity on Demand processors?

No. Inactive CoD processors do not require an AIX license until activated. The customer pays for hardware activation but does not consume AIX entitlement until the processor joins an active LPAR. Document CoD inventory in the LPAR profile. Confirm activation status with IBM at every refresh and renewal.

Can a customer downgrade AIX entitlement mid term?

Yes. AIX entitlement can be reduced through a partition profile change in the HMC. The contract entitlement remains at the original level unless renegotiated. Many customers run with reduced entitlement and renegotiate the contract entitlement at the next renewal cycle. The trail of HMC changes should be documented for audit defense and to support the renewal renegotiation conversation with IBM.

How does IBM ILMT compliance interact with AIX licensing?

ILMT is the mandatory mechanism for subcapacity AIX licensing across the Power Systems estate. Customers must deploy ILMT within ninety days of contract signature, run quarterly subcapacity reports, and retain the reports for two years. Failure to maintain ILMT in good standing typically triggers an audit reclassification from subcapacity to full capacity, which carries a significant cost impact.

Does Power11 change the AIX licensing model?

The Power11 generation maintains the same processor entitlement model as Power9 and Power10. PVU values per core remain at 120 PVU. The licensing rules around capping, uncapping, and dedicated mode are unchanged. Power11 does bring performance improvements that often let customers consolidate LPARs and reduce the entitlement count without service impact, which is the strategic refresh opportunity.

How does the refresh from Power9 to Power11 affect the AIX contract?

The hardware refresh is a discrete event from the AIX license contract. IBM typically pitches a refresh quote that includes both hardware and a software entitlement update. Customers should split the two conversations and rebaseline AIX entitlement against measured workload before accepting any new entitlement count. IBM account teams often inflate entitlement on the refresh quote.

How does Redress engage on IBM Power and AIX deals?

Redress runs IBM Power and AIX advisory inside the Vendor Shield subscription and the Renewal Program. Every engagement is led by a former IBM commercial executive on the buyer side and supported by a structured LPAR baseline, ILMT reconciliation, utilization measurement, and refresh model across Power9, Power10, and Power11 estates at enterprise scale.

How Redress engages on IBM deals

Redress runs IBM Power and AIX advisory inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment.

Read the related benchmarking, about us, locations, and contact pages.

Score your IBM audit readiness in under five minutes.
Open the Audit Defense Checklist →
White Paper · IBM

Download the IBM Audit Defense Guide.

A buyer side reference on IBM audit posture, ILMT compliance, PVU reconciliation, subcapacity rules, and the protective contract clauses that hold the deal through the term.

Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying IBM Power, mainframe, and middleware contracts. No IBM influence. No sales kickback.

IBM Audit Defense Guide

Open the white paper in your browser. Corporate email only.

Open the Paper →
120
PVU per Power core
30%
Typical entitlement overhang
500+
Enterprise clients
$2B+
Under advisory
100%
Buyer side

AIX licensing rewards careful baselining. Every refresh and every renewal is the opportunity to rebaseline the entitlement against measured workload. Most AIX customers find ten to thirty percent of entitlement is unused in production. That headroom is the negotiation lever.

Director of Procurement
Global financial services group
More Reading

More from this practice.

IBM Hub →
IBM Audit Defense Guide
IBM · White Paper
IBM Audit Defense Guide
Buyer side audit reference.
20 min read
IBM Advisory Services
IBM · Services
IBM Advisory Services
Practice overview.
12 min read
IBM Knowledge Hub
IBM · Hub
IBM Knowledge Hub
Master IBM reference.
20 min read
IBM Audit Defense Landing
IBM · Landing
IBM Audit Defense Landing
Audit advisory hub.
14 min read
Audit Defense Readiness
Audit Defense · Tool
Audit Defense Readiness
Cross vendor audit posture.
12 min read
Editorial photograph of enterprise contract negotiation strategy

Right size the AIX entitlement. Then negotiate the refresh.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

IBM intelligence, monthly.

Power refresh benchmarks, ILMT reconciliation patterns, PVU math, and audit settlement data across every IBM engagement we run on the buyer side.