TELON migration

Automated TELON migration

Preserve proven business logic while removing vendor dependencies, simplifying maintenance and enabling future modernization.

Abstract illustration of legacy systems moving to the cloud

Why modernize?

CA Telon accelerated development for batch and online workloads by generating COBOL, but today organizations face rising vendor costs, limited TELON skill sets, and integration constraints. An automated Telon-to-COBOL migration preserves proven business logic while removing vendor dependencies, simplifying maintenance, and enabling future modernization.

Reduce cost & risk

Lower license and platform spend; eliminate single-vendor lock-in.

Improve maintainability

Readable, documented COBOL with standard copybooks and clear I/O layers.

Enable modernization

Adopt CI/CD, SQL data access, API integration and cloud-ready deployment patterns.

Automated approach

  1. Discovery & inventory. Parse Telon models, procs, maps, JCL and external dependencies to build a comprehensive catalog.
  2. Static analysis. Identify data structures, copybooks, database calls, screen flows and cross-program dependencies.
  3. Code generation. Produce structured COBOL with modular I/O, replacing Telon constructs and generator artifacts.
  4. Data access modernization. Optionally replace Datacom/IDMS/VSAM calls with SQL (Db2, SQL Server or Oracle), or retain existing access patterns when required.
  5. Build & JCL updates. Generate or update compile/bind steps, link-edit and JCL to align with target runtimes.
  6. Test harness & equivalence. Create automated test cases and parallel runs that compare reports, files and key metrics.
  7. Tuning & cutover support. Optimize performance, finalize runbooks and assist with production transition.

Automation accelerates delivery while keeping IT resources in the loop for exception handling and business-rule validation.

What you receive

  • Generated COBOL source code and standardized copybooks
  • Documentation of data structures, screens/flows and external interfaces
  • JCL updates, build scripts and deployment runbooks
  • Optional SQL DDL and data-migration utilities for RDBMS targets
  • Executive summary with risks, metrics and roadmap

Take the next step

Ready to evaluate a Telon-to-COBOL path? Let’s start with a brief discovery session.