Product · Broadcom (CA) MICS

MICS licensing: the warehouse is large, the metric is capacity.

MICS Resource Management is Broadcom (CA) performance data management, the warehouse that turns SMF data into capacity and chargeback reporting. It is licensed on system capacity in MIPS or MSU and moving toward consumption, so the lever is the capacity baseline and the component set, not the size of the data store.

№ 01

What it is

Performance warehouseSMFz/OS

MICS Resource Management is Broadcom (CA) performance and capacity data management software. It collects SMF and other system instrumentation data, organizes it into a structured warehouse, and turns it into the performance analysis, capacity planning, and chargeback reporting that operations and capacity teams rely on. It is one of the long standing data warehouses on the platform, deeply wired into reporting and billing processes that have run for years, which makes it both valuable and hard to move. That embedded position shapes how its licensing should be approached.

№ 02

How it is licensed

CapacityMIPS or MSUMCL

MICS is licensed on capacity, not on the volume of data its warehouse holds. Historically that has meant a MIPS or MSU based charge tied to the machines or LPARs where the product runs, and Broadcom has been moving its mainframe customers toward Mainframe Consumption Licensing (MCL), which prices on measured MSU consumption reported through SCRT across the production environment. MICS also ships as a base product with optional component units for different data sources, so the entitlement is really a base plus a set of components. Whether your MICS license is a legacy capacity entitlement or sits under a consumption agreement depends on your contract, and the component mix needs to be read alongside the capacity basis.

MICS licensing at a glance
AttributeDetail
PublisherBroadcom (CA)
FunctionPerformance and capacity data warehouse from SMF data
Charge modelCapacity license, MIPS or MSU based
StructureBase product plus optional component units
DirectionMainframe Consumption Licensing (MCL), MSU consumption
№ 03

Cost drivers

CapacityComponentsPortfolio

The first driver is the licensed capacity baseline, which can drift above current need when it was set before a hardware upgrade and never revisited. The second is the component set, because MICS components for different data sources accumulate over time and some end up entitled but unused. The third is portfolio context, since Broadcom renews its mainframe products together and uplift pressure on the full CA estate flows through to MICS. The MIPS to MSU conversion underlies all three, because a transition done on the vendor's assumptions can quietly raise the licensed position. The size of the warehouse itself is a storage concern, not a license driver.

№ 04

Audit traps

ComponentsScopeNon-prod

MICS exposure comes from its component structure and its breadth. Common traps we see at pattern level:

Where exposure hides

  • Component units enabled or in use beyond what the entitlement actually covers
  • The product running on LPARs or machines beyond licensed capacity after a hardware upgrade
  • Test, development, and disaster recovery instances assumed covered when the contract treats them separately
  • Capacity figures that grew with the estate while the license baseline was never revisited
  • SCRT consumption under an MCL agreement that does not reconcile to your licensed position
№ 05

Renewal levers

5 levers

MICS responds to the portfolio levers, applied with its component structure in mind. The five that pay:

Buyer side levers

  • Prune the components: confirm which MICS component units are actually used and drop those that are entitled but idle
  • Validate the capacity baseline: match the licensed MIPS or MSU figure to current need, not the historical peak
  • Control the conversion: when moving from MIPS to MSU or consumption, validate the conversion factor and baseline independently
  • Anchor an alternative: evaluate an MXG based warehouse or comparable approach to give the renewal a credible reference point
  • Negotiate in portfolio and on time: position MICS inside the full CA renewal and open it 18 months out
№ 06

Alternatives, where credible

Reality check

Performance data warehousing has a real alternative market, most notably MXG, the SAS based performance database that many shops run instead of or alongside MICS, plus other capacity and reporting platforms. Displacement is credible leverage, but it is not free: years of historical data, the reports built on the warehouse, and the chargeback and capacity processes that consume them all have to be rebuilt or repointed, and that is a project with its own cost and risk. The practical move is usually to prune unused components and use a credible alternative as a reference point in the Broadcom renewal, reserving a full migration for cases where the long term saving clearly justifies the effort.

№ 07

Frequently asked

FAQ
Q1
How is MICS licensed?On system capacity, historically MIPS or MSU based, with Broadcom moving customers toward Mainframe Consumption Licensing on measured MSU via SCRT. It is a base plus optional components, so confirm both.
Q2
Does data volume drive cost?Not through the license metric, which follows system capacity. Warehouse size is a storage concern. The lever is the capacity baseline, the component set, and the contract.
Q3
Where does audit exposure sit?In components and scope: component units beyond entitlement, the product on LPARs beyond capacity, non production assumed covered, and SCRT that does not reconcile under MCL.
Q4
What moves the number?Pruning unused components, validating the capacity baseline and conversion, anchoring an alternative such as MXG, and negotiating inside the full CA portfolio on time.

Prune the components, validate the capacity, then renew.

Audit notice or renewal under 18 months out? We mobilize within 48 hours.

Pay for the components you run. We find the idle ones.

Get expert help