Blog

What’s Wrong With the Mainframe?

2 Pages

Something is wrong with the mainframe. Unfortunately, most people don’t realize what it is.

One piece of evidence that something is wrong with the mainframe is the near-total absence of positive media coverage regarding the platform. This is definitely odd given the fact that the mainframe remains the transaction engine of choice for the global economy.

However, very little of the rhetoric surrounding the mainframe seems to be based on an accurate, empirical understanding of the platform’s real issues. That’s why it may be useful to first review a few things that are not wrong with the mainframe:

  • The mainframe is not too expensive. This common myth is based on decades-old denial about the true cost of distributed infrastructure. Yes, mainframes require a high capital outlay when compared to commodity PC servers. But keeping that commodity infrastructure up and running has proven to be one of the most expensive and fruitless undertakings in history. In fact, TCO for distributed computing make capital IT costs look like pocket change.

To virtualize their distributed server environments, for example, enterprises are enriching a single software company—VMware—to the tune of $6 billion annually. In stark contrast, the entire mainframe ops tools market is just $10 billion for all vendors combined. That’s why Rubin Worldwide found that 1) over the past five years, costs at server-intensive IT shops have risen 65% more than at mainframe-intensive IT shops, and 2) mainframe-intensive companies earn 28% more per dollar of IT infrastructure than server-intensive companies.

  • The mainframe is not a security problem. Contrary to certain recent inaccurate reports, the mainframe is in no way a threat to any organization’s information security. Just the opposite is true. None of the many recent high-profile hacks (Sony, Target, etc.) have anything to do with penetrating mainframe defenses. On the contrary, they are almost all the result of poor security practices associated with distributed networks. The mainframe remains vastly more secure than distributed systems when it comes to intrusion exploits, malware, and every other category of security threat.
  • The mainframe is not a migration problem. Despite its technical and economic superiority to distributed platforms, a surprising number of industry voices still contextualize the mainframe as a “legacy” platform from which enterprises need to migrate their core applications if they are to succeed in the digital economy.

This makes no sense. First of all, why would any organization migrate its most critical applications from a supremely reliable, secure, scalable and secure platform to a relatively risky and expensive one? And why would any CIO allocate limited resources to a low- or negative-ROI migration project when so many other urgent imperatives clamor for his or her limited IT resources?

The answer is that there is no reason. That’s why analysts like Gartner are reporting minimal migration activity—and why 88% of CIOs assert that their mainframes will run existing and even net new workloads for at least another decade.

But if these are not the mainframe’s problems, what is?

The Apathy Virus

The mainframe, it turns out, is vulnerable to a virus. But this virus is not digital malware. It’s a cultural pathology: Apathy.

Apathy has infected mainframe culture in several ways. One is the complacency that comes with success. Mainframe teams have done a nearly flawless job of maintaining the availability and integrity of core business applications and data, decade after decade. So it’s natural that they would rest on those laurels—especially since the hard work of innovation has been largely left to their peers in the distributed, web and mobile spheres.

The illogic of platform migration has also lulled mainframe teams into an apathetic mindset. Mainframe applications represent irreplaceable and highly valued intellectual property. And they aren’t going anywhere. So mainframe teams have a certain level of job security that insulates them from the intense pressures that drive innovation in other areas of IT.

2 Pages