Journal · Broadcom (CA) · Telon

Telon renewal negotiation, what actually moves the number.

Telon generated COBOL and PL/I runs natively without any Telon runtime, so a Broadcom (CA) Telon renewal moves on scope and the freeze option, not the list rate. Here are the seven levers that actually shift a Telon renewal, and how each one works.

The list rate is the negotiation people expect. The scope and the freeze are the ones that decide the bill.

Broadcom (CA) Telon, the application generator that translates design facility definitions into COBOL, COBOL II, or PL/I source, is licensed on mainframe capacity measured in MSU, increasingly under the Broadcom Mainframe Consumption Licensing model. But the fact that reorders a Telon renewal is structural: the generated code runs natively without any Telon runtime, so the license buys the ability to generate and regenerate, not the right to run the applications. Buyers expect to argue the rate card, but the number on a Telon renewal moves on how much ongoing generation capacity the estate actually needs, the capacity baseline, and the freeze option that the runtime independence makes credible.

Around scope sit the structural levers: the capacity baseline and how it is set, the uplift cap, the in term escalator, the way Telon is often carried inside a portfolio deal, and the freeze where you stop generating and maintain the existing source directly. Each is decided on independently validated consumption data and an honest read of the development roadmap, because paying full price for change capability the estate no longer uses is the most common form of overspend here. Read this with our COBOL compiler renewal piece and the Broadcom (CA) publisher hub.

Seven levers and what each one moves

What we commonly observe · the lever and how it shifts the Telon number

LeverHow it worksWhat it moves
Separate generation from execution Generated code runs without Telon, so license change only What you actually need the license for
Scope to active development Match the license to real Telon generation, not legacy reach The capacity you must license at all
Price the freeze option Stop generating, maintain the existing source directly The captive assumption behind the renewal
Right size the capacity baseline Set the contracted MSU on validated consumption, not a peak The floor the whole renewal is built on
Cap the renewal uplift A hard ceiling on the increase against a fixed reference The size of the jump at signing
Unbundle the line item Pull Telon out of the portfolio deal and price it alone What you are actually paying for
Validate the consumption data Independent check of the reported MSU figures The accuracy of the number everything rests on

Levers are what we commonly observe working across buyer side engagements, not statements of Broadcom policy, and the effect of each depends on your development roadmap. Your consumption data, scope, and contract govern the real number.

Three levers that move it most

№ 01

License change, not the running estate

Telon produces standard COBOL or PL/I source that compiles and runs natively, with no proprietary runtime to license. The running applications do not depend on the tool. What the license buys is the ability to generate and regenerate, which means you only need it for the parts of the estate under active Telon development. Confining the license to genuine change capability, not the full legacy reach, is the largest structural lever here.

You license the act of generating, not the code already generated.

№ 02

Price the freeze and make it credible

Because Telon applications keep running without the tool, a freeze, where you stop generating and maintain the existing source directly, is a defensible alternative to a full price renewal. It is not always the right operational call, but pricing it makes the captive assumption negotiable. The freeze reframes the renewal from an open ended commitment to a question of how much ongoing generation is worth, and that question is where the number moves.

A freeze you can price is leverage the vendor has to answer.

№ 03

Set the floor and pull it from the bundle

The contracted capacity is the floor every other term is built on, so set it on validated consumption rather than a peak, then cap the uplift against a fixed reference. Telon is often carried inside a larger portfolio deal where the line is easy to lose, so pull it out and price it on its own consumption. Unbundling exposes whether you are paying for generation capacity or for cover the single number provides.

Set the floor on data, then see the line on its own.

Where the Telon number is moved

The list rate is the argument you expect. The scope, the freeze, the baseline are the ones that count. License the change, price the freeze, set the floor.

20 to 35%

Typical reduction negotiated on renewal spend

$180M+

Mainframe spend negotiated on the buyer side

500+

Engagements delivered since 2019

Frequently asked questions

Q1

What drives the Telon bill the most?

Telon is licensed on mainframe capacity in MSU, increasingly under Broadcom Mainframe Consumption Licensing, but the structural fact is that generated code runs without any Telon runtime. You license the ability to generate and change, not to run, so scope and the freeze option move the number. See MIPS and MSU explained.

Q2

Do Telon applications keep running without a license?

The generated programs do. Telon produces standard COBOL or PL/I source that compiles and executes natively, with no proprietary runtime. The license buys the ability to generate and regenerate, so a frozen estate keeps running while the renewal question becomes how much change capability you still need. See COBOL compiler renewal negotiation.

Q3

How does a freeze help a Telon negotiation?

Because the applications run without the tool, a credible freeze, where you stop generating and maintain the existing source directly, is a defensible alternative to a full price renewal. Pricing it makes the captive assumption negotiable. The freeze is leverage, not necessarily the operational plan. See competitive alternatives as leverage.

Q4

How do you negotiate a Telon renewal?

Separate generation from execution, scope to active development, price the freeze, right size the baseline, cap the uplift, and unbundle the line item. Our license negotiation service sets the structure and our cost optimization validates the scope. See also Broadcom (CA) price increase patterns.

Related: Broadcom (CA) publisher hub · COBOL compiler renewal negotiation · IDMS renewal negotiation · Broadcom (CA) price increase patterns · license negotiation

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

Get expert help

Facing a Telon renewal? We move the number on scope and the freeze, not the list.

Get expert help