Raincode v4 compilers are here, and if you are not excited about them, you should be! We have made a lot of changes since v3—changes that will improve the performance of your migrated applications, increase developer productivity, and ensure the success of your modernization project. But don’t take our word for it...
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
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
Last week, we had the opportunity to present the Raincode Stack in Frankfurt . You will see in the presentation below that we aimed to focus on the key issues of legacy modernization:
In the 2000s, large organizations questioned their dependency on their mainframes and legacy code. At the time, it appeared that a clean break-up would be impossible, or, best case scenario, it would have unbearable consequences. They had to accept to put up with this costly relationship. It is now time to reevaluate this position and