SoftwareMining •
COBOL to Java & C#
• Predictable & Repeatable
COBOL-to-Java and COBOL-to-C# conversion toolkit from SoftwareMining supports the migration of IBM ILE COBOL applications through automated, rule-based conversion. The tools operate within the customer's own infrastructure and generate maintainable Java or C# source code.
The toolkit translates COBOL business logic, data structures, file access and supported platform dependencies while allowing customers and system integrators to manage testing and deployment within their own infrastructure.
IBM i systems, historically known as AS/400 or iSeries, often contain a mixture of ILE COBOL and RPG programs. SoftwareMining converts the COBOL components, while dependencies on remaining RPG programs and other IBM i services must be identified and addressed as part of the target architecture.
ILE COBOL shares many language features with other IBM COBOL dialects but also uses IBM i facilities such as DDS-defined display and database files, record-level file access and Db2 for i. These dependencies require platform-specific analysis and conversion rather than language-statement translation alone.
COBOL ILE programs often use DDS sub-files to define user screens. These are usually part of conversational applications built for client-server systems. Interaction with the screens follows the same logic as VSAM file access, using COBOL READ and WRITE statements.
SoftwareMining converts these conversational COBOL applications into an application-server framework. The DDS screen layouts are translated into JSP or XHTML pages that run on a standard web server. The generated HTML retains the familiar character-based appearance of the original AS400 interface, helping users transition smoothly to the new system.
As part of modernization, businesses can enhance these screens with a modern UI design. The translated Java or C# applications can also use new JSP or ASP pages without changing the business logic underneath.
ILE COBOL applications can access IBM i database files through native
record-level operations such as READ, WRITE,
REWRITE, DELETE and keyed access. File
definitions, record formats and access paths may be defined through DDS
and referenced by the COBOL program.
SoftwareMining converts supported Db2 for i file definitions and record operations into generated Java or C# data-access components. These components use SQL to access Db2 for i or another supported relational database while representing the record structures and keyed operations required by the converted application.
The generated Java application can run on IBM i and continue using the existing Db2 for i database, or it can be deployed on other supported infrastructure. This allows application code and database migration to be planned as separate phases where the target architecture requires it.
Many IBM i, iSeries and AS/400 environments contain both ILE COBOL and RPG applications. SoftwareMining specializes in automated COBOL-to-Java and COBOL-to-C# conversion and does not currently provide an RPG conversion tool.
During application analysis, calls, shared files and other dependencies between COBOL and RPG components should be identified. Organizations can retain the RPG components during a phased conversion or use a specialist RPG conversion product alongside the SoftwareMining Conversion Toolkit. Interfaces between the converted COBOL application and the remaining or separately converted RPG components must then be integrated and tested.
SoftwareMining provides its automated, rule-based COBOL-to-Java and COBOL-to-C# Conversion Toolkit directly to enterprise customers and system integrators. Project teams can analyse representative ILE COBOL programs, inspect the generated Java or C# source code and validate its behaviour against the original IBM i application.
Review the COBOL-to-Java and COBOL-to-C# Conversion Toolkit features or contact SoftwareMining to discuss DDS screens, Db2 for i access, RPG dependencies and other IBM i requirements.
