COBOL to C# or Java Transformation

The expansion rate reflects how many lines of output code are produced based on a certain set of input code. This document explores the expansion rate when transforming COBOL code to C# or Java, using CodeTurn. The paper was documented based on a concrete use case of a recently transformed COBOL application that went into production for one of our customers.

To get meaningful numbers out of this exercise, some additional background on the transformation of COBOL needs to be provided, specifically around the concept of COBOL copybooks and how these can be transformed. From a maintenance point of view, copybooks should be transformed into separate C#/Java entities as much as possible.

For more details on the complexity of the usage of COBOL copybooks, please see the Safely transforming COBOL COPY statements with CodeTurn White Paper.

However, due to the specific technical characteristics of all the technologies involved, this is not always possible. As a result, the following two different categories of COBOL programs are identified:

  • COBOL programs that don’t need to expand any of the COBOL copybooks used
  • COBOL programs that need to expand at least one COBOL copybook
Get the full white paper using the form below.
Request White Paper

Please fill in this form to request a PDF download for this White Paper.

Thank you! Your request has been received!
Oops! Something went wrong while submitting the form.