Db2 Advanced Enterprise Server Edition licensing.

Db2 Advanced Enterprise Server Edition is the high end of the Db2 range, licensed per Processor Value Unit. Its real audit exposure is not the database engine. It is the long list of supporting programs bundled inside the edition, each carrying restrictions that are easy to breach without noticing.

What the edition actually entitles

Advanced Enterprise Server Edition packages the full Db2 engine together with advanced features and a set of supporting programs supplied under restricted use terms. The headline entitlement is core based PVU, counted across the processors where the database runs, with sub-capacity available when ILMT is deployed and operating correctly. The supporting programs that travel with the edition are not separately licensed for unrestricted use. They are licensed only to support the Db2 deployment they shipped with.

Where these estates drift out of compliance

Supporting programs used beyond their grant

The bundled tools that come with the edition carry a restricted use grant tied to the Db2 deployment. When a team adopts one of those tools for a workload that is not the entitled Db2 estate, the use moves outside the grant. Auditors look for exactly this pattern, because the bundle invites it and few buyers track the boundary.

Edition entitlement against deployment

Estates accumulate a mix of editions over time. An Advanced Enterprise Server Edition entitlement record and a deployment that quietly includes a different edition, or more PVU than the entitlement covers, is a routine finding. The fix is a clean reconciliation of what each server runs against what each server is entitled to run.

What to verify before accepting a finding

• Each supporting program is used only to support its entitled Db2 deployment.
• PVU counts reflect sub-capacity where ILMT supports it, not full capacity by default.
• The deployed edition on each host matches the edition on the entitlement record.
• Non-production and cold-standby instances are scoped under the correct rights.

How we defend the position

We separate the engine from the bundle. The Db2 engine count is reconciled against entitlements and sub-capacity evidence. The supporting programs are mapped to their restricted use grant so that any claim of out of scope use is tested against the actual deployment, not assumed. Where a genuine gap exists, it is isolated and quantified so the settlement covers only the real exposure.