A leading Global bank knew it needed to modernize its mainframe as costs increased, but it was also concerned about the impact on its daily activities and business disruptions. Digital transformation leader GFT and COBOL to Java modernization experts CloudFrame worked together to transform two batch jobs and their Cobol programs into a new environment in just three weeks. The project delivered greater-than-expected cost reductions without impacting the development teams supporting the application. Background Mainframe
The IBM zIIP is a dedicated specialty processor designed to operate asynchronously with mainframe general processors. The IIP in zIIP stands for Integrated Information Processor, but that doesn’t really define what the zIIP is or how it can best be used. When you use zIIPs, some percentage of your mainframe workload can be redirected off the general processors onto the zIIP specialty processor. The primary reason for doing this is that software charges are not
In our previous post, we covered the most common reasons why an enterprise faced with a COBOL application modernization challenge might choose to start again from scratch with a “greenfield” requirement, design, and build project. We mentioned some of the risks arising from this approach, and in this second part of our series, we’ll take a closer look at these. Forewarned is forearmed, and being able to understand and explain the potential dangers of greenfield
Mainframe systems have been the backbone of large businesses and organizations since the advent of the IBM System 360 in 1964. That is a long time for mainframe systems to grow and increase in complexity, making them difficult to maintain over time. As a result, many companies are now considering mainframe application modernization as a means of increasing their efficiency and reducing their costs. Mainframe application modernization refers to the process of updating and optimizing
As most z/OS practitioners know, zIIP processors can provide significant benefits in cost savings and improved performance. And one of the most significant areas for taking advantage of the benefits that zIIPs can provide is within Db2 for z/OS. As such, the role of Db2 DBAs in promoting zIIP usage can be critical. It is important to note that not all features of Db2 for z/OS can run on zIIP processors and that the extent
“Let’s just start fresh.” In the arena of COBOL application modernization, these words have been uttered many times over the years by technologists, business executives, and even board directors. While the phrase does have great power to lift the spirits (at least for a while) of everyone involved in a big, complex project, at CloudFrame we’ve seen the longer-term results of such “new starts” often enough to know that deeper consideration is warranted before embarking
What Applications are Good Shift COBOL Compute Candidates? If your curiosity has been piqued by the benefits of shifting COBOL compute and how it can be accomplished, you may have begun to think about the applications in your inventory and if they would align with this type of modernization effort. Selecting the right applications or programs to begin this journey is one of the critical success factors. Choose incorrectly, and no matter how good your
Regular readers of my posts here know that zIIPs are a type of mainframe specialty processor that augments the general-purpose CPUs. Instead of running all workloads on the general-purpose CPUs, specific workloads are shuttled to the specialty processors for execution. The zIIP, or Integrated Information Processor, was initially created to process certain types of Db2 workloads, but over time the work that can be processed on the zIIP has expanded. Nevertheless, the primary reason for
Units of work that run on the mainframe, at least those running on z/OS, are dispatched using two different types of control blocks: TCBs (Task Control Blocks) and SRBs (Service Request Blocks). It can be beneficial to understand these two types of control blocks, including how they are used, the differences between the two, and the implications of using each. There are significant nuances to understanding how z/OS work is dispatched, but we will not
Cost is the primary driver for shifting COBOL compute to less expensive platforms. But once organizations decide that they are going to use shifting COBOL compute they discover there are other benefits to this modernization method. These benefits are realized in three areas: impact, risk, and momentum. Financial Impact The immediate benefit of shifting COBOL compute can be seen in the reduction of mainframe MSU utilization of the environment from which the program or application
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 […]