De-supporting CA-Telon: Reverse Engineering Generated COBOL Screens into Pure CICS BMS Maps
Executive Summary: De-supporting CA-Telon: Reverse Engineering Generated COBOL Screens into Pure CICS BMS Maps
CA-Telon is a legacy 4GL application generator that produces obfuscated COBOL and proprietary runtime dependencies. Discover strategies to de-support Telon, reverse-engineer screen formats into pure CICS Basic Mapping Support (BMS) or modern React front-ends.
1 Problem Statement & Architecture Context: De-supporting CA-Telon: Reverse Engineering Generated COBOL Screens into Pure CICS BMS Maps
An enterprise relies on hundreds of mission-critical customer service screens generated in the 1990s using CA-Telon. Broadcom support for Telon is costly and specialized skills are nearly extinct. When developers need to update a screen or comply with accessibility guidelines, they find the underlying COBOL code heavily obscured by Telon macro expansions and runtime drivers.
2 Technical Root Cause & Architecture Mechanics
CA-Telon generated COBOL applications rely on proprietary runtime routines:
1. Telon Driver Architecture: Rather than calling standard CICS RECEIVE MAP and SEND MAP commands directly, Telon programs delegate execution to proprietary runtime modules (e.g., TLNMAIN, TLNCICS).
2. Proprietary TDF Data Dictionaries: Application logic, field validations, and screen transitions are trapped inside proprietary Telon Development Facility (TDF) files.
3. Macro Obfuscation: The emitted COBOL contains hundreds of repetitive generated labels, cryptic working-storage copybooks (TLNPCOMM), and opaque internal pointer arrays that cannot be easily maintained by standard COBOL engineers.
3 Implementation Guide & Modernization Strategy
# 1. Extract Screen Coordinates from Telon Panel Definitions
Export the screen panel layout from the Telon catalog or capture the 3270 datastream to extract literal labels, input fields, attributes (protect, numeric, bright), and cursor positions.
# 2. Generate Standard CICS BMS Macro Definition
Convert the extracted panel into pure, vendor-neutral CICS Basic Mapping Support (BMS) assembler macros:
* CICS BMS MAPSET DEFINITION - DECOUPLING FROM TELON
CUSTSET DFHMSD TYPE=&SYSPARM,MODE=INOUT,LANG=COBOL, X
STORAGE=AUTO,TIOAPFX=YES
CUSTMAP DFHMDI SIZE=(24,80),CTRL=(FREEKB,FRSET)
DFHMDF POS=(1,28),ATTRB=(ASKIP,BRT),LENGTH=24, X
INITIAL='CUSTOMER INQUIRY SYSTEM'
DFHMDF POS=(4,2),ATTRB=(ASKIP,NORM),LENGTH=12, X
INITIAL='ACCOUNT NO:'
ACCTIN DFHMDF POS=(4,15),ATTRB=(UNPROT,NUM,IC),LENGTH=10
DFHMDF POS=(4,26),ATTRB=(ASKIP),LENGTH=1
DFHMDF POS=(6,2),ATTRB=(ASKIP,NORM),LENGTH=12, X
INITIAL='CUST NAME :'
NAMEIN DFHMDF POS=(6,15),ATTRB=(ASKIP,BRT),LENGTH=30
CUSTSET DFHMSD TYPE=FINAL
END
# 3. Replace Telon Runtime Calls with Native CICS Commands
In the COBOL program, replace the Telon driver invocation with native CICS statements:
* NATIVE CICS RECEIVE & SEND (NO TELON LICENSES REQUIRED)
EXEC CICS RECEIVE
MAP('CUSTMAP')
MAPSET('CUSTSET')
INTO(CUSTMAPI)
END-EXEC.
MOVE CUST-NAME TO NAMEINO.
EXEC CICS SEND
MAP('CUSTMAP')
MAPSET('CUSTSET')
FROM(CUSTMAPO)
ERASE
END-EXEC.
# 4. Alternative: Direct Bridge to Modern Web (React / Vue)
For enterprises looking beyond green-screens, StackMF provides automated converters that translate BMS/Telon field layouts directly into JSON schemas and React UI component libraries!
Technical Specifications Matrix
| Attribute | Specification |
|---|---|
| Target Environment | IBM z/OS • Modernisation & Cloud |
| Key Technologies | Telon, CA-Telon, CICS BMS |
| Delivery SLA | Accelerated Sprint Delivery via StackMF Pods |
| Technical Reviewer | Anshu, Chief Technology Architect • StackMF Architecture Pod |
Production Readiness & Verification Checklist
- De-license CA-Telon runtime modules from CICS startup load libraries to eliminate recurrent fees.
- Adopt modern API-first architectures using z/OS Connect rather than generating new 3270 screens.
- Preserve original business validation rules when extracting logic from Telon generated COBOL.
- Partner with StackMF's modernization pods to automate large-scale Telon de-supporting.
? Frequently Asked Questions
What is the root cause of De-supporting CA-Telon: Reverse Engineering Generated COBOL Screens into Pure CICS BMS Maps? ↓
How do you resolve De-supporting CA-Telon: Reverse Engineering Generated COBOL Screens into Pure CICS BMS Maps in production? ↓
How can teams prevent De-supporting CA-Telon: Reverse Engineering Generated COBOL Screens into Pure CICS BMS Maps in enterprise pipelines? ↓
Recommended Technical Runbooks
Modernizing COBOL Copybooks to OpenAPI 3.0 REST APIs using IBM z/OS Connect
Real-Time Mainframe Change Data Capture (CDC) to Apache Kafka: Streaming DB2 & VSAM to Cloud
Dual-Stack COBOL and Java Interoperability on z/OS using 64-bit IBM Semeru Runtime
Authoritative Reference Documentation
Official IBM manuals, Redbooks, and vendor technical advisories:
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 →
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%.