A hunt for the government's oldest computer
muckrock.com
muckrock.com
In 2001, the Australian Navy still used the Mk152 computer. https://en.wikipedia.org/wiki/UNIVAC_418 on the last remaining Charles F Adams class destroyer, HMAS BRISBANE.
It was a general purpose computer entirely constructed from individual transistors with magnetic core memory. We had two of these onboard and if both were down we couldn't fire the missile system. I had 3 sailors dedicates solely to keeping these ancient machines running.
We got to diagnose some pretty cool bugs, like what happens when the card corresponding the the lowest significant bit of the least use register has an intermittent fault due to a bad mechanical connection.
In my opinion, hardware that can be repaired and software that has been running in production for years is not in need of an upgrade. The need to refresh software or hardware exists purely to keep vendors in business and even just to keep some I.T. departments busy and their C.V.'s up to date.
Provided a system is working reliably and is not dependent on changing external requirements there is no need to upgrade. The risk to a business or entity from the constant upgrade cycle is far greater than keeping something existing and tested running.
It doesn't even have to fail in a software/hardware specific way. If your floor collapses or is flooded, and you're using old mainframe with code written in Natural or similar, what's your DR story? Which actually makes me curious - does anyone know what the DR plans look like for companies using 70's mainframes? Let's say a critical S/370 in company basement? (and yes, I'm aware that new z series should virtualise that just fine, but in practice... if you lose a mainframe, what do you even do?)
Aside from comically high maintenance costs (which only the government and perhaps banks can afford to pay), such organizations also need to _hire_, _train_ and _retain_ staff that can actually do their jobs on these things. It simply isn't feasible to keep let alone recruit strong talent in an environment where legacy goes beyond a certain level. Yeah, good employees _ARE_ going to be concerned about their C.V.'s and that is understandable.
An excessive "upgrade cycle" may, in some cases be risky, but a vastly more common problem is orgs that don't change/adapt/upgrade fast enough. That has risks and costs as well.
I toured NORAD inside Cheyenne Mountain back in 1990 or '91, back when you had to submit background information to apply for the tour, and I saw that computing gear. It was amazing to see buildings on giants springs and caverns with Diesel locomotives in them for back-up power.
I used to run a couple hobbyist/enthusiast sites and mailing lists for people who collected and restored old DEC equipment (and I still run an all-systems-welcome "rescue" list). Shortly after 9/11, I got a phone call from someone working in the Pentagon who was looking for parts to repair a VAX that had been damaged...
Yep, today they tend to look like something out of Battlestar Galactica:
https://en.wikipedia.org/wiki/IBM_System_z
I've started working with Z/OS on Zseries machines just a few months ago. Obviously, I'm still learning. There is a _lot_ to learn- it's nothing like linux :0
Edit: Not sure why I am being down-voted. A lot of banks still use mainframes:
http://mainframes.wikidot.com/
http://www.networkworld.com/article/2916081/network-manageme...
I found the second link you posted to be quite baffling; I have worked for several companies where I had to integrate newer and older systems, and I would never list "integration" as a reason to use a mainframe. Yes, it can be done, but in my experience the assumption is that the mainframe must be worked around, with all of its fixed-width EBCDIC glory.
http://www.huffingtonpost.com/2014/05/01/floppy-disk-nuclear...
And of course we're still using operating systems from the 70's - Unix (in Linux form) and VMS (in Windows form).
EDIT: Typo, Corrected 80's to 70's.
https://en.wikipedia.org/wiki/Dave_Cutler
Cuttler and a core of VMS team exited en masse to work on NT. In fact, he coined the term "WNT" as a play on "VMS", each letter is a successor to the corresponding one. (c.f. IBM <==> HAL)
http://windowsitpro.com/windows-client/windows-nt-and-vms-re...
http://www.bloomberg.com/bw/stories/1993-04-25/flying-in-pla...
http://dailycaller.com/2015/07/28/faas-air-traffic-control-u...
http://www.pcworld.com/article/249951/if_it_aint_broke_dont_...
This article does mention this though: A recent federal review found that the U.S. Secret Service uses a mainframe computer system from the 1980s.
This article was pretty popular here a few months ago: http://www.theatlantic.com/technology/archive/2015/11/why-do...
http://www.pcworld.com/article/249951/if_it_aint_broke_dont_...
Last I heard, the budget and plan to replace it got thrown out as a cost saving exercise, but I haven't been involved in the Hawaii tech scene for nearly 3 years now.
https://www.reddit.com/r/sysadmin/comments/25mp2r/punch_card...
Still amazing they never upgraded that poor sod.
I'm also aware of a network of NT4 Alpha boxes running in production.