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

Migrating CA-Easytrieve Plus to COBOL using IBM Migration Utility (IMU / FSCCL1)

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

Executive Summary: Migrating CA-Easytrieve Plus to COBOL using IBM Migration Utility (IMU / FSCCL1)

Eliminate expensive Broadcom Easytrieve Plus software licenses by converting legacy EZT programs into standard Enterprise COBOL using IBM Migration Utility (IMU). Learn how to set up the FSCCL1 translator step, configure EZPARAMS, and verify bit-for-bit output parity.

1 Problem Statement & Architecture Context: Migrating CA-Easytrieve Plus to COBOL using IBM Migration Utility (IMU / FSCCL1)

Enterprises paying millions annually in Broadcom software renewals discover hundreds of legacy CA-Easytrieve Plus programs embedded in critical nightly batch extraction pipelines. Because Easytrieve is an interpreted or proprietary-compiled language, removing the Broadcom runtime causes jobs executing PGM=EZTPA00 to fail with ABEND S806 (Module Not Found).

2 Technical Root Cause & Architecture Mechanics

CA-Easytrieve Plus relies on proprietary macros, file control tables, and runtime dynamic link modules (EZTPA00, EZTPX01).

IBM Migration Utility (IMU / product 5655-MGM) provides a transparent source-to-source compiler:

  • IMU preprocessor FSCCL1 translates Easytrieve statements (JOB INPUT, PRINT, REPORT) into standard Enterprise COBOL source code.
  • The emitted COBOL is compiled with IGYCRCTL and linked into standard z/OS executable load modules.
  • Jobs run at native machine speed, completely bypassing Easytrieve runtime licenses while slashing CPU consumption up to 25%.

3 Implementation Guide & Modernization Strategy

# 1. Configure the IMU Translation JCL Step

Replace the legacy EXEC PGM=EZTPA00 with the standard IMU conversion cataloged procedure (FSCASAP):

jcl
//STEP1    EXEC PGM=FSCCL1,
//  PARM='LIST,SOURCE,NODECK,NOTEST,NOMAP,FLAG(I)'
//STEPLIB  DD DSN=SYS1.IMU.SFSCLLMD,DISP=SHR
//SYSIN    DD DSN=PROD.EZT.SRCLIB(REPORT01),DISP=SHR
//SYSOUT   DD SYSOUT=*
//FSCCOBOL DD DSN=&&COBSRCE,DISP=(NEW,PASS),
//            SPACE=(CYL,(5,2)),UNIT=SYSDA,
//            DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920)
//FSCDMSG  DD SYSOUT=*
//SYSERRS  DD SYSOUT=*

# 2. Configure EZPARAMS Translation Rules

Customize the IMU translation table (EZPARAMS) to ensure compatibility:

text
* IMU EZPARAMS CONFIGURATION
COLLSEQ=EBCDIC
DOWHILE=NATIVE
EASYTRAN=YES
SQLMODE=BIND
PAGESIZE=060
LINESIZE=132
AUTOCB=YES

# 3. Compile and Link the Emitted COBOL

Pass &&COBSRCE to standard Enterprise COBOL compiler:

jcl
//COBSTEP  EXEC PGM=IGYCRCTL,PARM='OPT(2),ARCH(14)'
//SYSIN    DD DSN=&&COBSRCE,DISP=(OLD,DELETE)
//SYSLIN   DD DSN=&&LOADSET,DISP=(MOD,PASS),SPACE=(CYL,(2,1))

# 4. Execute the Converted Native Load Module

Run the compiled application without any Broadcom software active:

jcl
//RUNSTEP  EXEC PGM=REPORT01
//STEPLIB  DD DSN=PROD.CONVERTED.LOADLIB,DISP=SHR
//SYSUT1   DD DSN=PROD.INVOICE.INPUT,DISP=SHR
//SYSPRINT DD SYSOUT=*

Technical Specifications Matrix

Attribute Specification
Target Environment IBM z/OS • Modernisation & Cloud
Key Technologies Easytrieve, IBM Migration Utility, IMU
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-Easytrieve Plus to COBOL using IBM Migration Utility (IMU / FSCCL1)? ↓
CA-Easytrieve Plus relies on proprietary macros, file control tables, and runtime dynamic link modules (EZTPA00, EZTPX01).
How do you resolve Migrating CA-Easytrieve Plus to COBOL using IBM Migration Utility (IMU / FSCCL1) in production? ↓
Eliminate expensive Broadcom Easytrieve Plus software licenses by converting legacy EZT programs into standard Enterprise COBOL using IBM Migration Utility (IMU). Learn how to set up the FSCCL1 translator step, configure EZPARAMS, and verify bit-for-bit output parity.
How can teams prevent Migrating CA-Easytrieve Plus to COBOL using IBM Migration Utility (IMU / FSCCL1) in enterprise pipelines? ↓
Run automated parallel runs for 3 cycles comparing the legacy Easytrieve output dataset with IMU-generated COBOL output byte-by-byte using SuperC (`ISRSUPC`).

Recommended Technical Runbooks

Authoritative Reference Documentation

Official IBM manuals, Redbooks, and vendor technical advisories:

Related Topics: EasytrieveIBM Migration UtilityIMUCOBOLBroadcom ReplacementFSCCL1
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%.