Partial Process Migration
Within application modernization, the possibility of ‘partial process migration’ emerges. It’s a simple strategy that will drastically reduce MIPS consumption while having a minimal impact on the IT organization.
Real cases have shown that a reduction of up to 50% in MIPS consumption can be achieved in a short time, through well-controlled and limited actions.
The key point is to address processes that are well-defined and, therefore, can be isolated from the rest of the system.
Depending on the architecture, these processes can be found in different parts of the system. In an analysis phase using Caravel technology, which facilitates the identification of isolatable subsystem components.
Once identified, a detailed analysis continues to verify the interfaces (if any) with the rest of the systems (interfaces with data or other processes), their characteristics, and how to handle them.
There is generally a well-identified group of subsystems that have these characteristics among batch applications. Procedures that include transactions running during low-activity hours, usually unattended.
In most cases, these processes only interact with the rest of the system through data.
Once identified, the workload needs to be extracted from the Mainframe.
All these processes offer an opportunity to save MIPS because they can be converted to Java and deployed on an external server (‘the processing device’) without interfering with the rest of the subsystems.
Conversion to Java can be achieved precisely and effectively using Caravel technology.
BASE100’s Caravel offers two independent or combined options:
- Automatic Conversion and/or
Automatic conversion is a quick and low-risk process, performed using the Caravel Express tool, while rewriting is done with the Caravel Converter tool.
Rewriting has the advantage of producing well-structured 100% pure Java code and the ability to include various enhancements.
Batch Java Processes
All processes involved in transforming the database (from the starting situation to the final) can be performed on this external platform without modifying the Mainframe’s content or incurring Mainframe MIPS consumption.
Once the processes are deployed on the external platform, the mechanism is simple: we copy the Mainframe database at a certain situation (let’s say A) to the external server.
Then, the processes run on the external server, transforming the data from situation A to Z, and finally, the external database is copied back to the Mainframe.
The result in the Mainframe database is the same as what we would achieve using the Mainframe CPU to perform these processes. But without any Mainframe MIPS consumption.