SoftwareMining •
COBOL to Java & C#
• Predictable & Repeatable
Verisk used SoftwareMining's automated, rule-based COBOL-to-Java and COBOL-to-C# Conversion Toolkit across two target architectures. COBOL batch applications were converted to Java and deployed on AWS with PostgreSQL, while online CICS applications using BMS screens were converted to C# and deployed on Microsoft IIS. Both projects included EBCDIC-to-ASCII data migration and provide project evidence across insurance batch processing and online transaction systems.
"The teams have been using the SoftwareMining-based solution in production for some time, and it has proven to be very stable. A testament to the quality of the solution. SoftwareMining was instrumental in the successful migration off the mainframe."
The Verisk modernization work covered separate batch and online application environments. SoftwareMining's rule-based Conversion Toolkit was used to generate Java or C# according to the target architecture selected for each environment.
COBOL batch applications were converted to Java for deployment on AWS, with database access migrated from DB2 to PostgreSQL. Supported JCL job definitions were converted into Unix shell scripts to coordinate the generated Java programs and batch utilities.
Online COBOL applications using CICS and BMS were converted to C# for deployment on Microsoft IIS. The conversion addressed business logic, CICS transaction processing, BMS screen handling and the supporting .NET runtime components required by the target application.
Both projects included EBCDIC-to-ASCII data migration. The client's team and systems integrator used SoftwareMining's tools to manage conversion, testing and deployment, with technical support from SoftwareMining. This model allowed the client to retain control of project schedules, business data and quality assurance.
The original COBOL applications used DB2. As part of the conversion, the database layer was migrated according to the architecture selected for each target application:
The database conversion required mapping schemas, data types, vendor-specific SQL behaviour, return codes and transaction handling for each target platform. The converted applications and migrated databases were then tested against the results of the original COBOL and DB2 systems.
See how SoftwareMining handles COBOL, DB2 and embedded EXEC SQL conversion .
Explore related projects in our COBOL-to-Java and COBOL-to-C# Case Studies .