① Journal · Renewal negotiation
MIM shares DASD, tape, and consoles across the images, which makes it feel like plumbing you cannot touch. Yet part of what it does, z/OS already does for free. Five factors move the renewal, and the one buyers overlook is the alternative they may already own.
MIM is priced on capacity, and on the assumption you have no alternative.
MIM Resource Sharing, from Broadcom (CA), coordinates the safe sharing of DASD, tape, and console resources across z/OS and z/VM images, through components for dataset integrity, tape sharing, and cross-system commands. It is commonly licensed on mainframe capacity measured in MIPS or MSU and metered against a contracted baseline, with a True Forward adjustment where measured capacity runs ahead during the term. The renewal that focuses only on a discount misses the lever that sits in plain sight: IBM (International Business Machines) ships Global Resource Serialization inside z/OS at no additional license, and for much of MIM's dataset serialization role that is a real alternative.
That reframes the exercise. The buyers who win a MIM renewal arrive having validated the contracted capacity and the True Forward exposure, mapped which MIM components they actually run against what GRS already covers, and decided to negotiate MIM inside the wider Broadcom portfolio rather than alone. The five factors below run roughly in order of how much they move, the metering and the alternative first, commercial structure and timing last. Read this with our Broadcom (CA) publisher hub and our explainer on usage pools and aggregation across sysplexes.
Each factor and which direction it moves the MIM bill
| Factor | What it moves | When it pays most |
|---|---|---|
| Contracted capacity | The MIPS or MSU baseline the charge is built on | Before the renewal, against measured consumption |
| True Forward exposure | The overage adjustment for capacity above baseline | Where consumption has crept past the commitment |
| The GRS alternative | Whether part of MIM maps to function already in z/OS | Where dataset serialization is the main MIM use |
| Portfolio bundling | The aggregate leverage of the full Broadcom deal | When MIM is negotiated with the portfolio, not alone |
| Timing and the term | The leverage window and the escalator caps | At the term boundary, before auto renewal |
Capacity metrics, consumption model names, and component coverage change; verify the current ones on your own agreement and against your z/OS configuration at the time of negotiation. The order is the durable part: the metering and the alternative set the floor, and the deal structure and timing price what is left.
MIM is metered against a MIPS or MSU baseline, and the renewal prices that baseline forward. Confirm what the estate actually consumes against what you contracted, because infrastructure products that have run for years often carry capacity sized for an estate that has since changed shape. The baseline you bring into the renewal is the number the escalators compound on, so it should be measured, not assumed.
Renew the capacity you use, not the one you signed.
Where measured capacity runs ahead of the commitment, Broadcom typically reconciles the difference through a True Forward adjustment. That exposure should be measured independently before the renewal, not discovered inside the vendor's reconciliation, because an unvalidated overage becomes a price you accept rather than a number you test.
Measure the overage before the vendor prices it.
IBM Global Resource Serialization ships inside z/OS at no additional license, and GRS Star provides global serialization across an actively coupled Parallel Sysplex. Where MIM is used mainly for dataset integrity, much of that maps to GRS. The honest scope check matters: MIM also handles tape sharing and cross-system commands that GRS does not cover, so the credible alternative depends on which MIM components you actually run. Build that map before the renewal, because it sets what the product is really worth to you.
The alternative you already own is the strongest one.
Most estates running MIM hold a broad Broadcom (CA) footprint under one agreement, governed by the same contracted capacity, the same escalators, and in many cases the Mainframe Consumption Licensing model. Negotiate MIM inside that portfolio renewal so the aggregate spend and the full relationship carry the leverage, rather than letting Broadcom price an infrastructure product alone.
A product priced alone is the vendor's strongest hand.
Leverage exists in a window before the term ends and before auto renewal narrows the options. Start early enough to validate the capacity and build the GRS map, then write escalator caps and consumption protections into the close so a stable estate does not pay a compounding increase for standing still.
Start before the clock favors the vendor.
④ The order that wins
MIM is priced as though you have no alternative. Part of it already ships in z/OS. Map the function, then price what only MIM provides.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
The contracted capacity. MIM is commonly licensed on MIPS or MSU and metered against a baseline, with a True Forward adjustment where consumption runs ahead. Validating that baseline and the overage exposure, not chasing a headline discount, is where the recoverable cost sits.
Partly, depending on use. IBM GRS ships in z/OS at no additional license, and GRS Star serializes globally across a Parallel Sysplex, covering much of MIM's dataset integrity role. MIM also handles tape sharing and cross-system commands that GRS does not, so map your components before assuming a full replacement.
With the portfolio. Most MIM estates hold a broad Broadcom (CA) footprint under one agreement, governed by the same capacity and escalators and, in many cases, the Mainframe Consumption Licensing model. Negotiating it inside the portfolio lets the aggregate spend carry the leverage.
Early enough to validate the capacity and build the GRS map before the term boundary. See our Broadcom (CA) MSU optimization and license negotiation service.
Related: Broadcom (CA) publisher hub · CA 7 renewal · CA View renewal · usage pools and aggregation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →