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
CloudFrame Relocate provides an easy way to shift COBOL workloads from CPs to a zIIP using cross-compilation. This means that COBOL source code is converted directly into Java bytecode, allowing the executable to run in a zIIP-eligible Java Virtual Machine (JVM). This process is transparent to the code’s existing relationship with data stores and other infrastructure. Therefore, stored procedures don’t have to be rewritten, batch schedulers don’t have to be adjusted, and sort processes can
Mainframe cost optimization is a current buzzword being applied to many different processes and techniques. But let’s face it, optimization in this context inevitably means reduction. The general idea is that companies are looking for ways to reduce the cost of their computing infrastructure. And who can blame them? If you can pay less for something, why not do it? So, what types of things get lumped into mainframe cost optimization? Generally speaking, you can
The title of today’s post is a question that I get asked all the time. Sometimes by users who are interested in trying to curtail mainframe costs. Sometimes by vendors looking for a way to promote their products that help to reduce costs. While both are well-meaning, this is a question I never answer. Because it is meaningless. Let’s discuss why this is so. First, let’s look at some of the “answers” to this question
Shifting COBOL compute to less expensive platforms is a great first step on many organizations’ application modernization journey. There are multiple reasons an organization might want to begin with shifting COBOL compute, including low risk, the straightforward nature of the approach, and the potential for extraordinary ROI. NOTE: Cross-compiling COBOL programs into Java byte code is CloudFrame’s recommended shifting COBOL compute approach and is accomplished using the CloudFrame Relocate product. You can learn more about
Whenever somebody talks about software pricing on the mainframe or tuning to save on their monthly mainframe bill, I always wonder just exactly what they are talking about. Are they aware of all their company’s licensing agreements and all the intricacies therein? Before we move on, let me just state that the mainframe still makes good economic sense. The total cost of ownership (TCO) for the mainframe, when you add up all of the cost
Mobile computing has had a seismic impact on IT and modern computing architecture… and will continue into the foreseeable future. Mobile devices – smartphones and tablets – have overtaken traditional computing devices, such as desktop and laptop computers, in terms of how we interact with service providers and retailers. And this transition is even more pronounced among the young. It is not uncommon for a smartphone to be used non-stop during the course of the
The cost per MSU (or MIPS) is not steady. At least not for sub-capacity pricing. As the number of MSUs or MIPS you consume increases, the cost per/MSU (MIPS) goes down. This means that each MSU (or MIPS) saved will be the cheapest you are paying for. This can be verified by reviewing the IBM Z Software Pricing Reference Guide. The price per MSU is based on a multi-level system unique to the sub-capacity pricing
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 […]
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 […]
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 […]