Mainframe Blog

How to Respond Quickly to Runaway Abends

< 1 minute read
Mark Schettenhelm, Paul Spicer

Many of us have experienced the phenomenon: New code reaches production and abends, then abends again and again. Multiple users could each be attempting the same abending transaction on their mobile phones over and over, or automated processes could be reattempting after each failure. These scenarios could create a runaway abend situation that negatively impacts performance and availability. A bug in one application could have effects that spread throughout your system, causing headaches for engineers and negative experiences for your customers. So, how can you shave minutes off of your response time and limit the impact?

BMC AMI DevX Abend-AID recently introduced a new option to help improve webhook notifications. Abend-AID will keep a running count of repeatedly occurring identical abends, allowing you to set thresholds—100, 1000, or maybe even just 10 times, and notifying you once this threshold has been reached so you can respond.

So, with runaway notifications solved, what can be done to resolve the underlying issue? This is where BMC AMI Ops Automation comes in. BMC AMI Ops Automation can be configured to react to abend notifications, triggering an event and driving an automation rule to take an in-context action based on the information provided in the notification.

Some examples of these automated actions include:

  • Canceling the job
  • Generating an alert
  • Gathering additional diagnostic data
  • Emailing developers so they can analyze the situation and provide a solution
  • Opening an incident ticket
  • Running an EXEC to perform custom automation

Applications running on the mainframe can be accessed by many concurrent users, and defects can spiral out of control unless you receive immediate notifications with automation ready to respond. BMC AMI DevX Abend-AID and BMC AMI Ops Automation deliver these capabilities to support you and your customers. For more information, visit our BMC Community post.

Access the 2023 Mainframe Report

The results of the 18th annual BMC Mainframe Survey are in, and the state of the mainframe remains strong. Overall perception of the mainframe is positive, as is the outlook for future growth on the platform, with workloads growing and investment in new technologies and processes increasing.

These postings are my own and do not necessarily represent BMC's position, strategies, or opinion.

See an error or have a suggestion? Please let us know by emailing

BMC Brings the A-Game

BMC works with 86% of the Forbes Global 50 and customers and partners around the world to create their future. With our history of innovation, industry-leading automation, operations, and service management solutions, combined with unmatched flexibility, we help organizations free up time and space to become an Autonomous Digital Enterprise that conquers the opportunities ahead.
Learn more about BMC ›

About the author

Mark Schettenhelm

Mark is a DevOps Evangelist and Lead Product Manager at BMC who has experience working with developers around the world in Source Control Management, Testing, DevOps and Application Portfolio Analysis. He is a frequent conference speaker, webinar presenter, blogger, and columnist, often explaining the benefits of bringing Agile and DevOps to mainframe development and encouraging development teams to adopt new methodologies and continuously improve.

His writing has appeared in Enterprise Executive and Enterprise Tech Journal and he is a frequent contributor to and SHARE Tech Watch. Mark is currently the Lead Product Manager for BMC products in Source Control Management, Deploy, Code and Fault Analysis.

About the author

Paul Spicer

Paul Spicer is a lead product manager for BMC’s zSolutions and is responsible for Automation, Middleware Management and Install strategy.

Paul has over 35 years of experience working with IBM mainframe systems, with over 30 years providing systems management solutions in roles spanning software development and product management.

Prior to joining BMC, Paul worked at software vendors including Macro4, Candle Corporation and IBM.