① Journal · IBM · CICS · Renewal
CICS Transaction Server is one of the larger MLC subsystems on most z/OS estates, so its peak drives a real share of the monthly bill. A CICS renewal is not won at the table, it is won in the months before, by shaping the rolling four hour average that the price follows. Five levers move the number.
A CICS renewal follows the rolling four hour average. Shape the peak and you move the price.
CICS Transaction Server (CICS TS) for z/OS is licensed under Monthly License Charge (MLC), and under sub-capacity it is billed on the rolling four hour average (R4HA) of MSU (Million Service Units) consumption, reported each month through the Sub-Capacity Reporting Tool (SCRT). The detail that decides a CICS renewal is that CICS is one of the heaviest MLC subsystems on a typical estate, so its peak contributes heavily to the combined R4HA that sets the bill. That makes the renewal a measurement problem before it is a pricing problem. The number you negotiate is downstream of the peak you ran, and the peak is shaped in the months before the renewal, not in the room. The buyers who move a CICS renewal are the ones who arrive with a measured, optimized R4HA profile and a credible alternative, not a request for a discount on whatever the meter happened to record.
The pattern we commonly observe is that the largest, most durable savings come from the R4HA itself, through defined capacity and soft capping, and that the table conversation only ratifies what the profile already shows. Around that sit four more levers: modeling CICS under Tailored Fit Pricing as both an option and a benchmark, harvesting the technology dividend that newer processors deliver, offloading eligible work to zIIP specialty engines, and scheduling discretionary work away from the monthly peak window. Read this with our explainer on soft capping and defined capacity and the IBM publisher hub.
What moves the number on a CICS Transaction Server renewal · the lever and its effect
| Lever | How it works | Effect on the number |
|---|---|---|
| R4HA peak shaping | Defined capacity and soft capping hold the rolling four hour average | Lowers the billed MSU directly, the largest durable lever |
| Tailored Fit Pricing | Model CICS under the Software Consumption baseline and carry forward | Can convert volatile peaks into a predictable baseline |
| Technology dividend | Newer processors carry lower MSU ratings for the same work | Reduces measured MSU on a hardware refresh |
| zIIP offload | Move eligible work to zIIP specialty engines | Lowers the general purpose capacity that drives the R4HA |
| Workload scheduling | Shift discretionary work off the monthly peak window | Lowers the peak that sets the monthly bill |
These are levers and patterns we commonly observe on CICS and the wider MLC stack, not guaranteed outcomes. The effect of each depends on your workload profile, contract, and configuration; model against your own SCRT data before relying on any figure.
The bill follows the R4HA, so the renewal is won by the profile you bring to it. Use defined capacity and soft capping to hold the peak across the LPARs CICS runs on, validate the result in your own SCRT data, and walk into the renewal with a measured, optimized profile rather than whatever the meter recorded. Every other lever works on top of this one. See our explainer on the MSU baseline and how to reset it.
Optimize the peak before you negotiate the price.
Tailored Fit Pricing Software Consumption sets an annual MSU baseline and prices consumption against it, with unused capacity typically carried forward, which suits volatile or growing estates better than flat ones. Model CICS and the rest of the MLC stack under both traditional sub-capacity and TFP, then carry the comparison into the negotiation whether or not you adopt it. A modeled alternative is leverage even when you stay where you are. See our explainer on Tailored Fit Pricing.
Model the alternative, then negotiate from it.
A hardware refresh delivers a technology dividend, because newer processors carry lower MSU ratings for the same work, which lowers measured CICS MSU if the renewal timing is aligned to it. zIIP offload moves eligible work off the general purpose engines that drive the R4HA. Together they reduce the measured profile the price builds on, and aligning a renewal to a refresh window compounds the effect. See our explainer on Parallel Sysplex aggregation and pricing.
Align the renewal to the refresh and the offload.
④ Where the CICS renewal is won
A CICS renewal is downstream of the peak you ran. The number moves in the months before the table. Shape the R4HA, model TFP, harvest the dividend.
Typical renewal reduction
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
CICS TS for z/OS is a Monthly License Charge product. Under sub-capacity it is billed on the rolling four hour average of MSU consumption, reported each month through SCRT. Because CICS is one of the larger MLC subsystems on most z/OS estates, its peak contributes heavily to the combined R4HA that sets the monthly bill, which is why shaping that peak moves the number.
The single largest lever is the rolling four hour average peak, because the bill follows it. Defined capacity and soft capping lower the billed MSU directly. Beyond that, modeling CICS under Tailored Fit Pricing can convert volatile peaks into a predictable baseline, the technology dividend on a hardware refresh reduces measured MSU, zIIP offload lowers the general purpose capacity that drives the R4HA, and scheduling discretionary work off the peak window lowers the peak.
It depends on the workload profile. Tailored Fit Pricing Software Consumption sets an annual MSU baseline and prices consumption against it, with unused capacity typically carried forward, which suits volatile or growing estates better than stable ones. Model CICS and the rest of the MLC stack under both traditional sub-capacity and TFP, and treat TFP as a benchmark whether or not you adopt it. See OMEGAMON renewal negotiation.
We validate your SCRT and R4HA profile independently, model CICS under sub-capacity and Tailored Fit Pricing, align the renewal to any hardware refresh, and build the credible alternative before the vendor controls the clock. Our IBM MSU optimization service shapes the peak the renewal builds on and our renewal advisory service runs the negotiation from the buyer side.
Related: IBM publisher hub · OMEGAMON renewal negotiation · Linux on IBM Z renewal negotiation · IBM MSU optimization · renewal advisory
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →