DB2 SQL dialect.

COBOL programs usually interact with a database system. In the vast majority of cases DB2 is the preferred choice, the killjoy is IMS. Migrating data from DB2 to MS SQL has been solved for a long time, but what about SQL statements embedded in application programs? One can believe that SQL is a standard, but each vendor supports its own SQL dialect.
MS SQL will not understand statements written for DB2. Migrating an application from one database to another can be a migration project in its own right. The Raincode compilers transform DB2 SQL statements into equivalent SQL Server statements at compile time so that there is no runtime performance penalty involved.
The existing code can run on top of SQL Server without any changes whatsoever, even though its SQL statements were written for another database. Raincode goes the extra mile: as you don’t change your existing code, your legacy programs can be executed simultaneously in 3 configurations to mitigate the migration risk

  • On your Mainframe unchanged for production

  • In parallel execution on a .NET platform with a DB2 database on mainframe

  • In parallel execution on a .NET platform with MS SQL database

Moving programs is only part of the story. If you can’t deal with SQL statements, you have no real solution
We are so confident that COBOL is not the problem that…

ASM 370

Promising migration projects for millions of lines can be jeopardized by as little as 30,000 lines of ASM 370. Legacy programs routinely call assembly code which has to be rewritten if the system is to be migrated.
It is a non-trivial undertaking. Until today, such migration projects were killed at inception.
To solve this issue, we address HLASM as a high level language and we have developed an ASM370 compiler for .NET. Macros, copy books, reentry code are automatically migrated and executed on .NET.
Our compiler supports the mainframe Assembler 370 and HLASM® syntax accurately, and emulates its data types and behavior. Modules compiled by the Raincode ASM370 compiler integrate seamlessly with the Raincode COBOL and PL/I compilers. The major obstacle for all legacy code migration is now out of the way.


COBOL is not the only language that must be addressed. IBM pushed PL/I as the most versatile computer language in the 1970’s and 80s, and it has gained some momentum. Rewriting those applications can take years and experience shows that no automated translation of PL/I ever reaches production, except in MS PowerPoint.
At Raincode, we developed a PL/I compiler for .NET. that complements and integrates with our COBOL compiler. The PL/I applications execute with a superior level of functionality on .NET; any new modules written in C# or VB.NET interacts gracefully with the legacy code, calling or being called transparently by COBOL, PL/I or ASM370 programs.


Legacy Modernization brings absolute benefits, cost saving from hardware and mainframe software licensing, rejuvenated and agile applications. It also prevents code obsolescence.
Migrated code on .NET interacts gracefully with any supported modern language. Today nobody should write new code in COBOL, PL/I or ASM370. New functionality can be developed using C# or VB.NET and integrated gracefully into the legacy system.
PL/I, COBOL and ASM370 resources will vanish in the next decade but, when legacy is migrated with Raincode, C# developers will gradually take over.

In a legacy code migration:

  • the devil is in the details, not in the mainstream

  • an integrated set of .NET compilers handles it

We are so confident that COBOL is not the problem that…
The Raincode COBOL compiler is totally free of charge.
Anyone can download it from our website: www.raincode.com/cobol