① Journal · BMC
BMC AMI Log Master for Db2 is MSU priced like the rest of the Db2 tooling, but it carries a second question the standalone view misses: is it entitled on its own, or inside the Recovery Management for Db2 suite? The suite position changes both the price and the leverage. That is the negotiation.
Standalone or in the suite. The position is the negotiation.
BMC AMI Log Master for Db2 reads the Db2 log for purposes beyond restart and recovery: logical backout of problem transactions, audit, and data migration, generating reports, SQL, and load files from the log records. It is commonly licensed on mainframe capacity in MSUs, and BMC offers zConsumption Licensing that bills on actual MSU utilization with a true up on overage. So far this is the standard Db2 tooling story. The wrinkle is that Log Master is also a component of the broader Recovery Management for Db2 solution, which integrates it with other recovery and apply tools.
That suite position matters because it changes both the price and the leverage. A bundle can lower the per tool cost if you genuinely use the whole recovery set, or it can quietly carry tools you do not, presented as a single number that is hard to challenge line by line. The buyer who knows exactly which recovery components are load bearing, and prices the standalone product against the suite on that real footprint, controls the number. Add the Db2 capacity baseline on top and the full picture is in view. Read this alongside our AMI Data for Db2 licensing page and the BMC publisher hub.
Log Master for Db2 cost drivers · what each one is and the buyer side lever on it · illustrative, not a quote
| Driver | What it is | Buyer side lever |
|---|---|---|
| Db2 capacity baseline | The MSU capacity and rolling four hour average the charge follows | Reconcile the baseline to the real Db2 footprint |
| Standalone or suite | Log Master alone versus inside Recovery Management for Db2 | Price both on the components you actually use |
| Suite components used | Recovery and apply tools bundled with Log Master | List what is load bearing and drop the rest |
| zConsumption Licensing | Usage based billing on actual MSU utilization | Model fixed capacity against zConsumption and choose on cost |
| Annual escalator | The yearly increase on the recurring charge | Cap the escalator in writing for the full term |
| Tool overlap | Db2 log function duplicated by native or third party tools | Consolidate so one capability is licensed once |
Suite membership and the exact metric follow your specific BMC entitlement and the current BMC AMI Data for Db2 terms; treat the basis as something to read from the contract, not assume. The pattern, that the capacity baseline and the suite position drive the number, is consistent across the estates we see.
The lever unique to Log Master is its suite position. Recovery Management for Db2 bundles it with other recovery and apply tools, and that bundle can help or hide cost. List which recovery components are genuinely load bearing, then price the standalone product against the suite on that real footprint. Decide on the numbers, not on the bundle as presented.
A suite is a deal only if you use the suite.
Log Master is MSU priced, so the contracted capacity and your rolling four hour average on the Db2 estate drive the recurring charge. Reconcile the baseline against the real Db2 footprint and smooth the peak where it makes sense. The recovery function does not change; the capacity it is billed at does, and that is real money recovered without losing protection.
Same protection, lower peak, smaller bill.
zConsumption Licensing bills on actual MSU utilization rather than fixed contracted capacity, which can favor an estate whose Db2 capacity runs below baseline. Do not take the model on the pitch. Build the renewal under both fixed capacity and zConsumption on your real numbers, then choose on cost. A licensing model change is a negotiation event the prepared buyer controls.
Decide the model on math, not on the slide.
Db2 estates often accumulate overlapping tooling, with log analysis, backout, or apply capability available from more than one product or from native Db2 features. At renewal, map where the function genuinely comes from and decide what each tool is for. Consolidating duplicated capability means one function is licensed once, and tightens the baseline the next term builds on.
License each Db2 capability once, not twice.
④ Where the Log Master number is won
A suite is a deal or a trap. Only the footprint tells you. Price the truth, then sign the term.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
On mainframe capacity in MSUs, with BMC AMI Log Master for Db2 reading the Db2 log for backout, audit, and migration beyond restart and recovery. BMC offers zConsumption Licensing that bills on actual MSU utilization. Log Master is also a component of Recovery Management for Db2, so it may be entitled standalone or as part of that suite. Read the exact basis from your entitlement.
The capacity baseline and the suite position. Log Master is MSU priced, so contracted capacity and the rolling four hour average drive the charge. Whether you hold it standalone or inside the recovery suite changes both price and leverage, because a suite number can bundle tools you do not use. Reconciling the Db2 baseline and unpicking the suite are the two largest levers.
Sometimes, but only the numbers tell you. The Recovery Management for Db2 suite bundles Log Master with other recovery tools, which can lower the per tool cost if you use the whole set, or add cost for tools you do not. List which components you actually run, then price standalone against the suite on that real footprint rather than accepting the bundle as presented.
Confirm whether Log Master is entitled standalone or within the suite, list which recovery components are genuinely used, and measure real MSU utilization on the Db2 estate against the baseline. Model zConsumption both ways and press for a written escalator cap. Start twelve to eighteen months out. Our BMC MSU optimization service runs the full play.
Related: AMI Data for Db2 licensing · MainView renewals · Control-M renewals · BMC support escalation · BMC publisher hub · BMC MSU optimization
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →