10 ms·
On the strange joys of mainframe OSes that have survived into modern times
- NonNefarious 4y agoInto "mo?" Whatever that is. Buried.
- KolmogorovComp 4y agoModern times
- Eleison23 4y agoCloud services and hyperscale data centers are arguably modern mainframe-class systems. If you look at them from the perspective of the provider, they have a lot of mainframe type features that distinguish them from micros or supercomputers. In the 70s, VM/CMS dominated the time-sharing landscape, and everything old is new again.
- qaq 4y agoReliability is nowhere near mainframe
- froh 4y agoyup. error detection in the CPU (Alu, Decoder, etc) traps into the hypervisor which fires up a spare core, transfers the registers over to it and calls the technician. technician calls you to tell you "your machine needs maintenance" and at application level there was a short "mouse hang" latency for this hardware failure. and of course that works cross-site, too, hot moving running software across data centres at the hypervisor level, because you want one data centre downtown, one at the airport. but it's not just for finance. some mainframe customers have virtualized thousands of "your personal domain and web server running php/perl/nodejs" on a single physical machine which shares a r/o mounted /usr, in ram, transparently. customer X needs more ram? click click life assign more ram. needs more cpu? activate another core. the Linux virtualization Features to support hit cpu and ram swap were driven by the mainframe guys from IBM, years ago.
- greggsy 4y ago> some mainframe customers have virtualized thousands of "your personal domain and web server running php/perl/nodejs” Are there hosting providers offering this type of service?
- rwmj 4y agoIBM Cloud offers Z systems: https://www.ibm.com/community/z-and-cloud/ https://www.ibm.com/community/z-and-cloud/ I imagine they're absurdly expensive like the real hardware.
- retcore 4y agoOnly available for existing Z/OS sites via your organization rep.
- froh 4y agothat was around 2010/2012, eg page 15 here https://www.slideshare.net/hcl/effective-web-hostingonzlinuxwhiteboardv1 https://www.slideshare.net/hcl/effective-web-hostingonzlinux... however virtualization on arm and Intel has meanwhile matured enough to replace that business model.
- bionsystem 4y agoWhat would prevent, in your opinion, to make some changes to current commodity hardware architectures (say, x64, arm...) to allow for mainframe-like scalability and reliability ? As per the article, how is the jitted/interpreted world of languages so bad ?
- ianai 4y agoECC bring the norm and better error handling all around. OSes that better handle memory and uptime. Possibly something like a user session being accessible from allowed terminals and applications that call for that. Think hotel front desk staff or anyone public facing who move from desk to desk.
- bayindirh 4y agoJust no. They are very large herds of cattle systems, which act like as a big pet system, because it tolerates small blows. A mainframe is a single pet, which can live undisturbed even with moderate size blows, and can host a sizable herd of cattle systems without even noticing on the load monitor.
- awesomeMilou 4y agoEvery time I hear someone advocating for mainframes, they always praise them and make them appear as something like a computing behemoth, that, while expensive outperforms any commoditiy hardware at the tasks it's good at, wether it's in performance or reliability. But there's never any real world use case. It's always just "If you're running a mainframe, you don't care about money". No performance benchmarks, no architecture comparisons. You get shown an architecture diagram of a mainframe, next to one of say, a cloud system and you get asked "See??", like the conclusion is obvious. > Instead, we got lowest-common-denominator systems. Not what was best, merely what was cheapest, easiest, and just barely good enough – the “minimum viable product” that an industry of shysters and con-men think is a good thing. How is this _not_ a good thing?? >But mainframes aren’t. They cost a lot, and rental and licensing costs a lot, and running them costs a lot… everything costs a lot. Meaning you don’t use them if you care about costs that much. You have other reasons. What those are doesn’t matter so much. ...which is exactly my point! Yeah it makes sense that there is a separate ecosystem for mainframes! Because from the outside and these kind of arguments it looks like IBM has been siphoning off some great marketing in the 80s and 90s and _really_ ignorant managers in charge of purchasing at large banks and the US gov. On an unrelated note, I kinda made the experience that people that like mainframes usually have some weird obsession with high level computing architectures. Is there maybe a correlation?
- zppln 4y ago> No performance benchmarks, no architecture comparisons. Yeah, I remember dipping my toes into this world when I was trying out COBOL a few years ago. IIRC they market these things with "transactions per second", which doesn't exactly lend it self to direct comparison with other systems...
- HyperSane 4y agoIBM actually forbids customers from sharing the performance of its z/OS mainframe performance benchmarks, which should tell you that they must be terrible for the money.
- neverartful 4y ago
- captainmuon 4y agoI don't really share the reverence for mainframes. While they have certain cool unique features, like extreme resiliance, that doesn't matter very much because all the low-level details can be abstracted away. We have learned to build reliable systems on "commodity" hardware. In all the other places where mainframes are different, they are not only utterly alien, but I would also argue inferior. Focus on 60s languages, weird menu-based OSes, no proper Unicode support (judging from plane tickets and payrolls with missing symbols), and so on. That they hold out in "important" areas like banking and insurances is especially damning. This is the "allocation" layer of our society and is also hopelessly obsolete. The way we allocate resources has not caught up with our technological development. My personal belief is, one day, when we make the step to "capitalism++" - I don't know what it will look like, but it will compare to our current society like that compared to feudalism - then all that legacy infrastructure will become unneccessary.
- adwn 4y agoThat was a wild ride – from a reasonable start of "mainframes are a sub-optimal compromise" via "important foundations of our society rely on obsolete systems" all the way to "we'll replace capitalism with something completely different and better, but I don't know what".
- 2fast4you 4y agoThey said we’d replace capitalism with another version of capitalism, he didn’t say it would be better
- rahen 4y ago> All modern computers are microcomputers I'm not sure if an IBM i system would really qualify this way, it's mini software running on downscaled mainframe hardware. IBM i is probably the last mini out there, it will feel completely alien to someone coming from the microcomputer world (say, *nix and Windows, x86 and ARM).
- trasz 4y ago“Mini” is just a marketing name at this point. The “i” is just a POWER machine - a micro - running a weird operating system.
- rahen 4y agoIt's not even marketing since IBM doesn't use this terminology. But i is still quite removed from the micro standards: POWER, EBCDIC, COBOL, RPG, 5250 terminals, and the SLIC/TIMI/LPAR abstractions. The typical "micro" app would use x86, UTF-8, Java/C++/Rust/Go on top of a general public system like Linux. Well at least both use 8 bits words, it hasn't always been the case.
- lproven 4y ago[Article author here] It's not really, you know. IBM i is very interesting: the last mainstream single-level store system. This is a concept I've both talked and written about in recent years -- examples here on HN: https://news.ycombinator.com/item?id=26066762 https://news.ycombinator.com/item?id=26066762 https://news.ycombinator.com/item?id=32314814 https://news.ycombinator.com/item?id=32314814 Saying that, I've done very very little work on the system. One job ever, really, 20Y ago. But IBM i is OS/400, yes, a minicomputer OS, yes -- but running on IBM P series, i.e. a POWER server, i.e. a modern RS/6000. It's a RISC workstation. Not even slightly mainframe-like. Other minicomputer OSes survive, notably VMS, now on x86-64. https://www.theregister.com/2022/05/10/openvms_92/ https://www.theregister.com/2022/05/10/openvms_92/ <- Another of my stories, just so you know where I stand. So, yes, mini OSes survive, sure, but not really any mini hardware. Arguably as minicomputers died out they evolved into workstations, and those have now died out, too. 99.99% of the workstation market is basically high-end PCs now, if we count modern Macs as sort of honourary PCs. (Arm Macs are in some ways more like desktop/laptop-shaped iPads, really.)
- thriftwy 4y agoI'm pretty sure nothing serious runs in mainframes outside of US and maybe EU. They have all that infrastructure like banks and planes and it looks quite modern and resilient.
- wokkel 4y agoUnless understand your comment wrong: most older EU banks run their core on mainframe. Sure the webapp to see your account is running on some websphere/j2ee or nowadays maybe even angular server. But that's just a gateway to the real accounting system on the mainframe.
- __d 4y agoJapan? NEC, Hitachi, and Fujitsu all used to make mainframes. Hitachi has merged their line with IBM z-Series, but I think it's still for sale? Fujitsu still sells several lines, and NEC still sells in Japan. I suspect their customers are pretty similar though: banks and airlines.
- jasode 4y ago>I read this wonderful article on mainframe OSes. As irony, the url link points to an article mentioning the Unisys mainframe. Unisys later switched to running on commodity x86 servers with a Unisys emulation on top: https://www.google.com/search?q=unisys+clearpath+shift+xeon https://www.google.com/search?q=unisys+clearpath+shift+xeon >, and that you don’t need all the fancy scaling infrastructure because one modern box [mainframe] can support a million concurrent users no problem, and a few such boxes can support tens of hundreds of millions of them, all in something in the corner of one room, with an uptime of decades and no need for any cloud. But it’s hard to do it that way, The author proposes that "mainframes-are-superior" by vague generalizations and no performance data. As a case study, consider that the Sabre travel reservations was the first IBM mainframe commercial customer since 1960. With 6 decades of experience with IBM 360 and Z upgrades, they'd know more about running mission-critical performance workloads on mainframes than just about anyone. And yet, they've been migrating off of mainframes to AWS + Azure + Google cloud : https://www.google.com/search?q=sabre+migration+multi-cloud+google https://www.google.com/search?q=sabre+migration+multi-cloud+... To think of the opposite case from Sabre, let's consider a new YC startup today with no legacy IT systems. Thinking from first principles (i.e. raw math of cpu & io performance & costs on an Excel spreadsheet), what situation makes sense to build the solution on an a new IBM z16 mainframe instead of cloud? If one is an old bank already running an older IBM z14 or z15 mainframe and wants the next iteration of performance improvements, a z16 upgrade is the simplest so probably makes the most financial sense. But without a "legacy IT" constraint, what's the compelling spreadsheet model for a YC company to choose a mainframe?
- dangus 4y agoAlso, supporting a lot of concurrent users is easier when the capabilities of the services being offered are very basic. Banks weren't doing things like providing millions of customers instant OCR processing of checks in the mainframe days.
- mhh__ 4y agoMigrating away from mainframes can also be just because of talent availability but also lock in. Where I work we have processes that would make perfect sense chucking jobs at a mainframe (if we implement our language on it...), but IBM have no competition so it's super risky.
- abrax3141 4y agoRelevant previous discussion: https://news.ycombinator.com/item?id=30505219 https://news.ycombinator.com/item?id=30505219
- magic_hamster 4y agoThis actually got me fairly curious as to what the big difference is between mainframes and regular ol' micros. I don't think I ever used a proper mainframe, and I honestly wanted to know more. The author keeps building up to this massively different, otherworldly system, and then just finishes without ever answering. I did feel some contempt towards certain developers (who dare call themselves software engineers) and there was definitely an "old man yelling at cloud" undercurrent. If only I could learn something of merit, that would have been worth it. So I guess it's up to us plebs to go and see what makes mainframes so different. How the "weird" custom architectures work. What's it like to work on one and write code for it.
- Tor3 4y agoThe maybe most distinguishing feature of a "mainframe" is intelligent I/O channels, which offloads a lot of what would otherwise be CPU work. And those I/O channels is why the PDP-10 was called a "mainframe" while the rest of the PDP series (without I/O channels) were called "minicomputers". There's more, but it depends on the system - some can do maintenance on parts of the system while still operating.
- HyperSane 4y agoThe x86 world is getting I/O channels in the form of "SmartNICs" which are NICs with substantial processing power.
- rbanffy 4y agoThey also have it with disks local and remote. The idea is that the CPU is running user code 100% of the time and that it doesn’t need to wait for anything.
- neverartful 4y agoWith the mainframe all disks are external. This diagram [0] does a good job of showing that. [0] https://en.wikipedia.org/wiki/Count_key_data#/media/File:IBM_CKD_Arch.png https://en.wikipedia.org/wiki/Count_key_data#/media/File:IBM...
- trasz 4y agoThere is a reason why there are no proper benchmark results for mainframes available, and why the EULA prohibits publishing them.
- neverartful 4y agoBack when IBM changed the branding on their hardware lines, it was done to help people identify WHY you would pick one platform versus another. z (mainframe) = "Zero downtime" i (as/400) = "integrated" (e.g., DB2 and stuff like processing queues is baked into the OS) p (rs/6000) = "performance" x (x86) = was sold off to Lenovo after a few years See the "p"? If you need maximum performance, you go with POWER and run AIX or Linux.
- tristor 4y agoAs someone who’s worked deeply on mainframe and minicomputer systems and then worked even more deeply in the cloud, there is really no point to mainframes anymore unless you are doing a realtime application, which in most cases is unnecessary. The only value proposition I see is realtime redundancies, which are physically impossible with geographically distributed systems, but par for the course on mainframes. For most non-realtime applications, though, you can achieve same or better uptime for cheaper and with better flexibility building in the cloud.
- _8j50 4y agoWhay is a mainframe's redundancy/uptime? > 5 9s?
- Tsiklon 4y agoA mainframe has 100% uptime. Redundancies are baked in by design, hardware maintenance can be performed while the system is live
- _8j50 4y agoIf that is true then that is enough of a selling point. Cloud providers with 5 9's have one or two outages a year. If you need the uptime for systems that can't have one outage in a decade, is there a competing solution?
- __d 4y agoNonStop? Originally from Tandem, then bought by .. Compaq? And then HP, now HPE. Not a mainframe, but designed and built for 100% uptime. They used to do demos where you could open the cabinet and pull out boards at random, and it'd just keep going. It migrated from custom hardware, to Itanium, to x86-64. It's a custom OS, but has a Unix-like layer on top for ease of porting stuff.
- jimmux 4y ago
- hatsuseno 4y agoIn jest I'll also assume the author could write a similar article lamenting what storage tech could have been, but instead everyone with data that mattered took the maintenance hit with RAID and called it a day. Commoditization is, to me, just a natural effect of product development in a free market, capitalist(-ish) society. It feels to me that as long as much of the population is chasing financially optimal outcomes this will continue to happen, and that may be okay.
- 13of40 4y ago"minimum viable product" I've heard a few folks use this term disparagingly lately, and I just want to point out that the spirit of an MVP isn't that you do the bare minimum required to huck your product to an unsuspecting customer. The point of an MVP is that every milestone you deliver something that's actually useful and functional in some way, end-to-end. The alternative to an MVP is a junk mock-up with all of the technical debt swept under the rug and the devs whistling and looking the other way when questions start coming out. Also, I loved the article.
- reaperducer 4y agoI'd like to see an article about the joys of mainframe operating systems that didn't survive. I cut my teeth on a PR1MEOS machine at SUNY New Paltz. Great system. But there is no modern emulator and almost zero information about it on the internet.
- bhauer 4y ago> A handful of grumpy old gits know that if you pick the right languages, and the right tools, you can build something to replace this 2nd level system in the same types of tools as the first level system, and that you don’t need all the fancy scaling infrastructure because one modern box can support a million concurrent users no problem, and a few such boxes can support tens of hundreds of millions of them, all in something in the corner of one room, with an uptime of decades and no need for any cloud. I suppose I am a grumpy old git, then, although I did not think of myself that way until recently. In the past decade or two, I've seen computer science lose its collective appreciation of the staggering potential of hardware. This has steadily resulted in software being built with tremendously over-engineered, hyper-complicated, cloud-first architectures that barely match the throughput of a single box running a high-performance platform (and for the record, "high performance" can still be relatively ergonomic via Java, C#, Rust, and so on). The scale of hardware, clock cycles, bits per second of bandwidth, etc., being squandered on modern cloud-first highly complicated architectures boggles the mind. I fear there is no strength behind any pendulum swing back to architectural simplicity, appreciation of the available capacity of hardware and how to use it, and local-first.
- phoehne 4y agoI think that's changing. You're seeing more companies investing more in custom silicon. Like Microsoft, Amazon, and Google all make custom silicon to support their cloud efforts. That's expected to increase over time. Apple has shown that if you don't settle for BOG standard hardware you get better than BOG standard performance.
- fock 4y ago> I fear there is no strength behind any pendulum swing back to architectural simplicity, appreciation of the available capacity of hardware and how to use it, and local-first. I'm pretty sure, the ecological devastation we are living will raze these things. If we are lucky we can salvage a bit. And the whole industry of the last 20years isn't worth saving.
- bsder 4y ago> I fear there is no strength behind any pendulum swing back to architectural simplicity, appreciation of the available capacity of hardware and how to use it, and local-first. The reason why there is no strength is that "cloud" seems to be the only way to monetize software.
- retrocryptid 4y agoWhat does this have to do with mainframes other than the word "mainframe" is in the title and it links to a blog post where someone mentions Unisys. BeOS and OS/2 were operating systems that predominantly ran on PC class systems.
- ngcc_hk 4y agoIt is never an issue of “or” (select one) or “and” (select all) but to think in multiples (and not even necessarily ecosystem that is linked). The key is it is part of the solution to many different ad possibly unrelated problems. Like playing with pi you have accessed to ports. And playing with mainframe they have access to lots of io ports. And controlled access to thousands of terminals. Pc is (in the older days) isolated calculation machine (excel/lotus 1-2-3/visicalc, words/WordPerfect and multimate/wordstars, real slides vs PowerPoint) and networked machine (unix, internet/decent and SNA). Many different species and some isolated and some linked. Also there are many mainframe in the past if one refers to a machine which has lots of CICS system. Dos/vse is sort of mainframe. Even though it is much smaller than mvs. And music, vms etc. The question is not why strange but rather can they have a place or a niche to survive. And if so, why. And if not really not. For example windows/NT to today windows servers are evolved like bird from the extinct dinosaurs called dec (at least the team is, dna or gene there but not the hardware). If you want one ring (do they still use the most unreliable in operation due to its being most relatable designed token ring?) to rule it all, it is stil mainframe. Strangely in the peak hour, we are considering the transaction processing system as mainframe is not that non-stop and the front end processor sometimes has to be non-mainframe. One thing in perspective is that in 1960-2000 you can use that to handle thousands of terminals with only 16 MB memory. That niche is …
- kukkeliskuu 4y agoI think one cannot understand the usefulness of mainframes without adding data integrity to the picture. Let's take a bank or an insurance company. For them, data integrity is of utmost importance. If you miscalculate bank account balance or insurance payment by one dollar, you erode trust, which is the most important asset they have. You will have data in multiple systems, none of which have the complete picture of all the data. So you need data integrity over multiple systems. Most modern architecture books recommend REST microservice architecture and "eventual consistency" approach to data integrity. The use of "sagas" is recommended for implementing this data integrity. However, this is not enough if you have high on-line data integrity needs, such as the banks have. And even if your needs are not as high, it is very difficult to get eventual consistency "right". On mainframe platforms, you have TP monitors (such as IBM CICS). Within TP monitors, you implement services, which is very similar to "serverless functions" such as AWS Lambda, but with distributed transactions. These TP Monitor services may be distributed across multiple physical "servers", and we can scale up the number of these services if needed. The platform provides reliability that is easily as high as AWS Lambdas. Also, you don't need to deal with the container startup time issues or pay for the container virtualization overhead. But the biggest benefit TP Monitor services have over modern "serverless functions" is the support for distributed transactions. I can call another service from within a service inside the context of the same global transaction, and the platform will take care of the distributed global transaction handling for me. This is essential when you need to guarantee high data integrity over various systems. There is at least one TP Monitor (Oracle Tuxedo) that runs on Linux as well, but if you look at the tooling, it resembles more the mainframe world than modern development. In my understanding there is no modern platform with this kind of data integrity guarantees. (Caveat: Although I am involved in a mainframe modernization project in a company in a related field, my knowledge of mainframes is fairly limited.)