S/MF
StackMF Knowledge Base • z/OS
Modernisation & Cloud 11 min read 2026-09-27

Migrating CA-Telon Batch Drivers and TDF Panels into Modular Enterprise COBOL 6.x

A
Reviewed by Anshu
Chief Technology Architect & Mainframe Systems SME
Enterprise Modernization Advisory
Google AI Overview & Featured Snippet Quick Answer

Executive Summary: Migrating CA-Telon Batch Drivers and TDF Panels into Modular Enterprise COBOL 6.x

Eliminate proprietary Broadcom CA-Telon batch drivers and generated spaghetti code. Discover how to extract business logic from Telon Development Facility (TDF) tables, eliminate the TLNMAIN driver, and refactor into clean, modern COBOL 6.x.

1 Problem Statement & Architecture Context: Migrating CA-Telon Batch Drivers and TDF Panels into Modular Enterprise COBOL 6.x

Enterprises trapped in CA-Telon spend millions in support fees for an obsolete 4GL tool. Batch reporting programs generated by Telon contain obfuscated driver loops that prevent optimization and block migration to modern DevOps CI/CD.

2 Technical Root Cause & Architecture Mechanics

CA-Telon batch programs do not contain clean standard PROCEDURE DIVISION logic:

  • Execution is driven by the proprietary Telon batch driver module (TLNMAIN).
  • Program logic is split into generated paragraphs (PG100, PG200) interspersed with proprietary Telon internal flags (TLN-EOF, TLN-ERR).
  • Compiling requires proprietary Telon macro libraries and pre-compilers.

3 Implementation Guide & Modernization Strategy

# 1. Reverse-Engineer the Telon Execution Loop

Examine the Telon driver structure:

text
TLNMAIN -> Initializes Telon buffers -> Calls generated module
        -> Handles I/O via Telon Access Modules -> Loops until TLN-DONE

# 2. Extract Business Logic into Pure Native COBOL

Extract validation rules and calculation logic from custom Telon exit sections (CUSTOM SECTION / MOD-SECT), eliminating all TLN* prefixes:

cobol
IDENTIFICATION DIVISION.
       PROGRAM-ID. BILLING01.
       ENVIRONMENT DIVISION.
       INPUT-OUTPUT SECTION.
       FILE-CONTROL.
           SELECT BILL-FILE ASSIGN TO BILLDD
                  ORGANIZATION IS SEQUENTIAL
                  FILE STATUS IS WS-BILL-STATUS.

       PROCEDURE DIVISION.
       0000-MAIN.
           OPEN INPUT BILL-FILE
           PERFORM UNTIL WS-BILL-STATUS = '10'
               READ BILL-FILE
                   AT END MOVE '10' TO WS-BILL-STATUS
                   NOT AT END PERFORM 1000-PROCESS-RECORD
               END-READ
           END-PERFORM
           CLOSE BILL-FILE
           GOBACK.

# 3. Recompile with Enterprise COBOL 6.4

Compile using modern IBM compiler flags (OPT(2),ARCH(14)), completely eliminating Broadcom Telon license dependencies!

Technical Specifications Matrix

Attribute Specification
Target Environment IBM z/OS • Modernisation & Cloud
Key Technologies Telon, CA-Telon, COBOL
Delivery SLA Accelerated Sprint Delivery via StackMF Pods
Technical Reviewer Anshu, Chief Technology Architect • StackMF Architecture Pod

Production Readiness & Verification Checklist

? Frequently Asked Questions

What is the root cause of Migrating CA-Telon Batch Drivers and TDF Panels into Modular Enterprise COBOL 6.x? ↓
CA-Telon batch programs do not contain clean standard PROCEDURE DIVISION logic:.
How do you resolve Migrating CA-Telon Batch Drivers and TDF Panels into Modular Enterprise COBOL 6.x in production? ↓
Eliminate proprietary Broadcom CA-Telon batch drivers and generated spaghetti code. Discover how to extract business logic from Telon Development Facility (TDF) tables, eliminate the TLNMAIN driver, and refactor into clean, modern COBOL 6.x.
How can teams prevent Migrating CA-Telon Batch Drivers and TDF Panels into Modular Enterprise COBOL 6.x in enterprise pipelines? ↓
De-license CA-Telon runtime modules from all test and production load libraries.

Recommended Technical Runbooks

Authoritative Reference Documentation

Official IBM manuals, Redbooks, and vendor technical advisories:

Related Topics: TelonCA-TelonCOBOLModernisationBroadcom ReplacementTDF
Diagnostic Runbook Notice & Nominative Fair Use Disclaimer

This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.

IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. ยง 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →

Enterprise Advisory

Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?

StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.