Computer programming in the punched card era
From the invention of computer programming languages up to the mid-1980s, many if not most computer programmers created, edited and stored their programs line by line on punched cards. The practice was nearly universal with IBM computers in the era. A punched card is a flexible write-once medium that encodes data, most commonly 80 characters. Groups or "decks" of cards form programs and collections of data. Users could create cards using a desk-sized keypunch with a typewriter-like keyboard. A typing error generally necessitated repunching an entire card. In some companies, programmers wrote information on special forms called coding sheets, taking care to distinguish the digit zero from the letter O, the digit one from the letter I, eight from B, two from Z, and so on. These forms were then converted to cards by keypunch operators, and in some cases, checked by verifiers. The editing of programs was facilitated by reorganizing the cards, and removing or replacing the lines that had changed; programs were backed up by duplicating the deck, or writing it to magnetic tape.
A typical corporate or university computer installation would have a suite of rooms, with a large, access-restricted, air conditioned room for the computer (similar to a modern server room) and a smaller adjacent room for submitting jobs. Nearby would be a room full of keypunch machines for programmer use. An IBM 407 Accounting Machine might be set up to allow newly created or edited programs to be listed (printed out on fan-fold paper) for proof reading. An IBM 519 might be provided to reproduce program decks for backup or to punch sequential numbers in columns 73-80. In such mainframe installations, known as closed shops, programmers submitted the program decks, often followed by data cards to be read by the program, to a person working behind a counter in the computer room. Many computer installations used cards with the opposite corner cut (sometimes no corner cut) as "job separators", so that an operator could stack several job decks in the card reader at the same time and be able to quickly separate the decks manually when he removed them from the stacker. These cards (e.g., a JCL "JOB" card to start a new job) were often prepunched in large quantities in advance. This was especially useful when the main computer did not read the cards directly, but instead read their images from magnetic tape that was prepared offline by smaller computers such as the IBM 1401. After running a program, the computer operator would return the card deck and any hardcopy printed or punched output, typically to one of a set of alphabetically labelled cubby holes, based on the programmer's last initial. This was all batch-mode processing, as opposed to interactive processing.
Overnight and even 24-hour turnaround times were not uncommon. During peak times, it was common to stand in line waiting to submit a deck. However, on a lightly used system, it was possible to make alterations and rerun a program in less than an hour. Dedicated programmers might stay up well past midnight to get a few quick turnarounds. Use of this expensive equipment was often charged to a user's account. A mainframe computer could cost millions of dollars and usage was measured in seconds per job.
Smaller computers like the IBM 650, 1620 and 1130, were less expensive and often run as an open shop, where programmers had use of the computer for a block of time. A keypunch was usually located nearby for quick corrections.
Many early programming languages, including Fortran, Cobol and the various IBM assembler languages, used only the first 72 columns of a card — a tradition that traces back to the IBM 711 card reader used on the IBM 704/709/7090/7094 series (especially the IBM 704, the first mass-produced computer with floating point arithmetic hardware), which could only read 72 of the 80 columns in one pass. Columns 73-80 were ignored by the compilers and could be used for identification or a sequence number so that if the card deck was dropped it could be restored to its proper order using a card sorter. (An alternative, imperfect but commonly employed technique to maintain proper card order was to draw one or more diagonal stripes across the top edge of all the cards in a deck.)
- Fisk, Dale (Setting 1973; Written 2005). "Programming With Punched Cards:
A Programmer's Memories of Learning the Craft in 1973". Retrieved 2008-11-11. Check date values in:
Article about the programming culture that developed around use of the punched card, following Fisk's experience of "learning the craft" from people around him. Also, how the concept of programming changed significantly as the computer began to multi-task and store programs internally on disk ... observing how the programmer's sense of possession/ownership of a program was somewhat relinquished after he no longer physically "held it in his hands" but trusted the computer to keep it safe for him.
- Columbia University Computing History: The Columbia University Self Service Input/Output Area
- E. I. Organick, A Fortran IV Primer, Addison-Wesley, 1966