① Journal · IBM · OMEGAMON · Renewal
The IBM Z OMEGAMON monitoring family is an IPLA product, so the renewal is not a monthly meter, it is a licensed capacity and a recurring Subscription and Support fee. The number moves when you right-size the entitlement to what you actually monitor and hold the annual uplift. Five levers move it.
OMEGAMON is licensed capacity plus recurring support. Right-size the entitlement and you move the price.
IBM Z OMEGAMON is the monitoring family that watches z/OS, CICS, Db2, IMS, networks and storage, and it is licensed under the International Program License Agreement (IPLA): a one-time charge for the entitlement plus an annual Subscription and Support (S&S) fee. The entitlement is sized in Value Units converted from MSU (Million Service Units) of licensed capacity, and the products are sub-capacity eligible, so the capacity that sets the charge can be the sub-capacity MSU the monitored LPARs run rather than the full machine. That structure changes where the renewal is won. Unlike a Monthly License Charge (MLC) subsystem, where the bill chases the rolling four hour average, an OMEGAMON renewal turns on two things you control directly: how much capacity you are entitled for, and what you pay in recurring support against it.
The pattern we commonly observe is that estates carry more OMEGAMON entitlement than they monitor, accumulated across years of acquisitions and component additions, and that the recurring S&S compounds quietly until a renewal forces the question. The buyers who move the number arrive with a component by component inventory of what is actually deployed, an entitlement right-sized to the sub-capacity MSU monitored, and a credible alternative on the table. Around the capacity and support levers sit three more: consolidating the monitoring stack, benchmarking against a real competitor, and offloading eligible work to zIIP. Read this with our explainer on contractual MSU vs consumed MSU and the IBM publisher hub.
What moves the number on an IBM Z OMEGAMON renewal · the lever and its effect
| Lever | How it works | Effect on the number |
|---|---|---|
| Sub-capacity value units | Price the entitlement on the sub-capacity MSU the monitored LPARs run, not the full box | Lowers the Value Units the renewal charges |
| Stack consolidation | Drop or merge OMEGAMON components and agents you no longer monitor with | Removes whole line items from the renewal |
| S&S scrutiny | Challenge the annual Subscription and Support uplift on each entitlement | Holds the recurring cost that compounds |
| Competitive benchmark | MainView and SYSVIEW are credible monitoring alternatives | Caps the renewal against a real switch |
| zIIP offload | OMEGAMON offloads eligible work to zIIP specialty engines | Lowers the general purpose MSU footprint the license tracks |
These are levers and patterns we commonly observe on OMEGAMON and the wider IBM IPLA monitoring stack, not guaranteed outcomes. The effect of each depends on your entitlement, contract, and deployment; inventory your actual components and capacity before relying on any figure.
OMEGAMON is licensed per component across z/OS, CICS, Db2, IMS, networks and storage, and estates routinely carry more entitlement than they deploy. Inventory every component, map it to the LPARs and subsystems actually monitored, and price the entitlement on the sub-capacity MSU those LPARs run rather than the full machine. The Value Units fall when the licensed capacity matches the monitored capacity. See our explainer on the MSU baseline and how to reset it.
License what you monitor, not what you own.
The recurring number on an IPLA product is the annual S&S, and it is the cost that compounds across a multi year term. Challenge the uplift on each entitlement, decline reinstatement charges on lapsed components you intend to drop rather than revive, and tie the support level to the components you keep. The recurring line is where a renewal quietly grows, so it is where the discipline pays. See our explainer on MSU explained.
The recurring fee is the renewal you live with.
OMEGAMON does not negotiate in a vacuum. BMC MainView and Broadcom (CA) SYSVIEW are credible monitoring alternatives, and a modeled switch, even one you do not execute, caps the renewal against a real number. Pair the benchmark with zIIP offload, which moves eligible monitoring work off the general purpose engines and lowers the MSU footprint the license tracks. A credible alternative is leverage whether or not you ever leave. See our CICS renewal negotiation piece.
Model the switch, then negotiate from it.
④ Where the OMEGAMON renewal is won
An OMEGAMON renewal is licensed capacity and recurring support. Both are yours to right-size before the table. Inventory the stack, hold the S&S, benchmark the switch.
Typical renewal reduction
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
OMEGAMON is licensed under IPLA as a one-time charge plus annual Subscription and Support. The charge is set in Value Units derived from MSU of licensed capacity, and the products are sub-capacity eligible, so the capacity that drives the price can be the sub-capacity MSU the monitored LPARs run. Because OMEGAMON is licensed per component across z/OS, CICS, Db2, IMS, networks and storage, the renewal is the sum of those line items plus recurring S&S on each.
The licensed capacity and the recurring support. Pricing OMEGAMON on the sub-capacity MSU the monitored LPARs actually run lowers the Value Units charged, and consolidating the stack by dropping unused components removes line items entirely. Beyond that, scrutinizing the annual S&S holds the recurring cost, a benchmark against MainView or SYSVIEW caps the renewal, and zIIP offload lowers the general purpose MSU footprint the license tracks.
OMEGAMON is an IPLA product, not an MLC subsystem. It carries a one-time charge for the entitlement and a separate annual S&S fee, rather than a monthly bill that follows the rolling four hour average. The entitlement is sized in Value Units converted from MSU, and sub-capacity terms can apply. At renewal the recurring number to negotiate is the S&S, and the entitlement to right-size is the licensed Value Unit capacity against what you actually monitor. See Linux on IBM Z renewal negotiation.
We inventory the OMEGAMON stack component by component, right-size the entitlement to the sub-capacity MSU you actually monitor, challenge the S&S uplift, and build the competitive benchmark before the vendor controls the clock. Our IBM MSU optimization service shapes the capacity the license builds on and our renewal advisory service runs the negotiation from the buyer side.
Related: IBM publisher hub · CICS renewal negotiation · Linux on IBM Z renewal negotiation · contractual vs consumed MSU · IBM MSU optimization · renewal advisory
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →