Skip to main content

Why the Time has Arrived for Mainframe AIOps

April Hickel
BMC

More and more mainframe decision makers are becoming aware that the traditional way of handling mainframe operations will soon fall by the wayside. The ever-growing demand for newer, faster digital services has placed increased pressure on data centers to keep up as new applications come online, the volume of data handled continually increases, and workloads become increasingly unpredictable.

In a recent Forrester Consulting AIOps survey, commissioned by BMC, the majority of respondents cited that they spend too much time reacting to incidents and not enough time finding ways to prevent them, with 70% stating that incidents have an impact before they are even detected, and 60% saying that it takes too long for their organizations to detect incidents. With the mainframe a central part of application infrastructure, performance issues can affect the entire application, making early detection and resolution of these issues (not to mention their avoidance altogether), vitally important.

Organizations must treat the mainframe as a connected platform and take a new, more proactive approach to operations management. Fortunately, the evolution of data collection and processing technology and the emergence of newly created machine learning techniques now afford us a path to transform mainframe operations with AIOps, becoming a more autonomous digital enterprise.

In today's fast-paced digital economy, operations teams don't have time to spend in prolonged investigative phases each time an issue arises. Instead of waiting for issues to arise, then devoting available resources to resolve them, the automated monitoring offered by modern tools uses artificial intelligence (AI) and machine learning (ML) to examine and evaluate the interplay of multiple pieces of intersecting information, allowing teams to detect potential problems and pinpoint their cause much earlier.

This automation becomes even more important as shifting workforce demographics result in the loss of institutional knowledge. The Forrester AIOps survey showed that 81% of respondents still rely in part on manual processes to respond to slowdowns, with 75% saying their organization employs some manual labor when diagnosing multisystem incidents. In today's fast-paced digital economy, this creates a perfect storm of higher customer expectations, faster implementation of an increasing number of digital services, and a more tightly connected mainframe supported by a less-experienced workforce.

Automated monitoring helps ease these pressures by codifying knowledge and identifying potential problems and possible solutions, resulting in proactive monitoring, faster response, and decreased reliance on specialized skillsets.

The good news is that AIOps on the mainframe is no longer limited to those organizations with the resources to design and implement customized large-scale data collection and data science infrastructures. The technology for being able to consume and process the large volume of data captured on the mainframe, and the proven techniques to apply machine learning algorithms to that data, have matured to a degree of accuracy and scale where they are now implementable in a wide range of customer environments. Vendors have even evolved to the point where they are now shipping out-of-the-box models that can be implemented immediately to accurately detect existing and potential problems.

So, where to begin?

Many organizations have found success in implementing mainframe AIOps by starting with a narrow scope. Build AIOps onto your existing systems management platform rather than replacing it wholesale. Make sure your existing platform is current and that you choose a monitoring tool that provides a modern user experience and allows you to quickly and easily integrate AIOps use cases.

Starting with a focused use case, such as detection, and inputting historical data can help demystify the process by showing how known issues are detected and help prove the value of moving to an AIOps-based approach. Once you have successfully implemented that first use case, move to a second, such as probable cause analysis, again taking advantage of historical data to learn and test the new technology. This gradual adoption not only ensures that your organization is employing AIOps tools to their full potential, it allows employees to learn the tools and adapt processes without the upheaval of a sudden, major change.

The detect and respond model of operations management has served the mainframe well for decades, but the confluence of multiple factors has made it clear that a change is in order. With an accelerating digital economy, the increased need to include the mainframe in your organization's digital strategy, shifting workforce demographics, and availability of technologies that enable automation everywhere, the time is right for your organization to adopt AIOps on the mainframe.

April Hickel is VP, Intelligent Z Optimization and Transformation, at BMC

Hot Topics

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

Why the Time has Arrived for Mainframe AIOps

April Hickel
BMC

More and more mainframe decision makers are becoming aware that the traditional way of handling mainframe operations will soon fall by the wayside. The ever-growing demand for newer, faster digital services has placed increased pressure on data centers to keep up as new applications come online, the volume of data handled continually increases, and workloads become increasingly unpredictable.

In a recent Forrester Consulting AIOps survey, commissioned by BMC, the majority of respondents cited that they spend too much time reacting to incidents and not enough time finding ways to prevent them, with 70% stating that incidents have an impact before they are even detected, and 60% saying that it takes too long for their organizations to detect incidents. With the mainframe a central part of application infrastructure, performance issues can affect the entire application, making early detection and resolution of these issues (not to mention their avoidance altogether), vitally important.

Organizations must treat the mainframe as a connected platform and take a new, more proactive approach to operations management. Fortunately, the evolution of data collection and processing technology and the emergence of newly created machine learning techniques now afford us a path to transform mainframe operations with AIOps, becoming a more autonomous digital enterprise.

In today's fast-paced digital economy, operations teams don't have time to spend in prolonged investigative phases each time an issue arises. Instead of waiting for issues to arise, then devoting available resources to resolve them, the automated monitoring offered by modern tools uses artificial intelligence (AI) and machine learning (ML) to examine and evaluate the interplay of multiple pieces of intersecting information, allowing teams to detect potential problems and pinpoint their cause much earlier.

This automation becomes even more important as shifting workforce demographics result in the loss of institutional knowledge. The Forrester AIOps survey showed that 81% of respondents still rely in part on manual processes to respond to slowdowns, with 75% saying their organization employs some manual labor when diagnosing multisystem incidents. In today's fast-paced digital economy, this creates a perfect storm of higher customer expectations, faster implementation of an increasing number of digital services, and a more tightly connected mainframe supported by a less-experienced workforce.

Automated monitoring helps ease these pressures by codifying knowledge and identifying potential problems and possible solutions, resulting in proactive monitoring, faster response, and decreased reliance on specialized skillsets.

The good news is that AIOps on the mainframe is no longer limited to those organizations with the resources to design and implement customized large-scale data collection and data science infrastructures. The technology for being able to consume and process the large volume of data captured on the mainframe, and the proven techniques to apply machine learning algorithms to that data, have matured to a degree of accuracy and scale where they are now implementable in a wide range of customer environments. Vendors have even evolved to the point where they are now shipping out-of-the-box models that can be implemented immediately to accurately detect existing and potential problems.

So, where to begin?

Many organizations have found success in implementing mainframe AIOps by starting with a narrow scope. Build AIOps onto your existing systems management platform rather than replacing it wholesale. Make sure your existing platform is current and that you choose a monitoring tool that provides a modern user experience and allows you to quickly and easily integrate AIOps use cases.

Starting with a focused use case, such as detection, and inputting historical data can help demystify the process by showing how known issues are detected and help prove the value of moving to an AIOps-based approach. Once you have successfully implemented that first use case, move to a second, such as probable cause analysis, again taking advantage of historical data to learn and test the new technology. This gradual adoption not only ensures that your organization is employing AIOps tools to their full potential, it allows employees to learn the tools and adapt processes without the upheaval of a sudden, major change.

The detect and respond model of operations management has served the mainframe well for decades, but the confluence of multiple factors has made it clear that a change is in order. With an accelerating digital economy, the increased need to include the mainframe in your organization's digital strategy, shifting workforce demographics, and availability of technologies that enable automation everywhere, the time is right for your organization to adopt AIOps on the mainframe.

April Hickel is VP, Intelligent Z Optimization and Transformation, at BMC

Hot Topics

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...