The Raincode COBOL compiler for Azure and .NET
The Raincode COBOL compiler supports IBM Mainframe COBOL syntax, data types and behavior.
Applications can be migrated seamlessly and the Visual Studio® 2017 plug-in provides a comfortable and productive development environment.
With Raincode COBOL Compiler new developments in C# are facilitated and the cost of licences for COBOL is no longer a burden.
Generates thread-safe, 100% managed code for .NET 4.5.1 and beyond in 32- and 64-bit mode
Native support for SQL, CICS®. The source code debugged is exactly the same as the source being maintained rather than the output of a pre-processor
Visual Studio® plugin 2015 & 2017 (debugger, compiler configuration, color coding, code folding and project management)
Support for all COBOL data types, with mainframe memory representation
Smooth integration with the Raincode PL/I compiler
Smooth integration with the Raincode ASM370 compiler
The interface manager maps symbols accessed from within COBOL programs (assembler routines, system calls) to .NET symbols, with type conversions and marshaling if needed
Populates a repository for call graphs, statistics and more portfolio analysis tasks
Support for static or dynamic SQL, targeting DB2® (through Microsoft’s HIS®) and SQL Server®
CICS Emulator: Ultimate flexibility
The Raincode COBOL compiler isn’t a black box. It can be tweaked and adapted to environment-specific constraints. Events can be intercepted, overridden or extended.
User-defined code can be used to alter the behavior of memory allocations, file I/O, module loading, SQL commands, tracing, transaction processing, etc.
More specifically, by taking advantage of the Raincode COBOL compiler’s built-in CICS recognition ability, a connection can be made to a CICS emulator without a precompiler.
Exclusive: Run unmodified DB2 code on SQL Server
In theory, the DB2 SQL statements included in your COBOL programs should be usable as is on SQL Server.
But that’s in theory only.
Even though SQL is a standard, there are so many discrepancies between SQL dialects that it is common to see portfolios where as many as 60% of the SQL statements require some level of transformation when moving from one database to another. Differences include built-in functions, operators, implicit type conversion, controlling locking, the number of records to fetch and more.
Migrating an application from one database to another used to be a migration project in its own right. Not anymore. The Raincode COBOL compiler transforms DB2 SQL statements into equivalent SQL Server statements at compile time. The existing code can then run on the target database without any changes whatsoever.
Compiled programs can target either DB2 or SQL Server based on a runtime flag. And since it all happens at compile time, there is no performance penalty involved. Statements run as fast as if they had been coded for SQL Server in the first place.