COBOL-to-Java Converter for IBM i ILE COBOL Applications

SoftwareMining's COBOL-to-Java and COBOL-to-C# Converter supports the migration of IBM i ILE COBOL applications to maintainable Java or C# source code through automated, rule-based conversion within the customer's own infrastructure.

The converter handles COBOL business logic, data structures, file access and supported IBM i dependencies, including Db2 for i, record-level access and DDS-defined database and display files.

IBM i systems, formerly known as AS/400 and iSeries, may combine ILE COBOL with RPG programs and other platform services. SoftwareMining converts the COBOL components, while dependencies on RPG and retained IBM i services must be addressed in the target architecture.


View COBOL-to-Java and C# Conversion Process and Features

DDS Subfiles and Conversational Screens

IBM i COBOL applications may use DDS display files and subfiles to define conversational screens accessed through COBOL record-level operations. SoftwareMining converts supported screen definitions and processing logic into web-interface components within the generated Java or C# application.

The initial JSP or ASP.NET interface can preserve the fields and interaction flow of the original AS/400 screens. It can then be enhanced with modern web controls and layouts without rewriting the converted business logic.

Converting Db2 for i Data Access

ILE COBOL applications may access IBM i database files through READ, WRITE, REWRITE, DELETE and keyed operations using DDS-defined files, record formats and access paths. SoftwareMining converts supported operations into Java or C# data-access components using SQL.

The converted application can continue using Db2 for i on IBM i or access another supported relational database on the selected target platform. Application conversion and database migration can therefore be performed in separate phases where required.

RPG Dependencies in IBM i Applications

IBM i environments may contain both ILE COBOL and RPG applications. SoftwareMining converts the COBOL components but does not currently provide an RPG converter. Dependencies such as program calls and shared files must therefore be identified, integrated and tested when RPG components are retained or converted using a specialist product.