Move off Endevor without losing forty years of mainframe discipline
Your COBOL, PL/I, and Assembler source has lived in Endevor for decades — and that history matters. We connect it to Git and Dependency Based Build without flattening the promotion path you rely on.
Endevor still works. It just works alone.
Endevor manages your mainframe source with more rigor than most distributed shops ever achieve. The problem isn’t the discipline — it’s the isolation. Your mainframe team works in a different system, with different tools, than everyone else in engineering.
It’s also less automated in practice than it looks on the panel. A base Endevor GENERATE invokes the element Type’s Generate Processor — the JCL that builds only the element you name. Dependency-driven rebuilds do exist — the Autogen option can regenerate the programs that use a changed copybook — but only if your site licensed the separate Automated Configuration (ACM) option, only in batch, submitting that Processor’s JCL as a job, and never inside a package, the governed promotion vehicle most shops actually rely on. Using elements off or below the map are skipped. IBM Dependency Based Build (DBB) makes that same analysis native to every build — including re-linking statically bound load modules — with no separately licensed option and no exclusion from your delivery path.
New developers replacing retiring COBOL veterans have never opened an Endevor panel. They expect branches, pull requests, and a build that only touches what changed. Every day that gap stays open, onboarding gets harder and mainframe work stays siloed.
The migration, in five stages
This isn’t a rip-and-replace. Each stage is a checkpoint you can pause at — and several can run in parallel once the Endevor structure is extracted.
Broadcom’s renewal math doesn’t improve by waiting
Endevor licensing runs through Broadcom, which acquired CA Technologies — and Endevor with it — in 2018. Independent licensing advisories tracking Broadcom’s mainframe portfolio since the acquisition report a consistent pattern: capacity-based contracts (priced by MIPS or MSU) carrying annual escalator clauses, with bundled products that lock customers into paying for tools they don’t use.
None of this is specific to Endevor — it’s the same commercial model applied across Broadcom’s CA mainframe lineup. But it does mean the cost of standing still keeps compounding, while the cost of migrating is fixed and one-time.
Sources: Redress Compliance, “Broadcom Software (CA) Mainframe Licensing: CIO Playbook 2025–2027” and “Broadcom CA Mainframe Pricing” advisories (redresscompliance.com). See the chat response for full citations — verify current figures before publishing.
We’re not a systems integrator selling a multi-year transformation program. We do the migration and the DBB implementation directly — with mainframe engineers who’ve done this before.
Tell us what’s still in Endevor. We’ll tell you what moves first.
A migration assessment maps your current dataset structure against a Git + DBB model — no commitment, no generic sales deck.