SoftwareMining •
COBOL to Java & C#
• Predictable & Repeatable
Claude Code is changing how organizations approach mainframe modernization. It can accelerate application analysis, assist with code generation and reduce manual development effort.
Two different approaches are commonly used:
Enterprise modernization involves more than generating source code. Small differences in business logic, data handling, transaction processing or batch execution can have significant operational consequences. For most enterprise projects, demonstrating functional equivalence between the original COBOL application and the translated Java or C# application represents the largest part of the modernization effort.
We evaluated Claude Code using representative enterprise COBOL programs together with the NIST COBOL benchmark suite. The objective was not simply to generate readable Java, but to determine whether the translated applications were complete, compilable, executable and suitable for enterprise modernization.
These results suggest that benchmark results alone is not sufficient to assess enterprise modernization tools. Organizations should evaluate representative application programs, compile and execute the translated system, and compare the results with the original COBOL application.
A meaningful enterprise evaluation should include representative batch and online programs, copybooks, embedded SQL, CICS or IMS transaction processing, representative business data, and execution-based testing to determine functional completeness and the amount of manual correction required.
AI-based tools are valuable for analysis and developer assistance, but enterprise modernization also requires repeatable results, controlled change management, and execution-based validation. Large COBOL applications must demonstrate functional equivalence with the original system before production deployment.
Deterministic translation supports this by producing consistent output from the same COBOL source, simplifying regression testing, audit, and controlled modernization programmes.
Enterprise COBOL modernization should be evaluated on more than the appearance of the generated Java or C# code. The key questions are whether the translated application is complete, repeatable, testable, and suitable for controlled deployment.
When comparing modernization technologies, consider the following:
Can the complete application be translated, including business logic, data definitions, file handling, databases, error paths, and platform-specific technologies? Compilable code alone does not demonstrate a complete translation.
Does the same COBOL source produce consistent results each time it is translated? Enterprise projects typically require multiple translation cycles as applications continue to evolve.
Can the translated application be compiled, executed, and compared with the original COBOL system using representative business scenarios? Successful modernization should be demonstrated through execution-based testing rather than code review alone.
Does the approach support the technologies used by the application, such as CICS, IMS, DB2 embedded SQL, VSAM, JCL, or other platform-specific services?
How much manual correction is required? Can the application be regenerated after future COBOL changes? Is the process suitable for controlled change management, audit, and large application portfolios?
Every enterprise COBOL application is different, and AI-assisted modernization tools continue to evolve. Rather than relying solely on published benchmarks or third-party evaluations, organisations should perform their own assessment using representative application programs.
One practical approach is to evaluate publicly available benchmark programs, such as the NIST COBOL test suite, after removing comments and meaningful identifiers. This helps determine whether a tool is analysing the program logic itself or relying on descriptive names and embedded documentation.
The evaluation should then be extended to representative enterprise applications containing copybooks, batch and online processing, embedded SQL, CICS or IMS transactions, together with compilation, execution and comparison of the generated results against the original COBOL application.
Whether evaluating SoftwareMining, Claude Code or any other modernization technology, the objective should not simply be to generate readable Java or C#, but to demonstrate complete, executable and functionally equivalent enterprise applications.
AI tools such as Claude Code represent a significant advance in software engineering. They can accelerate application analysis, documentation, and developer productivity.
Enterprise COBOL modernization has additional requirements. Success depends on repeatability, auditability, and demonstrating functional equivalence under representative workloads. Deterministic translation supports these objectives through consistent transformation and controlled validation.
For enterprise organizations, the question is not simply whether AI can generate modern code, but whether the chosen modernization approach delivers predictable, testable, and repeatable results at scale.
If you're evaluating approaches to COBOL modernization, the following resources may also be useful: