COBOL Application Modernization

CTU (COBOL-to-Universal) is an automated conversion tool that transforms a Mainframe-based legacy application from COBOL to Java or C#, producing object oriented code that can be easily maintainable and efficiently integrated with other Java and C# applications. CTU supports the full environment of the Mainframe-based COBOL application, including databases (e.g.,DB2, IDMS, IMS and VSAM), TP monitors (e.g., CICS), JCL, utilities (e.g., IDCAMS), and SORT. The resulting code has the exact functionality of the original legacy application and can easily be tested and implemented in production.

How It Works

During initial project kick-off, Modern Systems will provide the customer with an inventory preparation guide that details how to ‘punch’ and gather all required components from the legacy mainframe environment to be converted. Modern Systems uses these resources to establish the definitive project inventory and to populate a repository of components to be migrated to the target environment.

Once the Inventory Analysis is complete, the next phase is to review the in-scope application inventory and document design decisions related to the source and target platforms, data modeling from legacy to relational, data migration rules for the database, and any required files, and code migration rules or anomalies that are encountered.

Next, Modern Systems begins the process of unloading, transforming, and loading of data from the source environment to the target environment. The data migration processes used to accomplish this are based on the structure of the existing data model and its mapping to the relational database, defined during the previous phase.

Converted, functionally equivalent application code is then delivered to the customer in a series of work packets, based on milestones determined during the initial analysis. Automated COBOL Conversion covers online applications, batch programs, and JCL members. Modern Systems tests the converted code, then delivers it along with any required frameworks to the customer.

Since Modern Systems does not require code freezes during the conversion process, there will be a final code refresh performed to account for changes to the source system during the conversion process. Once complete, the customer is responsible for testing the target environment while Modern Systems provides post-delivery support for a contracted time frame.