Whether the target is Amazon AWS, Microsoft Azure, a private cloud, or other platforms, there are significant financial incentives to migrate mainframe applications to the cloud. This process, known as mainframe modernization, is becoming increasingly essential.
The BIGGEST expense of such projects, often encountered during the mainframe modernization process, is the Testing phase: ensuring the same functionality in the new application, whether it was rehosted (re-compiled with a new compiler, and deployed onto the cloud) or translated into new languages. Given the cost and effort involved in Testing the new application, many organizations are opting for the long-term solution of mainframe modernization, and translate the codebase to a new language to allow continued maintenance by new developers.
This paper focuses on a long-term solution that involves changing the codebase from COBOL to a cloud-friendly language/framework such as Java or C#. This approach offers the following benefits in the context of mainframe modernization:
The most cost-effective and low-risk approach to Java/C# during mainframe modernization is using a mature translator capable of producing maintainable and functionally correct Java/C# code. SoftwareMining achieves this by addressing 16 Features Essential for Successful COBOL to Java Conversion Projects in the context of mainframe modernization.
Java and C# Application Servers provide much of the functionality provided by CICS, vital for mainframe modernization. The COBOL Translator must be able to generate code which will utilize such features during the modernization process.
See Approach to Migration of CICS Cobol to Java / C#.
The translation should support the conversion of BMS/MFS formats to HTML documents which utilize APIs provided by native languages such as JSP, Razor, or ASP. This is a critical step in mainframe modernization.
Furthermore, the generated code should use meaningful statements instead of legacy BMS statements. Many of the COBOL screen manipulation statements may be foreign to new developers, making this clarity essential for effective mainframe modernization.
For more detail please see converting legacy BMS operations to meaningful statements.
While mainframe modernization efforts often involve moving COBOL applications to SQL Databases, a significant number of applications still use KSDS files for their data storage needs. One of the essential steps in mainframe modernization is to address this aspect of data migration.
SoftwareMining's conversion process is designed to facilitate this key aspect of mainframe modernization. It automatically handles the migration of VSAM/KSDS structures by generating representative SQL database schemas, streamlining the transition from legacy data structures to modern, scalable databases.
Additionally, as part of the mainframe modernization process, the data migration scripts provided by SoftwareMining are equipped to handle the conversion of character encoding from EBCDIC to ASCII, ensuring data integrity and compatibility in the new environment.
Most legacy COBOL applications use a queueing framework for passing messages between modules. As a key aspect of mainframe modernization, once translated, during the testing phase the new system should be able to communicate with the legacy MQ Series.
Beyond the testing phase, the new application should be prepared to use any other commercial or Open-Source queueing system, enabling seamless integration and flexibility as part of the mainframe modernization process.
SoftwareMining's approach to mainframe modernization includes translating interfaces which allow implementations to communicate with any queueing system, ensuring adaptability and ease of integration in modernized applications.
For successful mainframe modernization, it is crucial that JCL scripts are converted and are compatible with the cloud. A viable JCL solution needs to address a series of challenges, making the legacy JCL scripts comprehensible and functional for new developers.
In mainframe modernization, the conversion of COBOL + EXEC SQL to Java / C# needs to change the dialect of SQL - from COBOL centric (using Host-Variables, Null-Indicators) to Java (using '?') or C# centric.
Additionally, for performance reasons, the converter will also need to try and reduce the amount of data-based communication, as these may have higher overheads on the Cloud.
There may also be performance issues when communicating between DB2 on mainframe and external Java/C# applications. For more information, see detecting cause of performance issues.
For some cases, such as IMS DB, the mainframe modernization process may require a separate stage by creating a "middle-data-access-layer".
During mainframe modernization, Assembler programs should be reviewed on a case-by-case basis. In many instances, they can be replaced by Java and C# libraries, offering a richer framework and library set than COBOL.
For more detailed information about SoftwareMining's approach to mainframe modernization, including its CICS libraries, JCL solutions, and more, please refer to the respective sections.
© 2023 SoftwareMining is a trademark of Software Modernization Technologies Ltd (UK). Registered in England company no: 07300248. Reg Offices: 79 Stevens House, Jerome Place, Kingston Upon Thames, KT1 1HX, United Kingdom.