modernization of mainframe applications

[suchona.kani.z]

In recent years, modernization measures have been introduced in the area of ​​mainframe development. The 3270 TSO ISPF interface is increasingly being supplemented by graphical user interfaces (GUIs) - for example the Eclipse-based workbench IDz or Topaz. Classic mainframe-based source code management (SCM) systems are being replaced by git or other shared repositories. IBM zUnit or BMC Compuware Topaz for Total Test are being gradually introduced to automate unit and functional tests with mocking functions. The deployment processes are being automated with Jenkins Pipelines. Code coverage and quality gates are used for quality assurance. Continuous integration and/or continuous delivery, DevOps and agile software development have thus arrived in the mainframe area.

However, setting up and implementing these DevOps tool chains requires a lot of effort, time and good cooperation with the software suppliers. Many small to medium-sized mainframe installations (< 5,000 MIPS with fewer than 50 developers) shy away from this effort because an ROI is rarely achievable. Older developers are often hard to get thailand consumer email list excited about the DevOps world and prefer to develop in their familiar 3270 environment (REXX and Clist functions) that is also optimized for their own needs.


Here the world looks a little more diverse. Companies have numerous options for modernizing their mainframe applications. First of all, however, it should be clear which IT corporate strategy is being pursued globally, because the modernization should fit architecturally. In the area of ​​mainframe application modernization, we come across different approaches to solutions.

Code transformation involves the automatic transfer of existing code to Java. The business logic remains unchanged. The adesso transformer is based on a tool suite consisting of the components at|analyze, at|convert, at|edit, at|batch and at|test. Refactorable code can also be taken into account in the transformer by adapting it to customer-specific requirements. The advantage of code transformation is that the migration can be planned. Testing efforts (use cases) can be reduced to a minimum. Fixed-price migrations are the rule after a reliable analysis.