LowEndBox - Cheap VPS, Hosting and Dedicated Server Deals

Run a $8 Million Mainframe at Home for FREE!

MVS Mainframe
In the mid-70s, my father worked in the American automotive industry in Michigan, and I visited him at work as a small boy.  He took me into the “computer room” (as they used to call datacenters) and sat me down at the terminal of the biggest, baddest system on the planet at the time: IBM System/370.  There were rows of blinking lights, switches, and indicators.  I was instructed to type something on the keyboard or flip a switch and the system’s blinking lights changed and then the real programmers got back to work.

The System/370 was the sequel over its predecessor, the System/360, which was one of the big turning points in computer history.  I’m not sure exactly what model my father’s employer had, but it was likely one of the 303x series.  In 1978, IBM announced that it was releasing a multi-processor version in the 303x line, which would give customers two cores, and I believe this was the first or one of the first multiprocessor system as we would think of them today.  This was 24-bit computing – 31-bit was still a few years ago.

To get one of these dual-core hot rods, on a 48-month purchase agreement, you’d be spending on the order of $154,130 per month for 8MB, or $182,130 for 16MB.  Or you could write a check for $7,160,000 or $8,050,000 and own it outright.  That got you CPU, RAM, two consoles, and power/cooling.  Disk, more terminals (there’s no “LAN network” in the modern sense here), card punch readers, floppy disks, etc. are all extra.

In 2022, most of us would chuckle over 16MB of RAM.  But I’ve spoken to old vets who say that with a single CPU and only 8MB of RAM, they were routinely supporting hundreds (hundreds!) of logged-on users doing active work, while also processing batch, talking to dozens of printers at the same time, and communicating with a galaxy of antique I/O equipment such as SNA terminals, communication multiplexers, etc.  These people were running applications, compiling, submitting jobs, etc. and doing the business of the enterprise.  This is before the “client/server” model.  Everyone logged into the same system.  It’s possible to do such with so little because the way the mainframe works is fundamentally different than Unix or Windows.

Keep in mind that the mainframe’s roots stretch back to a time before operating systems, and indeed you can watch blue-suited (well, in black and white) IBM nerds from the 1960s explain what a “monitor program” (OS) is because it was a new idea.  The mainframe spans from a purely mechanical time (pre-WWII) where computers were mainly sophisticated card sorters that you ran sets of paper through, into the virtual world where there is “always something running” (an OS, or a “monitor” in 60s parlance).  The 1940s and 1950s, computing was not far removed from “setting up electronic circuits” but as the 50s/60s progressed, the mainframe evolved modern computing.

To illustrate how different things have been in the past, originally IBM used non-volatile RAM: you could power off a system, move it, plug it back in, and it would be exactly back where you were.  No boot or anything, just exactly where it was the moment you powered it off (today, dynamic RAM is used).  Many hardware components have been broken out into sub-units.  For example, there are specialized components that let many mainframes speak to each other, or handle the communication complexities of hundreds of terminals, etc.

The mainframe is also very batch-oriented, where even interactive sessions feel like mini-batch sessions.  While there are many on-line applications, much of the work is “take this program and this dataset and run this job, putting the output over here” kind of work.  The entire environment supports this – there are sophisticated job-control subsystems and much of the OS is very record-/dataset-oriented rather than file-oriented.  There are of course some ideas that are common to all systems – for example, the idea of “booting a system” is called an “initial program load (IPL)” in the mainframe world, the concept of a “configuration area” (/etc on Unix, PARMLIB on the mainframe) is there, etc.  But fundamentally the environment is different.

Today, modern mainframes have gigabytes/terabytes of memory, use fast SSD/NVMe SAN storage, speak TCP/IP and host web sites, etc.  IBM has actually offered Linux on the mainframe since 2008.  Another mainframe innovation was virtualization and mainframes have been virtualizing operating systems since the 1970s.  Modern mainframes can run hundreds of Linux instances simultaneously, right alongside however many copies of z/OS (the current operating system) you wish.  Mainframes tend to still be physically big, but they’ve shrunk to refrigerator-sized and they’re not larger than some high-end Unix gear (Sun E15000, HP SuperDome, etc.) or racks of open systems.

BTW, the concept of sharing software also came from the mainframe community.

Mainframes are still expensive, but back in the 1970s, they  up the entire floor of a building with staggering electricity bills, mammoth cooling requirements, and a priesthood of acolytes to tend these mighty systems.

And you, dear LowEndBox reader, can have one of these $8 million piece of computing history for free.

Well, sort of.

OK, you can’t actually get a free IBM 3033 (and couldn’t afford to run it if you could!), but you can emulate them on modern hardware and run much faster than systems of that era.

IBM has placed its operating systems prior to the 31-bit era in the public domain…or rather, it was forced to after the US government noted that it had developed the software under contract for the government and by law, it’s public domain.  In general, though, IBM has been generally gracious about this computing history, continuing to offer manuals and downloads on its web site for systems it has not sold for decades.

The Hercules emulator allows you to run any mainframe operating system.  You can even run z/OS (the current mainframe OS) on it, though not legally.  The latest free (public domain) OS you can run is MVS 3.8j from 1981.

Personally, I tried to get into the mainframe years ago but found it too alien.  For one thing, you can’t login with ssh but rather need a TN3270 emulator.  They’re available for all platforms but it’s a sign that you’re heading into a foreign country.  When you do connect, it’s like using Unix for the first time: what do I type, what are the special keys, how do I “move around”, etc.  There’s no “prompt” in the same scrolling sense, for example, which immediately is a little disorienting.

However, in recent years there have sprung up various YouTube channels that can walk you through getting the mainframe up and running.  There has also been some software packaging which makes things much easier.  It’s very analogous to the work the BSD community did with NET/2, or what Linux distributions do with the kernel.  If you had to download, compile, and build Linux from scratch, not many could do it.  But installing a distro, where things are all setup for you, is pretty simple.  Same thing with modern packaging of MVS 3.8j, as expressed in the TK4- package.

To get the mainframe up and running on Hercules, I recommend following one of these two tutorials:

Moshix will walk you through it step by step and take you from “I’ve never logged into a mainframe in my life” to “I just submitted a COBOL program to calculate prime numbers viewed the batch job output” in an hour.  You’ll be installing Hercules, a TN3270 emulator, and the TK4- “turkey MVS” kit, which is the MVS 3.8j system setup and ready to go.  It’s sort of like if you hired a Linux sysadmin to install Linux, get it setup, take care of all the startup/shutdown permissions, configured users, etc. – that’s what TK4- is.  You can customize anything you want but it’s a solid, professionally setup system to start from.

MVS Mainframe

It’s interesting to compare the “ecosystem” here to other operating systems:

  • Programming: COBOL, assembler, high-level assembler, FORTRAN, PL/I, many others of the era
  • Jobs/Scripting: JCL, REXX
  • Editors: no vim or emacs, but the RFE and RPF environments have sophisticated editors in them

Needless to say, anything you have will run it just fine in terms of power.  Minimum specs are much higher for the emulator itself compared to what it’s emulating.  Hercules is most comfortable with 1GB of RAM, and will use as many or as few cores as you want to throw at it.  They recommend 1.5Ghz or faster processor.

I don’t think LowEndBox is going to see a lot of z/OS or even MVS 3.8j offers anytime soon, but it’s a fun and fascinating step back in time.  And since z/OS people are very short demand this day, if you like it, you can always step up to 2022 with IBM’s “z/OS Practitioner” certification.

TK4-

 

11 Comments

  1. Not_Oles:

    Hi @raindog308!

    Nice post! I enjoyed it so much that I read it twice!

    Here’s a Youtube video about a kid who wanted a mainframe and didn’t want to use an emulator: https://www.youtube.com/watch?v=45X4VP8CGtk

    Check around 8:28 for the excavation required to get the kid’s mainframe into his basement! :)

    Best wishes!

    March 5, 2022 @ 3:19 pm | Reply
  2. Shelly Cashmann:

    3270 and TSO are for posers – interactive computing will never catch on. Is there an RJE subsystem thru which I can run my compile/link/load/run batch job card-decks for my COBOL reports that I can spool to a bisynch HDLC line printer ?

    March 6, 2022 @ 3:27 pm | Reply
    • Hi,
      Are you the shelly cashman who wrote the text books I used back
      in college in th 70’s and 80’s?

      If you want use mvs like an rje system(real computer at console)
      the try Jason( a free gui, that looks and feels like your at the console
      running batch jobs!!!)

      You have to gen MVS or os yourself(custom install), Jay Mosely MVS pages
      have instructions to gen mvs or other ibm os.

      Does anyone know of an RJE IBM simulator for windows?
      Bill

      May 16, 2022 @ 1:42 pm | Reply
      • PS: 2 correction in aeticle.I

        1) IBM and United Shoe in 1956 signed a consent decree sattlement(with doj)
        that said Ibm had to give its software and patents to anyone who
        wanted it, untill 1970. After 1970 they could charge fot those items.

        2) MYTH CORE MEMORY WAS NON VOLITAL: WE ALWAYS HAD TO RELOAD OR IPL
        A SYSTEM WHEN RUNNING DIAGNOSTICS. TURNING POWER OFF SCRAMBLED THE MEMORY.
        I WORKED ON IBM, UNIVAC, DEC, RCA SYSTEMS WITH CORE MEMORY.
        ALWAYS HAD TO RELOAD PROGRAMS AFTER POWER OFF!!!

        May 16, 2022 @ 1:58 pm | Reply
  3. Dan:

    I find it interesting that you equate the mainframe with a specific operating system. That’s somewhat akin to saying you can’t get into AMD processors because they can still run MS-DOS.

    There’s a lot more to the mainframe then TSO and 3270 consoles.

    March 6, 2022 @ 10:26 pm | Reply
    • We do have MVS 3.7 starter, MVS 3.8, VM/370, DOS/VS, OS/360 MFT 21.8F with APL\360, MTS, Linux. No ACP/TPF, TSS, or AIX unfortunately.

      March 7, 2022 @ 12:34 am | Reply
  4. Scott:

    Loved REXX and VM/CMS as a wide eyed college student in the early 90s. Got to load tapes, program on a 3278 terminal. SQL/DS was so cool. Also programed in Model 204 on the VSE/Dos environment. Loved to work with system programmer’s who were gods to me. Xedit was a fun editor to boot!

    March 7, 2022 @ 7:10 am | Reply
    • Rock on, Scott. Fellow child of the 204 era here. Would get a kick if I could fire up an emulator for some user language such as to write an apsy–or some hli or ifam with cics, or even some good ol flod and jcl. Ah, good times, for me from ’83-’97.

      And oh yes, the many great brains and some wonderful people from that era. A time I’ll always cherish.

      March 7, 2022 @ 9:00 pm | Reply
  5. Penggunaan directory komputer penting untuk Sistem Aturan.

    March 7, 2022 @ 7:55 am | Reply
  6. Love the revisiting of my past. Thank you. I remember jcl just fine. Roscoe. I still own an ISPF book.

    Tom M

    March 7, 2022 @ 8:40 am | Reply
  7. Vance:

    You can SSH into z/OS.

    March 7, 2022 @ 11:08 am | Reply

Leave a Reply

Some notes on commenting on LowEndBox:

  • Do not use LowEndBox for support issues. Go to your hosting provider and issue a ticket there. Coming here saying "my VPS is down, what do I do?!" will only have your comments removed.
  • Akismet is used for spam detection. Some comments may be held temporarily for manual approval.
  • Use <pre>...</pre> to quote the output from your terminal/console, or consider using a pastebin service.

Your email address will not be published.