Home / Broadcom (CA) / CA Panvalet Licensing
① Product · Broadcom (CA)
CA Panvalet is a source library tool from 1969 still billing on modern capacity. On a declining legacy product, the renewal levers are unusually strong. Here is how it is licensed and what to pull, from the buyer side.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →CA Panvalet is a source code and library management system for z/OS and z/VSE, originally built by Pansophic Systems in 1969, acquired by Computer Associates in 1991, and now part of the Broadcom (CA) portfolio after the 2018 acquisition. It establishes and protects a control library of source programs, JCL, macros, and card image data, including the source and macros for utilities such as Easytrieve. Its age is the point: in many shops it survives only because legacy assets still live inside it, which shapes the entire licensing conversation.
CA Panvalet is licensed on mainframe capacity within the Broadcom (CA) portfolio. The legacy basis is a MIPS entitlement enforced through CA License Management Program, or LMP, keys tied to the processor complex. Broadcom has been moving customers toward Mainframe Consumption Licensing, or MCL, priced on actual MSU consumption. Because Panvalet is a mature, low footprint tool, it almost always sits inside the wider portfolio agreement rather than carrying a standalone metric, so the renewal lever is the portfolio structure, not the product alone.
| Element | How CA Panvalet is treated |
|---|---|
| Legacy basis | MIPS capacity, enforced by LMP keys |
| Current direction | Mainframe Consumption Licensing on MSU |
| Deal level | Portfolio agreement, not standalone |
| Product status | Mature legacy, replaceable function |
| Term | Multi year, with renewal uplift pressure |
Directional summary. The basis on a given contract depends on whether you have moved to consumption licensing.
Three drivers set the Panvalet number. The capacity basis, legacy MIPS on the rated complex or consumption MSU on actual use, which can value the same estate very differently. The portfolio uplift, because Broadcom (CA) commonly raises the bundle as a whole and Panvalet rides that increase even when its own usage is flat or falling. And inertia, because a 1969 vintage library tool is rarely reviewed, so it keeps drawing capacity charges long after the workload that justified them has shrunk. On a declining product, that inertia is the cost, and removing it is the saving.
The recurring traps are about paying for the past. Capacity entitlement larger than the estate Panvalet now runs on after consolidation or migration. The product carried across LPARs where the libraries are effectively dormant but the entitlement persists. And a portfolio renewal uplift that lifts Panvalet along with everything else even though its usage has declined for years. Legacy tools like this are the least likely to be rebaselined, so they are exactly where reconciling entitlement to reality, the same discipline used on version charging, surfaces money.
Panvalet is one of the cleaner products to push hard on, because the function is replaceable. Rebaseline the capacity it is licensed against to where it actually runs. Build a credible migration path off it to a modern source control system, which weakens the vendor's switching cost assumption even if you do not execute it this cycle. Refuse a blanket portfolio uplift on a declining legacy product, and negotiate Panvalet as one line in the bundle rather than accepting per product pricing. Where the libraries can be retired outright, elimination beats any renewal. This is the buyer side work we do on Broadcom (CA) cost optimization.
CA Panvalet is licensed on mainframe capacity within the Broadcom (CA) portfolio. The legacy basis is a MIPS entitlement enforced through CA License Management Program keys, and Broadcom has been moving customers to Mainframe Consumption Licensing priced on actual MSU. As a mature source library tool it almost always sits inside the wider portfolio agreement rather than carrying a standalone metric.
That is the real question on a product first written in 1969. Many estates keep Panvalet only because legacy source, JCL, and Easytrieve macros still live in it. Where the libraries can be migrated to a modern source control system, the function is replaceable, which makes Panvalet one of the clearer candidates for elimination or hard renewal pressure rather than an automatic renewal.
The common traps are capacity entitlement larger than the estate Panvalet now runs on, the product carried across LPARs where the libraries are dormant, and a portfolio renewal uplift that lifts Panvalet along with everything else even though usage has declined. Legacy tools are rarely rebaselined, so they often pay for capacity the business reduced years ago.
Rebaseline the capacity Panvalet is licensed against to where it actually runs, build a credible migration path off it to weaken the vendor's switching cost assumption, refuse a blanket portfolio uplift on a declining legacy product, and negotiate it as one line in the bundle rather than accepting per product pricing.
Publisher hub: Broadcom (CA) mainframe licensing. Related products: CA 11 licensing and NetMaster licensing. Related metric: Single Version Charging. Put it to work: Broadcom (CA) cost optimization.