When you hear “COBOL transformation to maintainable Java in 60 minutes” the reaction is predictable; eye rolls, thinking – “yeah right,” and suspicion. It’s understandable that you have a healthy skepticism when it comes to COBOL transformation pronouncements. After all, COBOL has been on the “replace” list for decades, and stories of failed projects are numerous and easy to find. CloudFrame wants to chip away at the skepticism and suspicion. Demonstrating and displaying our approach
The zIIP, an IBM specialty processor, allows organizations to reduce the workload of their general processors (GPs). This reduction can lower the MSU metrics used to calculate MLC software charges. Lower MSU usage can lead to lower MLC charges. Knowing that zIIPs may reduce your cost and achieve the benefit isn’t as complicated as you might think. Understanding how to leverage the zIIP for cost reduction is a CloudFrame Modernization Best Practice and can be
The drive to get COBOL applications into the cloud, and specifically Java, created a monster: JOBOL. It is the evil offspring of COBOL and Java when no planning, optimization, and design is applied to transformation. JOBOL is the byproduct of speed at all cost, check-the-cloud-box initiatives. But when modernization efforts deliver JOBOL to application teams, with its inheritance of complicated mainframe COBOL structure and bloated code base, problems arise. Development teams are reluctant to own
Organizations invest time and effort into new software products based on business plans and goals. They want to solve a problem, gain an advantage, or reduce risk and cost. One of the first steps on the new software journey is to establish that the product can do what the vendor says the software will do. Organizations want proof. That’s the purpose of the Proof of Concept (POC) engagement. An example solution scenario is tested in
COBOL modernization projects can be high-risk and costly. Especially if applications are modernized using a green-field rewrite approach. These projects can involve small armies of developers deployed for the heavy lifting of code production as they attempt to reduce the risk of extended project duration. Some of these projects are “successful” – often by tweaking the definition of success. The reasons for redefining success are varied. The code produced by the deployed army might be
Enterprises have long sought the Cure for COBOL, the cure for rising costs, the cure for risks associated with the loss of knowledgeable resources, the rise of technical debt, and loss of understanding the mission-critical business applications and processes. History provides examples of what not to do: • ignoring the problem • thinking Lift and Shift modernization supports innovation attempting to conform Java to COBOL structures • using large teams of coders to manually transform
Almost everyone wants to modernize their mainframe COBOL applications, but most see the process as too big, too costly, and too risky. They are rightfully fearful as it’s reported that 77% of organizations have started but failed to complete at least one modernization program. That’s probably the result of big bang projects or inadequate planning and execution. The antidote for these failed modernization programs is incremental modernization. Incremental modernization reduces risks, accelerates progress, and provides
We’re moving to the cloud. That simple declaration has launched a thousand modernization projects. Mission-critical mainframe COBOL applications be damned! We’re moving to the cloud. It’s a reaction to peer and societal pressures for some IT leaders. For others, it’s the modern-day “nobody ever got fired for buying IBM” cliché. Or it could be just a career trajectory checkbox. If moving your mission-critical, intellectual-property-filled, what-pays-the-bills application to the cloud is simply an exercise to list
Mainframe costs continue to increase. 2022 enterprise software costs are expected to be 11% higher than 2021, and data center costs will increase nearly 6% year to year. Cost reduction and avoidance are critical considerations for mission-critical mainframe COBOL application owners, stressed to delivery on greater transaction volumes, greater access requirements, demanding SLAs, and tightening budgets. If your mission-critical mainframe COBOL applications will continue to reside on the mainframe and you are looking for methods
Knowing that your COBOL modernization pilot project is successful requires defining success before you start.
FS Firm envisions a COBOL-less future by collaborating with CloudFrame and EPAM Download RenovateCase Study Download Case Study Financial Services Firm envisions a COBOL-less future by collaborating with CloudFrame and EPAM as a partner Customer A Financial Services (FS) Firm wanted to reduce mainframe COBOL application costs without disrupting operations. CloudFrame facilitated a collaboration between […]
Telecom Saves $4m a Year by Reducing MIPS Usage with CloudFrame Substantial Savings, Reduced RiskCase Study Download Case Study Telecom Company Reduced Mainframe Application Costs with CloudFrame Relocate™ Customer A large TeleCom achieved nearly $4M in savings using an incremental project approach with CloudFrame Relocate, moving COBOL workloads to both cloud and zIIP eligible JVM. […]
Financial Services Firm Accelerates Application Modernization by Automating JUnit Test Case Generation Automated JUnit Test Case GenerationCase Study Download Case Study Financial Services Firm Accelerates Application Modernization by Automating JUnit Test Case Generation Customer The client is a leading international financial services organization with a strong focus on providing protection and wealth management solutions. Operating […]