① Journal · Renewal Playbook
Recovery Management for Db2 is a BMC AMI suite, typically priced on MSU capacity, and it is a family of components rather than one product: Recover, Recovery Manager, Copy, and Log Master under one premium feature. The footprint, the bundle, the zCL model, and overlap with native Db2 are the levers. Here is what actually moves the number.
Recovery is insurance, so nobody questions it. Which is exactly why the suite quietly outgrows the estate.
Recovery Management for Db2 is BMC's AMI suite for Db2 backup and recovery, the tooling that takes image copies, recovers table spaces and tables to a point in time or log point, analyzes the Db2 log, and keeps the database recoverable when something goes wrong. It is a family rather than a single product, commonly including BMC AMI Recover for Db2, BMC AMI Recovery Manager for Db2, BMC AMI Copy for Db2, and BMC AMI Log Master for Db2, drawn together under the Recovery Management premium feature. Like most of the BMC mainframe portfolio it is typically licensed on capacity, measured in MSU, so the number tracks the MSU of the LPARs the suite is entitled across rather than the count of Db2 objects or recoveries.
What makes this suite distinctive at renewal is the combination of two things: it is a bundle of components, and it is recovery tooling, which is to say insurance. Insurance is the category nobody wants to interrogate, because the downside of being wrong is a failed recovery, so the licensed scope and capacity tend to roll forward unchallenged year after year while the Db2 estate underneath them changes. Subsystems are consolidated, workloads move, some recovery tasks shift to native Db2 utilities, and components that were essential a decade ago quietly stop being used. A renewal is the moment to find that gap, on evidence, never on hope. Reading it means working the MSU footprint, the component bundle, the licensing model, and the genuine overlap with native Db2 together. This builds on our BMC publisher hub and our AMI Data for IMS licensing page.
Lever · what it moves · how to pull it
| Lever | What it moves | How to pull it |
|---|---|---|
| MSU footprint | The capacity the suite is licensed across drives the price | Align entitled MSU to the LPARs running the Db2 workload; remove dead scope |
| Component bundle | Packaging Recover, Copy, Log Master, and Recovery Manager hides per component cost | Price each component; confirm which are actually in production use |
| Native Db2 overlap | Tasks native Db2 utilities now cover may be redundant scope | Map recovery tasks against native Db2 utilities; cut what you do not need |
| zCL vs capacity pricing | The model sets how BMC capacity is charged and trued up | Model traditional capacity against zCL consumption and choose on the numbers |
| Fiscal year timing | Quota pressure near BMC's year end softens the number | Align the close to BMC's fiscal year end where the term allows |
Recovery cost hides inside a component bundle priced on capacity. Unbundle it, map it against native Db2, and the redundant scope appears, on evidence.
The suite grows because questioning it feels risky. The discipline is to question it carefully, not to leave it alone.
The largest movement on a Recovery Management for Db2 renewal usually comes from component and footprint rationalization, and the reason it is left on the table is psychological as much as technical. Recovery is the one place where being wrong is unforgivable, so the natural instinct is to keep everything, renew everything, and move on. That instinct protects the recovery posture but not the budget, and over time it funds a suite that is larger than the estate it covers. Subsystems get consolidated, Db2 versions absorb functions that once needed a separate tool, recovery patterns change, and the licensed components and MSU quietly drift away from what production actually uses. The renewal is the natural moment to close that gap, because the only way to know whether scope is needed is to look, and almost nobody looks at the recovery suite between renewals.
Doing it well means three disciplined passes, all evidence based. First, unbundle: insist that Recover, Recovery Manager, Copy, and Log Master each carry a separately stated price, so the suite cannot hide a redundant component inside a single number. Second, map use against native capability: document which recovery, copy, and log tasks genuinely depend on the BMC tools and which native Db2 utilities or competing tools could cover, distinguishing real dependence from inherited habit. Third, rationalize the footprint: align the licensed MSU to the LPARs that actually run the Db2 workload the suite protects. The discipline throughout is to cut only on evidence of what is unused, never on hope that a recovery will not be needed, because the saving is never worth a failed recovery. Combined with a deliberate capacity versus zCL choice and fiscal timing, this is where the renewal is won. Our cost optimization service finds the unused scope, and our license negotiation service converts it into a lower number.
Insist Recover, Recovery Manager, Copy, and Log Master each carry a separately stated price. A combined number hides a component that has stopped being used, and a price you cannot see is a price you cannot cut.
An unbundled price is the only price you can challenge.
Document which recovery, copy, and log tasks genuinely need the BMC suite and which native Db2 utilities could cover. Separate real dependence from inherited habit, and cut only on evidence of what is unused.
Pay for the recoveries you run, not the ones you stopped running.
The suite is priced on capacity. Align the licensed MSU to the LPARs that actually run the Db2 workload it protects, and remove capacity that rolled forward from consolidated or retired subsystems.
The capacity nobody uses is the capacity everybody pays for.
Model traditional capacity pricing against zCL consumption and choose on the numbers, and align the close to BMC's fiscal year end where the term allows, so the vendor negotiates against its own quota clock as well as yours.
The model and the quarter are both part of the price.
⑤ The discipline that pays
Recovery tooling is insurance nobody audits between renewals. Unbundle it, map it against native Db2, and the redundant scope becomes the saving, on evidence.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
It is BMC's AMI suite for Db2 backup and recovery, a family of components including BMC AMI Recover, Recovery Manager, Copy, and Log Master under the Recovery Management premium feature, and like most of the BMC mainframe portfolio it is typically licensed on capacity in MSU. The number tracks the MSU of the LPARs the suite is entitled across. Many estates also have the option of BMC zConsumption Licensing, charging on prior year consumption with a year end true up.
In part. IBM ships Db2 for z/OS with native copy, recover, and log utilities, and many estates run the BMC tools for speed, automation, and recovery scenarios the native utilities handle less gracefully. Much of that dependence is genuine, but the overlap means a real alternative exists for some tasks, and mapping which truly need the BMC suite sharpens the renewal.
Rationalizing the component bundle and the MSU footprint. Pricing each component separately, confirming which are in production, aligning the licensed MSU to the LPARs running the Db2 workload, and testing tasks against native Db2 exposes the scope that can be cut, usually the largest source of movement. The caveat is that recovery is insurance, so cut only on evidence of what is unused.
Unbundle the components into separately stated prices, map use against native Db2 utilities, rationalize the MSU footprint, model capacity pricing against zCL, and time the close to BMC's fiscal year end. Cut only on evidence, never on hope, because the saving is never worth a failed recovery. See our BMC publisher hub and our AMI Data for IMS licensing page.
Related: BMC publisher hub · AMI Data for IMS licensing · Negotiating BMC AMI suite bundles · BMC vs Broadcom · BMC roadmap moves · cost optimization
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →