IBM
IBM MQ licensing, without the audit surprise.
MQ cost turns on sub capacity, ILMT, and editions. Here is how to license messaging without overpaying or failing an audit.
MQ cost turns on sub capacity, ILMT, and editions. Here is how to license messaging without overpaying or failing an audit.
IBM MQ licenses on Processor Value Units or Virtual Processor Cores, and the difference between them, plus sub capacity rules, decides whether you overpay on a virtualized estate.
Older MQ entitlements are measured in Processor Value Units, where a core maps to a PVU rating by processor type. Newer entitlements use Virtual Processor Cores, a simpler per core count. IBM documents both on the IBM MQ product page.
Mixing the two across an estate is where audit exposure builds. A queue manager licensed under PVU running on hardware counted under VPC creates a reconciliation gap.
IBM MQ licensing metrics
| Metric | Basis | Sub capacity | Note |
|---|---|---|---|
| PVU | Core times processor rating | Yes, with ILMT | Legacy entitlements |
| VPC | Virtual processor cores | Yes, with ILMT | Current model |
| Appliance | Fixed hardware unit | Not applicable | Predictable cost |
New MQ deployments generally land on VPC, which is simpler to count. Keep PVU and VPC entitlements clearly separated in your records to avoid reconciliation gaps at audit.
Map every queue manager to its entitlement metric and host. A single inventory that ties deployment to entitlement is what closes the gap auditors look for.
Sub capacity lets you license only the cores allocated to MQ on a virtualized host, not the entire physical server. IBM requires the IBM License Metric Tool to claim it.
Without current ILMT data, IBM licenses MQ at the full physical capacity of the host. On a large virtualized cluster that difference is enormous.
MQ Advanced adds managed file transfer and Advanced Message Security at a higher unit cost. Licensing it estate wide when only some queue managers use those features is common waste.
Splitting Advanced and base entitlements by actual feature use, rather than buying one edition for simplicity, routinely cut MQ spend in our engagements. Check your entitlements on IBM Passport Advantage.
MQ running in containers on OpenShift or Kubernetes follows container licensing rules tied to allocated virtual cores. IBM publishes the container terms in its MQ documentation.
Misapplying full host licensing to container deployments is a frequent overpayment. Allocated cores, not cluster size, set the entitlement.
The standard reseller advice is that buying MQ Advanced estate wide simplifies licensing and protects you at audit. We disagree. In roughly 15 of the 25 plus IBM estates we benchmarked, Advanced was licensed across every queue manager when only a fraction used managed file transfer or Advanced Message Security, and the simplicity argument hid a steady overpayment. The buyer side move is to split base and Advanced by actual feature use and to invest the savings in keeping ILMT current, which is the control that genuinely protects you at audit. Simplicity that costs you double every year is not a saving, it is a default you never challenged.
Three cuts of our advisory engagement file frame the size of the opportunity.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Five moves turn this analysis into a lower invoice on the next renewal.
White Paper · IBM
Settle an IBM Audit Without Overpaying
How to settle an IBM audit without overpaying: the settlement math, the bundle traps, and the legal posture that shrinks a 7 figure exposure. Read it free.
IBM MQ licenses on Processor Value Units for older entitlements or Virtual Processor Cores for newer ones. Both support sub capacity licensing with the IBM License Metric Tool, and the MQ Appliance offers a fixed hardware unit alternative.
Processor Value Units rate a core by processor type, while Virtual Processor Cores are a simpler per core count. New deployments generally use VPC. Mixing the two across an estate creates reconciliation gaps that surface at audit.
Without current IBM License Metric Tool reports, IBM licenses MQ at the full physical capacity of every virtualized host. ILMT is the control that lets you claim sub capacity and license only the cores allocated to MQ.
Sub capacity can dramatically reduce cost on virtualized estates because you license allocated cores rather than the whole server. Without ILMT, exposure on a large cluster can rise 30 to 200 percent versus the sub capacity figure.
Usually not. MQ Advanced adds managed file transfer and Advanced Message Security at a higher unit. In our engagements only 20 to 40 percent of queue managers used those features, so licensing Advanced estate wide was a common overpayment.
Container deployments license the virtual cores allocated to MQ, often through a Cloud Pak for Integration entitlement. ILMT reporting still applies. Applying full host licensing to containers is a frequent and avoidable overpayment.
The MQ Appliance shifts licensing to a fixed hardware unit rather than per core software metrics. It offers predictable cost and removes sub capacity tracking, which suits estates that want simpler, capped MQ spend.
The most common findings are missing or stale ILMT reports and mixed PVU and VPC entitlements that do not reconcile to deployment. A single inventory tying each queue manager to its metric and host closes most of that gap.
PVU versus VPC, sub capacity and ILMT rules, edition splitting, and the controls that protect MQ at audit.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Simplicity that costs you double every year is not a saving, it is a default you never challenged.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Pricing moves, audit signals, and the levers that work. No vendor spin.
