That’s more of a training / staffing issue than a tech stack issue. I’ve seen similar outages at my clients in distributed systems. A lot of mainframe staff has

That’s more of a training / staffing issue than a tech stack issue. I’ve seen similar outages at my clients in distributed systems. A lot of mainframe staff has been outsourced / offshored and those providers suffer constant turnover because the money and job prospects in distributed systems is generally better. Mainframe jobs pay well at the very apex of skills, but if you’re coming up through the ranks in an outsource provider you’re a cost not profit center. The compensation package and work life balance are good if you are with a company that keeps everyone in house, trains in house, have a deep bench of expertise who maintain the systems in an orderly fashion, and have a continuous succession plan for staff. Super low drama, and they keep the financial lights on in the house by processing the bulk of profit-generators’ needs. These tend to be in places like stodgy COBOL shops the Cool Kids would rather gnaw their feet off to avoid, though. The part many people miss when comparing mainframes and distributed is you get all that mainframe magic with the application programmers accommodating the architecture little if at all. But your system programmers (system admins in Linux) have to be top tier. You can accomplish most if not all of that same magic in distributed architectures with parallelizable workloads. But your application and devops staff have to be top tier.