6 ms·
Building the System/360 Mainframe Nearly Destroyed IBM
- FpUser 2y agoThis was some great read
- ListeningPie 2y agoYour comment was reason enough for me to read it, 8/10
- noworld 2y agoThe successor IBM Mainframes are still alive... for the time being. https://www.redbooks.ibm.com/redbooks/pdfs/sg248329.pdf https://www.redbooks.ibm.com/redbooks/pdfs/sg248329.pdf
- froh 2y agooh, they'll stay around for another while. they also moved on three more CPU generations since that redbook, to z17. I think it's Linux on Z that makes it sexy and keeps it young, in addition to a number of crazy features, like a hypervisor that can share CPUs between tenants, and a hardware that support live migration of running processes between sites (via fibre optic interconnect) and the option to hot swap any parts on a running machine. It's doing a number of things in hardware and hypervisor that need lots of brain power to emulate on commodity hardware. _and_ it's designed for throughput, from grounds up. Depending on your workload there may be very good economical reasons to consider a mainframe instead of a number of rack-frames.
- rbanffy 2y ago> I think it's Linux on Z that makes it sexy and keeps it young They feel fantastic when running Linux, but, if you don't need all the reliability features that come with the platform, commodity hardware might be a better choice for the kind of workload that has evolved on Linux. > Depending on your workload there may be very good economical reasons to consider a mainframe instead of a number of rack-frames. Absolutely - it makes a lot of the administrative toil disappear. I know clusters are sexy, but getting the job done is always better.
- trollbridge 2y agoOther than IBM’s absurdly high pricing, they’re cheaper to run in almost every way than x86 machines (including cloud). I haven’t done the math to compare with aarch64/ARM. But most people don’t want to deal with the hassle of dealing with IBM.
- MrBuddyCasino 2y agoI suspect the main reason isn't just strictly economical. If you are Google or some such you can probably compensate by building smart software around commodity hardware, but most companies simply can't. Even if they have boatloads of money (banking, insurance) and can hire expensive talent, they simply can't successfully complete such an undertaking because they don't have it in their DNA, and management isn't incentivised to take on such a risky project. In this case they will just use a mainframe, even it isn't cheaper in the long run.
- cmrdporcupine 2y agoThing is Google does not use commodity hardware for their DCs as far as I can tell. They got famous for that back in the early 2000s but I think they abandoned that approach a long time ago.
- MrBuddyCasino 2y agoThey may design their own hardware, but their approach to scaling and fault tolerance is still the same: not a low number of fast and very expensive enterprise grade hardware that is unlikely to fail, but a huge fleet of servers that scale horizontally and that can tolerate the loss of a machine. Which is the Mainframe vs commodity server dichotomy.
- jasode 2y ago>Depending on your workload there may be very good economical reasons to consider a mainframe instead of a number of rack-frames. For legacy companies yes but it would be very hard for new YC companies or existing non-mainframe companies to create a spreadsheet showing how buying a new IBM Z mainframe would cost less than the latest commodity x86 or ARM servers in the cloud or on-premise. The IBM pricing for mainframes makes sense for legacy companies like banks and airlines with a million lines of old COBOL code that want to keep it all running with the latest chip technology. (The mainframes from a few years ago are coming off the lease and they need to upgrade to whatever new mainframe IBM is offering and sign another lease & service contract.) So, IBM mainframe prices are very expensive -- but legacy companies will pay it because migrating the code away from mainframes can be even more expensive. It's similar to expensive enterprise pricing of Oracle, Embarcadero Delphi, Broadcom etc that takes advantage of existing customers already locked into their products. Virtually no new tech startup with a greenfield project is going to pay Delphi $1599-per-seat for each of their developers. Only existing customers stuck with their investment in Delphi code are going to pay that. (https://www.embarcadero.com/app-development-tools-store/delphi https://www.embarcadero.com/app-development-tools-store/delp...) But some companies do endure the costs of migration to get out from IBM lock-in. There are lots of case studies of companies shifting their workload from mainframes to AWS/GCP/Azure. I can't think of a notable company that did the reverse. Even a mainframe hardware vendor like Fujitsu quit making mainframes and shifted to x86 running an emulation of their mainframe os. Yes, IBM mainframe can run other workloads besides COBOL like Java and C/C++ but no company that's not already using mainframes would buy & deploy to IBM's Z hardware for that purpose.
- Spooky23 2y agoIt’s a risk issue. 5 year high risk projects aren’t appealing to CIOs with an average tenure around 18-36 months. Even if it works, why should the next asshole get the credit?
- KerrAvon 2y agoI think the point is that IBM’s market is shrinking, and they can’t acquire new customers. They will eventually need to stop making mainframes because there will be a crossover between the cost for new mainframes for remaining customers vs transition to commodity hardware cost.
- speed_spread 2y agoA mainframe is the biggest single system image you can get commercially. It's the easiest, most reliable way to scale a classical transactional workload.
- rbanffy 2y ago> A mainframe is the biggest single system image you can get commercially It depends. As we have seen the other day, HPE has a machine with more than 1024 logical cores, and they have machines available to order that can grow up to 16 sockets and 960 cores on a single image of up to 32TB of RAM. Their Superdome Flex goes up to 896 cores and 48TB of RAM. I believe IBM's POWER line also has machines with more memory and more processing power, but, of course, that's not the whole story with mainframes. You count CPUs that run application code, but there are loads of other computers in there doing a lot of heavy-lifting so that the CPUs can keep running application code at 100% capacity with zero performance impact. > It's the easiest, most reliable way to scale a classical transactional workload. And that's where they really excel. Nobody is going to buy a z17 to do weather models or AI training.
- ryao 2y agoSGI’s UV 2000 could scale to 4096 logical cores and 64TB of RAM around 13 years ago. The current 4096 core limit in Linux is from that.
- jareds 2y agoDo you have resources that provide info on companies using Linux on Z and the benefits of this verses commodity hardware? I used to work for a Mainframe ISV but the majority of our software ran on z/OS. I only saw customers using Linux on Z to begrudgingly run software that wouldn't efficiently run on z/OS, mainly Java applications when customers didn't want to deal with the complexity of specialty engines. I realize because our software focused on z/OS I had limited visibility into the full operations at our customers.
- froh 2y agothe advantage comes with the full package, operations and all. you don't have racks with blades but one box or two, that you upgrade every few years and other than that your hardware side is covered. rewiring networks, reattaching storage etc all remotely, CLI, and most importantly you only pay what you use. you need one guy or a consultancy for the initial etc up and for fancy Config changes but once it's essentially set up you simply have a large Linux data centre and do Linux stuff. oh and you can hot plug additional physical CPUs into a running VM and pull it out and reassign when it's not needed, likewise RAM. that's somewhat difficult with commodity hardware. and there _are_ companies that value this and choose Linux on Z as a pure Linux deployment. but you have a point. if nobody in the building knows this, nobody's gonna call IBM and ask for a quote. it's simply not on anybody's radar.
- toast0 2y ago> Depending on your workload there may be very good economical reasons to consider a mainframe instead of a number of rack-frames. This may be true, but because there's basically no on ramp to running on a mainframe, there's no way anybody is going to try it unless they're already on a mainframe. Or maybe unless they really need something that only a mainframe can provide. But most companies can live with some downtime, and once you can live with some downtime, you have options for migration between sites, and options for migrating loads so you can swap parts on a stopped machine. Splurging on network infrastructure with multi-chasis redundancy is an easier step to take to get to a more reliable system than building against a totally different system architecture.
- timewizard 2y ago> This may be true, but because there's basically no on ramp to running on a mainframe You can get a partition of IBM Z to run in the cloud. The cost is about $5/hr for the smallest configuration. > Splurging on network infrastructure with multi-chasis redundancy is an easier step to take to get to a more reliable system than building against a totally different system architecture. Yes and no. If you truly need that redundancy than the mainframe is going to provide a much better version of it. SYSPLEXs and LPARs are some insanely powerful technologies.
- NelsonMinar 2y agoMy partner makes a living writing z/OS assembly language, has been for many years now. The platform is still going strong as a business. The main problem they face is all the folks who know how to program these things are retiring (or dropping dead at their keypunches.) It's very hard to convince new people to learn how to operate these systems.
- bityard 2y agoFor your partner's sake I hope you're right but is z/OS as a platform actually continuing to grow, or are they just having a hard time filling seats because it's hard to see a long and profitable future working on (what some might call) "legacy" systems? When I was growing up (decades ago, mind), my dad kept trying to convince me to get into machining. Lathes, mills, tool and die making, etc. In his line of work, he saw lots of machining companies basically paying all education and training expenses for new hires because their experienced old timers were retiring faster than they could be replaced. (He also thought computers were a fad...) I'm sure it was a good opportunity at the time. But nearly all of those companies eventually closed up because offshore manual labor was and still is way cheaper. If I'd had taken his advice, I'm pretty sure I would have had to reboot into another career at least once by this point.
- wglb 2y agoInteresting. What sort of applications does your partner work on?
- NelsonMinar 2y agoHe does system level stuff, enhancements to IBM's z/OS. A lot of their customers are big financial institutions, banks and the like that use MVS for transaction processing. His software augments the operating system and isn't application specific.
- EncomLab 2y agoAlan Kay has promulgated many famous truths about computer science - one of them being that among all fields of study, it has the least regard for the people and discoveries that brought it to where it is today. Maybe it's just my own sense of history as I move into my 4th and likely last decade of working with computers, but I find this to be both true and lamentable. This was a great article - thanks for sharing!
- bluGill 2y agoHow many of the people who made the steam engine possible do we remember? James Watt of course, but many many people were making contributions in material science, needed to make them useful. Not to mention many advances in values. No doubt lots of other areas as well, but I'm no expert in the steam engine.
- EncomLab 2y agoNot sure what you mean by this - it's not as if steam engines are an extensive technology today, and certainly no university is teaching "steam science", while nearly every school is teaching "computer science". Perhaps this is just the attitude that drives Mr. Kay's point home - do individuals who are interested in CS have little value for who and what has come before them?
- CamperBob2 2y agoTo be fair, everybody who takes a thermodynamics course owes 90% of it to the 'steam science' pioneers. Understanding what determines and limits the efficiency of heat engines was as big a deal in its day as the WWW is in ours, but unlike our own era, a lot of brand-new science and math had to be discovered by those engineers. Steam tech is much, much more interesting than it appears at first.
- nancyminusone 2y agoSure they do, it's just called fluid dynamics and thermodynamics. Enough to fill up about 1/3 of a mechanical engineering degree, if you're really into it (most aren't). Not that there's a lot of historical context to things as far as which people did what - most of that sort live on in names of techniques and methods (Rankine cycle, de Laval turbine, Carnot efficiency, etc.)
- froh 2y agoTIL that not only the software side was chaotic (served as the backdrop of Fred Brook's "Mythical Man Month"), but also the hardware side almost failed. the article here ends around 1971 --- the mainframe would later save IBM again, twice, once when they replaced aluminum with copper in interconnects, and then when some crazy IBM Fellow had a team port Linux to s390. Which marked the birth of "enterprise Linux", i.e. Linux running the data centre, for real.
- mananaysiempre 2y ago> [Porting Linux to s390] marked the birth of "enterprise Linux", i.e. Linux running the data centre Did it though? Or was it the gradual phasing out of mainframe-class hardware in favour of PC-compatible servers and the death of commercial Unices?
- rbanffy 2y ago> Or was it the gradual phasing out of mainframe-class hardware in favour of PC-compatible servers Proprietary Unix is still around. Solaris, HP-UX and AIX still make money for their owners and there are lots of places running those on brand-new metal. You are right, however, that Linux displaced most of the proprietary Unixes, as well as Windows and whatever was left of the minicomputer business that wasn't first killed by the unixes. I'm not sure when exactly people started talking about "Enterprise Linux".
- kevin_thibedeau 2y agoRedhat was doing enterprise Linux well before IBM was involved. It was the rational platform for non-legacy .com 1.0 businesses.
- froh 2y agonope. the first enterprise Linux was SuSE on s390, then came RH on x86 and then suse there as well. but RH marketing was better back then already :-D
- 2y ago
- cafard 2y agoThomas Watson, Jr.'s A Business and Its Beliefs was published in 1963 and makes no allusion to the S/360 work. It makes for curious reading today, for unrelated reasons.
- curtisszmania 2y ago[dead]
- scrlk 2y agoThe IBM Centennial Film has a short interview with Fred Brooks about System/360: https://youtu.be/VQ0PBve6Alk?t=84 https://youtu.be/VQ0PBve6Alk?t=84 Set to some nice Philip Glass music to boot.
- herodotus 2y agoMy Master's supervisor, at Wits university in Johannesburg, worked on the architecture of the 360 after graduating from the PhD program at Harvard. I remember him telling us how they went about deciding whether or not 32 bits would be a sufficient size for "most" floating point numbers. They were very systematic about it, scouring journals, talking with physicists and mathematicians and so on.
- PaulHoule 2y ago(1) Maybe I'm just a little too young but my impression was that the 360 and it's successors were not that big in scientific computing, certainly there were some big academic installations but I saw a lot more DEC machines (PDP-8 in the experimental lab, PDP-10, PDP-11 and VAX elsewhere) and by the time I went to college circa 1990 you were likely to see Motorola 68k-based "workstations" that were quickly replaced by RISC architectures like SPARC and PA-RISC which in turn failed to compete with the PC. Cornell had one of very few IBM 3090s with a vector unit (to compete with the Cray) just before I showed up, but when I did IBM had donated a message-passing based supercomputer based on the Power PC architecture. I only saw a 3090 (no vector unit) at New Hampshire Insurance which I got to use as a Computer Explorer. (2) I was taught in grad school in the 1990s to use floats if at all possible to reduce the memory requirements of scientific codes if not actually speed up the computation. (In the 1990s floats were twice as fast as doubles on most architectures but not the x86). I really enjoyed taking a course on numerics from Saul Teukolsky, what stood out in the class as opposed my reading to the Numerical Recipes book which he was a co-author of, was the part about the numerical stability of discretizing and integrating partial differential equations. If you did it wrong, unphysical artifacts of the discretization would wreck your calculation. Depending on how you did things rounding errors can be made better or worse, Foreman Action's Numerical Methods that Work and later Real Computing Made Real reveal techniques for managing these errors that let you accomplish a lot with floats and some would point out that going to doubles doesn't win you that much slack to do things wrong.
- wglb 2y ago> 360 and it's successors were not that big in scientific computing I do believe that is true. IBM did have the Model 90 series, which was on the way to being a supercomputer. Bur during that time CDC with the 6400/6600 etc was likely bigger in scientific computing.
- svilen_dobrev 2y agoi have also found these to be interesting, kind of selection/ analysis/ visualisation over memoirs of Lou Gerstner (part 2 is around s/360): https://juliusgamanyi.com/2018/12/28/wardley-maps-an-illustration-from-gerstners-book/ https://juliusgamanyi.com/2018/12/28/wardley-maps-an-illustr... https://juliusgamanyi.com/2019/06/18/wardley-maps-an-illustration-from-gerstners-book-part-2/ https://juliusgamanyi.com/2019/06/18/wardley-maps-an-illustr... https://juliusgamanyi.com/2020/06/25/wardley-maps-illustrated-through-gerstner-part-3-loop-2/ https://juliusgamanyi.com/2020/06/25/wardley-maps-illustrate... Now, reading the article, this "[rivalry].. So intense was it that sometimes it seemed to exceed the rivalry with external competitors.” reminded me of something old about Motorola.. where rivalry went to the need to reverse-engineering other depts' chips via 3rd party acquiring them.. www.chicagomag.com/Chicago-Magazine/September-2014/What-Happened-to-Motorola/
- kwanbix 2y agoAs an ex-IBMer, I miss the IBM of old. So much innovation. Now they are just a consulting company. So sad to see it go that way.
- winrid 2y agoIndeed. Their current goal as communicated to shareholders is literally to move all engineering offshore.
- talkingtab 2y agoThis whole thing is very cool and worth reading. BUT. I worked at a place that used IBM 360s. We ran stuff for engineers, a lot of Fortran along with assembly code. We had so much stuff going on we could not code up and run things fast enough. The engineer/scientist got frustrated. Then one day an engineer brought in an Apple II from home and ran the programs on that. The earth shook. The very ground beneath us moved. Tectonic plates shifted. The world was never the same again! I think it was Visicalc. Later there were other things. Soul Of A New Machine. The Mac. I wonder how the compute power of a current high end smart phone compares with and IBM 360? I know the graphics chip is better.
- winrid 2y agoA $50 smartphone is many orders of magnitude faster.
- PaulHoule 2y agoIf I had to compare computers based on one number it would be the amount of RAM. The 360 had a 24 bit address space which could fit 16MB of RAM although only the largest installations, like the one at NASA, were that big. iPhone 16s have 8GB of RAM so you're talking 512 times the memory capacity, never mind that my desktop PCs are all loaded with 4-8x times that of the phone and you can definitely get a big server with a few TB. An IBM 360/20 on the small side, however, ranged from 4kB to 32kB which was similar to home computers circa 1980, before it is routine to have a complete 64kB address space. Where the 360 crushed home computers was in mass storage, 9-track tapes could store 80MB contrasted to floppy disks that stored less than 200kB. Large storage compared to memory meant a lot of focus on external memory algorithms, also there was already a culture of data processing on punched cards that translated to the 360 (e.g. terminals have 80 columns because punched cards had 80 columns)
- kjs3 2y agoWhere the 360 crushed home computers was in mass storage Well...sure, you could put bigger storage on a mainframe. It's just money, after all. But you could put a tape drive on a home computer. And bigger disks. And a card reader, for that matter. Where the 360 really crushed the home computer was in aggregate bandwidth, via the Channel architecture. An Apple 2 could just about keep up with a floppy and a display. A 360 could keep up with dozens to hundreds of tapes, disks, card readers, terminals, printers and other things all at the same time. Large storage compared to memory meant a lot of focus on external memory algorithms I would agree with that. I would just argue the real mainframe advantage is a whole-system one and not point to a single factor (memory size).
- ChicagoDave 2y agoMy sister worked at IBM and one of my favorite stories is when Lotus tried to pressure IBM to spend millions on licensing, a few engineers went off and built their own spreadsheet application and IBM told Lotus to piss off.
- Synaesthesia 2y agoAnd this is all before integrated circuits, so the circuits are still very large, consisting of many circuits on boards mounted on a backplane. https://en.wikipedia.org/wiki/IBM_System/360#Basic_hardware_components https://en.wikipedia.org/wiki/IBM_System/360#Basic_hardware_... https://en.wikipedia.org/wiki/Solid_Logic_Technology https://en.wikipedia.org/wiki/Solid_Logic_Technology
- SoftTalker 2y agoThe reason the tape drives are in those tall enclosures are the vertical channels below the tape reels. That was for slack in the tape, there was a loop of tape hanging in each of the channels, so that tape reads and writes could be stopped and started faster than the heavy tape reels could stop and start.
- Henchman21 2y agoThis is super interesting to me, thanks for that. Are there any other hidden but well-known things like that?
- shrubble 2y agoTo add to this: they had $750 million in 1963 dollars, in parts and no shipping computers; inventory control was so bad that they had to have guys with clipboards to physically go into the warehouse and count parts. They announced it and started getting a huge number of orders; IBM hired 1000 people a month and kept up that pace of hiring for 5 years.
- RazorDev 2y ago[flagged]
- skmurphy 2y agoIt was a business decision driven by Tom Watson Jr. after listening to a lot of customer feedback. See "Father, Son, and Co." https://www.amazon.com/Father-Son-Co-Life-Beyond/dp/0553380834 https://www.amazon.com/Father-Son-Co-Life-Beyond/dp/05533808... his autobiography of his years at IBM, and beyond. The 360 project figures prominently.
- JJMcJ 2y agoThe well known book "The Mythical Man Month" is in large part based on the author's experience as one of the top people on the System 360 project, and what went wrong during the effort.
- emchammer 2y agoI liked the Mad Men plot about the computer arriving in the office. Everybody was trying to decide how to react to it.
- BXLE_1-1-BitIs1 2y agoz boxes use a flavor of VM to run all the LPARS and allocate memory and devices. z/OS, z/VM and Linux all run as VMs. Then there's CMS which runs under VM; theoretically it could run as an LPAR, but I've not seen that as running DIAGNOSE (VM system call) to the LPAR hypervisor could be disruptive. It would be interesting to drop DIAGNOSE into a z/OS environment, but I suspect it would be intercepted. I much prefer z/VM to z/OS as a development environment. At one shop, I developed products under VM for deployment under both VM and MVS. Many early S/360 installations ran 7070 and, I guess, 1401 emulators. Eventually with VM, the SIE (Start Interpretive Execution) instruction appeared. A form is running LPARs.