How are CA 1 and IBM DFSMSrmm licensed differently?

CA 1 Tape Management is a standalone Broadcom (CA) product, licensed on mainframe capacity and commonly migrating from a MIPS basis to MSU under Broadcom Mainframe Consumption Licensing, with its own renewal cycle, its own support stream, and its own audit exposure. IBM RMM, properly DFSMSrmm, is a priced optional feature of DFSMS within z/OS, enabled in IFAPRDxx and charged through the z/OS Monthly License Charge stack on the same sub-capacity R4HA basis as the rest of your MLC software. The practical difference is structural: CA 1 is a separately negotiated vendor line item, while DFSMSrmm folds tape management into the IBM bill you already report through SCRT.

Is CA 1 or DFSMSrmm cheaper?

It depends entirely on the rest of your estate, not on a published rate. For an estate already consolidating onto IBM, converting CA 1 to DFSMSrmm removes a Broadcom line item and its renewal uplift risk, and the incremental MLC cost of enabling the feature can be modest against the savings. For a Broadcom heavy estate already committed to a large consumption baseline, CA 1 may carry little marginal cost inside the bundle, and pulling it out earns nothing. The cheaper option is the one that strengthens the negotiation you are already having, which is why the tape tool is best priced as part of the wider portfolio decision rather than in isolation.

Is it worth converting from CA 1 to DFSMSrmm?

Conversion is technically well trodden, with utilities documented in both directions, but it is real work: the tape catalog, retention and vaulting rules, vital record specifications, and the batch and automation built around the incumbent all carry across with care. The case for converting is strongest when it removes a Broadcom renewal you no longer want exposure to, or when an IBM agreement makes the feature effectively free at the margin. The case against is the migration effort and the operational risk of changing the system of record for every tape in the estate. For most buyers the conversion threat is most valuable as prepared leverage on a CA 1 renewal, made credible by a costed migration plan, rather than as a project run for its own sake.

CA 1 vs IBM RMM: Tape Management Licensing

CA 1 vs IBM RMM: a Broadcom line item against your z/OS bill.

Broadcom (CA) CA 1 Tape Management and IBM DFSMSrmm do the same job: catalog, retain, and vault every tape in the estate. The licensing could not be more different. One is a separately negotiated Broadcom product on a capacity charge. The other is a priced feature of z/OS that folds into the MLC stack you already report. That structure, not the feature list, decides the cost.

Decide on the contract structure, not the tape function. CA 1 and DFSMSrmm both manage tape catalogs, retention, scratch pools, and vaulting competently, so neither wins on capability alone. What separates them is where the cost lands. CA 1 is a standalone Broadcom (CA) product with its own renewal, its own support stream, and its own audit exposure. DFSMSrmm is a priced feature of z/OS DFSMS that charges through your existing MLC sub-capacity bill. For an estate consolidating onto IBM, converting to DFSMSrmm retires a Broadcom line item. For a Broadcom committed estate, CA 1 may cost little at the margin inside the bundle. Price the tool inside the portfolio decision, never on its own.

CA 1 vs IBM DFSMSrmm, the licensing levers compared
Dimension	Broadcom (CA) CA 1	IBM RMM (DFSMSrmm)
Vendor	Broadcom (CA)	IBM
Product form	Standalone tape management product	Priced optional feature of DFSMS in z/OS
Licensing basis	Mainframe capacity, MIPS migrating to MSU	z/OS MLC sub-capacity, R4HA via SCRT
Contract vehicle	Commonly Broadcom Mainframe Consumption Licensing	Folded into the IBM MLC agreement
Where the bill lands	Separate Broadcom renewal and invoice	Inside the existing z/OS MLC report
Audit exposure	Its own review cycle and entitlement record	Reported through SCRT with the MLC stack
Conversion path	Utilities to and from DFSMSrmm exist	Utilities to and from CA 1 exist
Third option	BMC Control-M/Tape	BMC Control-M/Tape

CA 1 vs IBM DFSMSrmm, the licensing levers compared

Dimension

Broadcom (CA) CA 1

IBM RMM (DFSMSrmm)

Vendor

Broadcom (CA)

IBM

Product form

Standalone tape management product

Priced optional feature of DFSMS in z/OS

Licensing basis

Mainframe capacity, MIPS migrating to MSU

z/OS MLC sub-capacity, R4HA via SCRT

Contract vehicle

Commonly Broadcom Mainframe Consumption Licensing

Folded into the IBM MLC agreement

Where the bill lands

Separate Broadcom renewal and invoice

Inside the existing z/OS MLC report

Audit exposure

Its own review cycle and entitlement record

Reported through SCRT with the MLC stack

Conversion path

Utilities to and from DFSMSrmm exist

Utilities to and from CA 1 exist

Third option

BMC Control-M/Tape

Because the tools are close in function, this is a portfolio and leverage decision. Use it this way:

Convert to DFSMSrmm if

You are consolidating onto IBM and want to retire a Broadcom line item with its own renewal uplift risk
An IBM agreement makes enabling the feature modest at the margin against the Broadcom cost removed
You want tape management reported inside the MLC stack you already validate through SCRT rather than as a separate audit surface

Keep CA 1 if

You hold a large Broadcom consumption baseline where the tape tool carries little marginal cost inside the bundle
The automation, retention rules, and operational muscle memory built around CA 1 make a conversion's risk outweigh the saving
You would rather hold the conversion as prepared leverage on the Broadcom renewal than spend the project budget now

Either way, the first move is to reconcile what you actually run against what you are entitled to, separate the tape tool cleanly enough to price it on its own, and cost the conversion both ways before you decide or before you threaten to move.

How are they licensed differently?CA 1 is a standalone Broadcom product on a capacity charge, MIPS migrating to MSU under consumption licensing. DFSMSrmm is a priced feature of z/OS, charged through the MLC sub-capacity stack via SCRT.

Which is cheaper?It depends on the estate. Converting to DFSMSrmm removes a Broadcom line item for an IBM consolidating shop; CA 1 may cost little at the margin inside a large Broadcom baseline. Price it inside the portfolio.

Is conversion worth it?Technically well trodden in both directions, but it changes the system of record for every tape. Best run when it retires unwanted Broadcom exposure, or held as costed leverage on a CA 1 renewal.

What decides the cost?The contract structure and the wider portfolio, not the tape function. Whether the charge is a separate Broadcom renewal or folded into your z/OS MLC bill is the lever that moves the number.

Same tapes, different bill. The structure sets the price.

Explainers: cost per MSU benchmarks and drivers and decommissioning credits and license retirement. Sibling product: TLMS licensing. Other comparisons: File-AID vs CA File Master and Broadcom MCL vs traditional MIPS licensing. Hubs and commercial: the Broadcom (CA) buyer side guide, the IBM buyer side guide, Broadcom (CA) MSU optimization, and IBM mainframe cost optimization.

CA 1 vs IBM RMM: a Broadcom line item against your z/OS bill.

The verdict

Head to head

Who should pick which

Frequently asked

A credible conversion disciplines the renewal. We cost the move.