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# without any translation of the existing portfolio

Rationale:

  • You need to take care of devils’ details at the project inception: reverse engineering your HLASM code would kill the whole project

  • You need to deploy a truly scalable architecture for CICS: going for an off the shelf emulator will not work beyond a few hundred MIPS

  • You need to leverage a new generation of developers without throwing away the existing portfolio

By |2017-09-18T13:51:34+00:00September 12th, 2017|.NET, CICS, Migration, Raincode|0 Comments