4 ms·
This is so cool. Especially given that this thing can run Linux. I had a sorta-kinda similar experience in college years ago. My college (a small community
by mindcrime 11y ago
This is so cool. Especially given that this thing can run Linux.
I had a sorta-kinda similar experience in college years ago. My college (a small community college in the middle of nowhere) had received an IBM AS/400 machine as a donation. I signed up for some "Survey of Operating Systems" class, and when I showed up the first day, the instructor (who already knew me) goes "Phil, your job is to take the AS/400, install an OS and get it on the Internet". Needless to say, at that point in time, I'd never seen or touched an AS/400 before.
Anyway, the instructor pointed me to a room with an AS/400, a huge stack of tapes (for the OS), a huge stack of manuals, and basically said "just do it." It was an interesting experience, but in the end, I got the thing on the 'net so you could telnet to it and work on it. And that indirectly led to the beginnings of my career in IT, as my first real IT job was as an AS/400 operator / Netware admin, and it was a job this instructor connected me with after this class.
So here's to taking vintage IBM equipment and dorking around with it and putting it on the Internet!
- larrik 11y agoI've installed OS's on plenty of AS/400's for a prior job. When everything goes perfect, they are still a complete nightmare. I can't imagine how you pulled it off, frankly.
- mindcrime 11y agoLet's just say it took me a while, and a lot of trial and error.
- sixothree 11y agoAs someone who collects vintage computers my suggestion is to document the process. Having to re-discover an obscure command is just painful.
- apecat 11y agoPlease feel free to share some of these nightmares. These systems are so surrounded by an air of mystique and vague hints of danger, and I've mainly tried to read up on the supposed benefits of using mainframes to get why anybody would use them. I'm honestly interested in all kinds of IT horror stories, I need a reminder every now and then to keep the IT part of free from things that break and require tinkering (starting with unnecessary on-premise servers in small biz settings). Mainframes are obviously nine orders of magnitude beyond what I ever to, but still: the lessons of expensive and proprietary can be somewhat universal.
- nickpsecurity 11y agoOnce you get them running, they stay running. Like OpenVMS systems, you'll occasionally hear stories of how people lost them. They'd run without maintenance for so long that people would forget where they were when they needed it. My company has one that's been running all the critical stuff for years. It's the only thing that always works. Btw, the original design was an awesome capability-secure system called System/38: https://homes.cs.washington.edu/~levy/capabook/index.html https://homes.cs.washington.edu/~levy/capabook/index.html
- cbd1984 11y agoIt was originally part of an even more awesome concept called Future Systems, which was supposed to replace the entire IBM universe with capability-based single-level storage systems. http://people.cs.clemson.edu/~mark/fs.html http://people.cs.clemson.edu/~mark/fs.html http://www.garlic.com/~lynn/submain.html#futuresys http://www.garlic.com/~lynn/submain.html#futuresys It never got off the ground. System/38 and AS/400 are the only visible remnants of it, survivors from an alien world.
- Shivetya 11y agoworking on the iSeries (AS/400) currently and to be honest, I don't know of an easier to maintain system. DB2 is nearly automatic in maintenance and the only time we suffer an outage is paranoia when a multiple level redundant system went out and they wanted to replace the backup units with the failed. The size of these machines range from barely seeming bigger than a PC to 64 way and hundreds of terabytes. IBM was smart in that pSeries and iSeries share hardware, though running a Linux VM/partition/etc is more for sheer fun of it than work.
- nickpsecurity 11y agoI used to joke that slackers should specialize in AS/400 "repair" with revenue coming from support and maintenance contracts. I predicted it would be a really easy job. Just regularly run reports or something to hand management to justify your salary. Take credit for the uptimes. And so on. :) "though running a Linux VM/partition/etc is more for sheer fun of it than work." I thought that was to get benefits of modern stacks running side-by-side with legacy OS/400 apps. You don't use it that way? And while we're at it, did they ever provide an easy, machine-usable interface between those instead of a web app simulating a terminal typing individual characters in like some mainframe places do? That seemed kind of ridiculous.
- pjmlp 11y agoI used to start the backup jobs on a AS/400 during a Summer job for my technical course. The most interesting thing was while researching about them almost a decade later, I came to discover their programming model with a common runtime and a kernel level JIT for software. .NET on Windows/WP, Android and iOS/bitcode might be the closest thing we have on current systems about that programming model.
- chiph 11y agoThe other interesting thing about them is single-level store. With a 64 (65-ish) bit address space, all your RAM and DASD gets mapped into it. So the objects in your program just have memory offsets, and the OS handles the underlying storage. Their reputation for reliability is well deserved. The only time ours went down was for upgrades, and the few times we ran out of UPS power during storms.
- msandford 11y ago> The only time ours went down was for upgrades, and the few times we ran out of UPS power during storms. I'm surprised that you didn't have UPS for stopgap until the generators kick in. If you have a mainframe, it's probably for something mission critical to where a generator (or two or three for redundancy) is a good idea. I'm curious what kind of business you're in where you can justify a mainframe and UPS but not generator, if you can talk about it.
- chiph 11y agoThis was many years ago - the firm wrote and sold accounting software for the AS/400, so while they were production machines, there wasn't really a 100% uptime requirement since there weren't end-users involved. The UPS was there to tide us over short power outages, and ensure a clean shutdown (IPLs after a hard shutdown took a very long time, as the OS would have to verify the whole filesystem). Me and another guy were the only Windows programmers there. We put a friendly UI in front of the AS/400 via network calls (SNA APPC, later TCP/IP sockets) to an endpoint that the RPG guys wrote for us. Later, we wrote an Excel add-in to allow the users to access their financial data from the AS/400, and this became so successful that the entire company is now based around the same technology. Sadly, I don't get a percentage.
- bitwize 11y ago> Anyway, the instructor pointed me to a room with an AS/400, a huge stack of tapes (for the OS), a huge stack of manuals, and basically said "just do it." "You're gonna learn to swim the Stennis way."
- Moru 11y agoMe and a friend went to a programming class ages ago that was teaching AS/400 and programming in RPG/400 on them. That was a funny language. I was working at the state for a bit too, doing smaller programs for the database of inhabitants. Some of the bigger industries had a few AS/400 too but never got a job there programming.
- mindcrime 11y agoYeah, this same college started teaching RPG around the same time all this happened. I took two semesters of RPG programming, but I've never used it for anything in the real world. RPG, at least back then, didn't suit me. It was very much column oriented, with this oddball tool (SEU - Source Entry Utility) that you had to program in. I understand the ILE version(s) of RPG have gone to more of a free-form format, but back then it was a royal pain.
- Moru 11y agoNo, wasn't my favourite programming language but at least it worked :-)
- GnarfGnarf 11y agoRPG is "Repulsive Programming Garbage". It is the worst production programming language ever conceived. It was designed in the 60's based on the IBM 402 tabulator paradigm, to bridge programmers from plugboard wiring, to the 360 stored-program mode. It has long outlived its usefulness. Yet it lives on, entrenched in legions of schlubs who, like Bre'r Rabbit, have never known anything else.
- eps 11y agoWhen was it? Must be at least 20 years ago judging by the Netware reference.
- mindcrime 11y ago1996/1997 or thereabouts.
- snark42 11y agoDid it at least support Ethernet by this point or did you get to learn all about Token Ring as well?
- mindcrime 11y agoDid it at least support Ethernet by this point Luckily, yes. It had an Ethernet port and TCP/IP, so once it was up and running, getting it on the 'net wasn't too bad. The biggest challenge was actually getting the IT dept. to assign us an IP address, etc. Luckily I knew the IT guy pretty well from doing work-study with him earlier, so it wasn't too bad. On the other hand, while you could telnet to the thing, you couldn't really use plain old command line telnet, which usually assumes something like a VT100 or VT200 terminal. AS/400's usually want 5250 terminal emulation, not VT100/220. So I had to find a 5250 terminal emulator to use to connect to the system and actually work with it.
- 13of40 11y agoWas it just the escape codes that weren't compatible, or was the as/400 trying to talk in EBCDIC?
- carey 11y agoA normal telnet connection will be assumed to be something VT100-ish, so it won't try to use EBCDIC. If you send one of a few specific values for the terminal type, though, the AS/400 will use block-oriented EBCDIC comms. This is even documented in RFCs 1205 and 4777. A bigger issue can be with trying to send each of the 24 function keys when a VT102 didn't have any.
- deleted 11y ago[deleted]
- akerro 11y ago> Especially given that this thing can run Linux. Interview with Linus: What's the most amused you've ever been by the collaborative development process (flame war, silly code submission, amazing accomplishment)? I think my favorite part is when somebody does something utterly crazy using Linux. Things that just make no sense at all, but are impressive from a technical angle (and even more impressive from a "they spent many months doing that?" angle). Like when Alan Cox was working on porting Linux to the 8086. Or the guy who built his own computer using an 8-bit microcontroller that he wired up to some RAM and an SD card, then wrote an ARM emulator for it, and booted Linux (really really slowly) on his board. https://www.linux.com/news/special-feature/linux-developers/587846-30-linux-kernel-developers-in-30-weeks-linus-torvalds https://www.linux.com/news/special-feature/linux-developers/...