The industry trend is clear, but why exactly are organizations choosing to leave the mainframe and make the transition to the cloud? 1. The mainframe is at the peak of a 25-year crisis Even before Y2K bug threatened to bring modern civilization to a screeching halt, pressure was mounting on organizations to
What is the COBOL Tax? Most of us who are not white-collar criminals are intimately familiar with the concept of paying taxes. We pay tax on our incomes and when we go shopping. There are taxes on all kinds of products and services; taxes of varying amounts for a variety of different reasons.
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...
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
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#