Previous Entry Share Flag Next Entry

My first computer - the IBM 1620

IBM 1620I was a prisoner graduate Physics student at Columbia in the fall of 1961 busy avoiding the draft and trying to find a new direction that would let me leave NYC, not get drafted, and find something I'd like to do. I decided to try computer programming and took an introductory course (foolishly not having tried computers while I was at MIT dabbling in Physics and Math). The machine at the Watson Lab was the IBM 1620 Model 1.
The machine had a paper tape reader and punch, a console typewriter, did arithmetic by table lookup, had 20K characters of memory, an assembler and a Fortran compiler. The nickname for the machine was CADET (can't add, doesn't even try).

To program we wrote programs with pencil and paper, went to the key punch machine, made listings of our card decks on the 407 Accounting Machine, corrected errors, made a paper tape on the card-to-tape machine and then brought the tape to the computer. You loaded the Compiler or Assembler from paper tape, then put in your tape and started assembling or compiling. The first thing the compiler or assembler did was to punch a paper tape with a program loader on it. The it started processing your tape. For the Fortran compiler when it detected an error it printed a message on the typewriter console - something like error 57 on line 12 and stopped!

You corrected your mistake, punched a new card, converted to paper tape and started again. There was also a Fortran pre-compiler that could process a whole program and print out multiple errors but it and the compiler weren't completely compatible so a clean precompile didn't mean a clean compile.

Punching the loader for the Fortran compiler took 7 minutes! This is where I learned that I was going to become a hacker/system programmer. I found the listings of the compiler, found out where it punched out the loader, and made a patched version of the compiler to skip this step. Having saved a copy of the loader on a piece of tape. I and other fellow students could now save 7 minutes of time for each use of the compiler.

This was my last term at Columbia. I returned to MIT as a special student for the spring term, got a part-time job in the computer center, and applied for and got a job at Honeywell writing a Fortran compiler - such jobs got me draft deferment because I was working for a "critical industry".

  • 1
It weren't no fancy computer, but this reminded me of the days in the shipping industry when we had such high-tech gadgets as Telex/TWX machines that also used paper tape. You'd use the keyboard to punch out your message to tape and then dial the local access by hand (using a rotary dial, of course) and then run your tape through to send your message.

It could be a pain to have to go through all these steps to just send a message to a single location, but if you had to sent it to multiple receivers, you could punch seperate header tapes and then use the common tape for the bulk of the message.

Ah and I had the joy of learning RPG and Cobol. Fortunatly they had just gotten rid of the punch cards, I have a bunch that make great bookmarks and conversation starters.

That reminds me that I have a card deck of an English to Piglatin generator that I wrote in Fortran.

Summer of 1964 I had a job at Swift & Company's OR department in Chicago. We had two 12K 1401s and a 40K 1620. I was mostly a 1401 jock and only used the 1620 a few times, to run a linear programming job that calculated the ingredient mix for Swift hot dogs. I think the LP program was written in FORTRAN. Our machine had hardware add, but even so, an LP with tens of rows and columns, starting from a feasible solution, took 30 minutes.

The Computer History Museum has a project to restore a 1620 to operation. See http://www.computerhistory.org/projects/ibm_1620/Journal/ for information. Under the "sim" tab you will find a Java applet that simulates the 1620 with a beautiful control panel simulator.

  • 1