Modernizing Mainframe Systems: The Imperative of Expertise
Michael Burgun
Senior Technology Consultant | System/data architect, System integration consultant
In recent times I have noticed a sudden increase in interest and attention to those systems that enterprise leadership has been ignoring. Those systems have been quietly running the vast majority of their company’s business transactions. Ignoring those core mainframe systems for so long has meant that risk has risen to such an extent that regulators are becoming concerned and boards are paying attention. Accordingly, organizations are under increasing pressure to modernize their IT infrastructure and this will come at both a financial and organisational cost. This push towards modernization, while necessary, is fraught with risks that can lead to vendor capture and significant cost blowouts if not managed with a deep understanding of the mainframe environment.
The Allure and the Pitfalls of Modernization
Modernization initiatives, such as integrating Infosphere Change Data Capture (CDC) and IBM z/OS Connect, promise numerous benefits, including improved data accessibility, enhanced performance, and better scalability. These tools are designed to leverage the mainframe’s capabilities while facilitating seamless interaction with newer, more agile systems.
However, the complexity of these modernization efforts cannot be overstated. One of the primary challenges lies in the assumption that skills transferable from generic Linux environments will suffice for mainframe systems. While the Linux subsystem within the mainframe provides a familiar interface for many IT professionals, the unique characteristics of mainframe environments—particularly in areas such as security, cross-file system access, and networking—require specialized knowledge and experience.
The Hidden Costs of Increased CPU Utilization
Modern services running on the Linux subsystem are known to be heavy users of compute (CPU) resources. This increased demand for processing power translates directly into higher costs. Most mainframe software licensing is priced by Million Service Units (MSU), an IBM measure of processing power. As CPU requirements grow, so too do the costs associated with both hardware and existing software workloads. This is because most mainframe software is licensed on an annual basis proportionally to the MSU of the hardware that it is running on. This creates a scenario where modernization can lead to spiralling expenses if not carefully managed.
The Risk of Vendor Capture
A significant risk in the modernization journey is vendor capture. As organizations adopt new tools and services, they often become increasingly dependent on specific vendors for support, updates, and integration. This dependency on both infrastructure and managed service providers can limit flexibility and drive-up costs over time, especially if the vendor's pricing models or strategic direction changes.
To manage these risks, it's crucial to maintain a level of independence by ensuring that in-house teams possess the necessary skills and understanding of the mainframe environment. Additionally, the market also has a myriad of smaller consultancies and individuals who may be retained directly to provide more independent advice. This expertise allows organizations to make informed decisions, negotiate better terms with vendors, and implement solutions that are truly in their best interest.
领英推荐
The Imperative of Mainframe Expertise
The gap between available Linux skills and the specialized knowledge required for mainframe systems is significant. Missteps in configuration, security protocols, and system integration can lead to vulnerabilities and inefficiencies. This is why experience and a deep understanding of the mainframe environment are imperative.
Experienced professionals can navigate the nuances of mainframe operations, ensuring that modernization efforts enhance, rather than compromise, system integrity and performance. They can also help in optimizing resource utilization, thereby controlling costs and avoiding unnecessary expenditures.
Strategic Approaches to Addressing Skill Shortages
1. Invest in Training and Development:?Building in-house expertise through targeted training programs can help bridge the skills gap. Encouraging a culture of continuous learning ensures that teams stay updated with the latest advancements and best practices in mainframe technology. This is not a short-term project or cheap and requires dedicated ongoing attention. Because such skills are rare and in high demand, retention of such skilled staff means attention must be given to renumeration and a positive culture within the team.
2. Engage Experienced Partners:?Collaborating with vendors and consultants who have a proven track record in mainframe modernization can provide valuable insights and support. These partners can help navigate the complexities and ensure that the modernization strategy aligns with organizational goals. It should be noted however, larger venders have an imperative to lower costs and accordingly not put the effort into retaining specialist expertise. Such venders need to be monitored carefully, not only at contract commencement for capability but throughout their engagement to ensure service is maintained. This monitoring must be performed independently by experienced mainframe practitioners.
TL;DR
Modernizing mainframe systems goes beyond merely adopting new technologies; it’s about doing so sustainably, cost-effectively, and in line with enterprise objectives. The risks of vendor capture and cost blowouts underscore the critical need for deep mainframe expertise. By investing in this expertise and implementing strategic approaches, organizations can successfully modernize, ensuring their IT infrastructure remains robust, secure, and poised for future growth.
Innovative thinker and learner
8 个月The Risk of Vendor Capture - The most important part once you are looking to explore Migration. CPU cost can increase from here, knowledge sharing can also be suppressed and a parallel knowledgeable team within the client's organisation will be a tough path. Another measure is, organisations should give some time to groom new hires before retiring their champions, it is not a pitch of 2-3 months.
Good article Michael. Maybe mainframes just need AI ?? LOL
Technical Liaison, Systems Analyst, Data Engineer and Mainframe Specialist
8 个月I completely concur. This has been the “elephant in the room” for a long time. Unfortunately, the clock is definitely ticking here. Two problems that I see are, getting the knowledge transferred from older heads and encouraging those that drive corporate strategy to focus on the long game rather than be distracted by the so far unfulfilled promises of AI as the panacea of IT solutions.