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 [...]
The Philosophy Never change the existing code if you can avoid doing so Don’t change the user look and feel of existing programs when migrating Develop new functionnality in a modern language Guarantee 99. 99% availability for business critical applications thanks to staged migration and reversibility Why should [...]
Even in (relatively) small volumes, HLASM is a serious problem In most mainframe shops, the volume of HLASM code is small compared to COBOL or PL/I. Even so, as little as 30’000 lines of assembler code will cause unexpected delays and budget overruns. If one considers rewriting it, reverse engineering its behavior requires [...]
To achieve this, you must make sure that: The same source code runs on the mainframe and on Azure You have an ASM370 compiler on Azure Your user interfaces are externalised (.NET or Java) and rely on CICS transactions for the business logic You can modernize the code to C# [...]
When migrating Mainframe to .NET, reduce dependancy of COBOL & allow cost-less new developments At Microsoft Inspire, Raincode releases the community edition version 3.0 of its free to use COBOL Compiler: a major upgrade for this exceptional product downloaded over 11’000 times and counting. It is de facto the industry standard COBOL compiler when corporations [...]
The Raincode team decided to offer its partners and customers an unbreakable cookie, called Couque de Dinant (or Cake of Dinant), which represents the unbreakable Mainframe. And we've, as a symbol, broke this cookie to underline the idea that Mainframe is no longer a tough and unbreakable cookie! Step 1: Getting the cookies out of their boxes [...]
