Simple, Safe & Effective COBOL to Java / C#

Check out other COBOL Platforms (IBM, Unisys, Tandem, ...)

Migration of COBOL With Embedded SQL to Java or C#

Many COBOL applications have moved away from use of VSAM files to relational databases SQL.
This step would have significantly improved the data-maintenance of the application as well as easing integration with other non-COBOL applications.
COBOL applications which use EXEC SQL for data access are hence the prime candidates for migration to Java or C#. This path can bring the general application maintenance inline with the already improved data maintenance.

It is worth noting that COBOL SQL applications are also prime candidates for gradual and migration projects.

SQL COBOL Conversion to Java / C#

Some COBOL program use DB2 instead of VSAM files. Access to DB2 is provided via EXECute SQL queries. Migration of embedded EXEC SQL Programs involves the translation of DB2 SQL to ANSI, and replacement of COBOL / SQL Integration features with standard Java/C# practices.
SoftwareMining CORECT changes the Embedded SQL statements from COBOL to Java / C# dialects. Additionally, the system allows externalization of SQL statements in order to ease future database migrations e.g. from DB2 to Oracle.


Many SQL COBOL applications are Batch-programs which need to be completed within a set time frame every day.
As such the migration of such system would hugely benefit from translation into a design which has performance as one of its main considerations.

Changing the SQL dialect from COBOL to Java & C#

In order for the embedded SQL code to work in new system, the dialect has to change from COBOL to Java or C#. This entails converting COBOL host variable (e.g. :FIELD ) to java and C# standards for passing parameters using '?' or '@' characters.
SoftwareMining tools achieve this automatically.

Catering for Database Changes

After the migrationf of COBOL applications to Java, it may also be desirable to change the underlying database, for example moving from DB2 to Oracle, or MySQL ...
The main issue to overcome is the SQL return codes hard-coded in the application which differ between database servers. SoftwareMining migration process allows runtime configuration / substitution of SQL codes - minimizing efforts involved in such database changes.

Migration of COBOL Stored Procedures to Java or C#

SoftwareMining tools can be used to migrate COBOL Stored Procedures to Java or C#. The new Java or C# stored-procedures can then be imported into a variety of databases such as Oracle or Microsoft SQL Server. Due to use of Object-Orientation, Exception handling, and framework based architecture, Java / C# stored procedures have better maintainability than standard Transact SQL or PL SQL scripts The new stored procedures are run within the target database environment, leading a better performance.

SQL COBOL to Java/C# Migration Project Phases

The Migration of COBOL applications to Java or C# involves:
  • Asset Management: Identify all the artefacts required for translation .
  • Translate to target language
  • Database and Data Migration
  • Migrate JCL
  • Create and Populate of Test Database
  • System acceptance testing
  • User Acceptance Testing
  • (Optional): Other Improvements: Screen Redesign, SOA Integration, Cloud Deployments, Coding Improvements and clean up

Comparing COBOL to translated code

Comparison of Converted code: COBOL to Java
Comparison of Converted code: COBOL to C#
COBOL to Java / C# Conversion Tool - Download Trial (Release 2017-02-20)

Related White Papers

COBOL to Java Overview- PDF version

IBM COBOL Migration, Modernization and Re-hosting References

Pseudo Conversational Transactions (Wiki)
Pseudo Conversational Transactions (IBM)
SoftwareMining on Wikipedia


  © 2017, SoftwareMining Technologies. All Rights Reserved. "SoftwareMining Technologies" is a trademark of Software Modernization Technologies Ltd (UK). Software Modernization Technologies Ltd. Registered in England company no: 7300248. Reg Offices: 8b Accommodation Road, London NW11 8ED, United Kingdom.