IBM 305 RAMAC

The IBM 305 RAMAC was the first commercial computer that used a moving-head hard disk drive (magnetic disk storage) for secondary storage.[1] The system was publicly announced on September 14, 1956,[2][3] with test units already installed at the U.S. Navy and at private corporations.[2] RAMAC stood for "Random Access Method of Accounting and Control",[4] as its design was motivated by the need for real-time accounting in business.[5]

IBM 305 RAMAC
IBM 305 at U.S. Army Red River Arsenal. Foreground: two 350 disk drives. Background: 380 console and 305 processing unit
DeveloperIBM
ManufacturerIBM
Release dateSeptember 14, 1956 (1956-09-14)
Introductory priceUS$3,200 (equivalent to $29,130 in 2019) per month
Discontinued1961
Units soldMore than 1,000
SuccessorIBM 1401
Websitewww.ibm.com/ibm/history/exhibits/storage/storage_PH0305.html

History

The first RAMAC to be used in the U.S. auto industry was installed at Chrysler's MOPAR Division in 1957. It replaced a huge tub file which was part of MOPAR's parts inventory control and order processing system.

During the 1960 Olympic Winter Games in Squaw Valley (USA), IBM provided the first electronic data processing systems for the Games. The system featured an IBM RAMAC 305 computer, punched card data collection, and a central printing facility.

More than 1,000 systems were built. Production ended in 1961; the RAMAC computer became obsolete in 1962 when the IBM 1405 Disk Storage Unit for the IBM 1401 was introduced, and the 305 was withdrawn in 1969.

Overview

The first hard disk unit was shipped September 13, 1956.[6] The additional components of the computer were a card punch, a central processing unit, a power supply unit, an operator's console/card reader unit, and a printer. There was also a manual inquiry station that allowed direct access to stored records. IBM touted the system as being able to store the equivalent of 64,000 punched cards.[5]

The 305 was one of the last vacuum tube computers that IBM built. It weighed over a ton.[7]

The IBM 350 disk system stored 5 million alphanumeric characters recorded as six data bits, one parity bit and one space bit for eight bits recorded per character.[8] It had fifty 24-inch-diameter (610 mm) disks. Two independent access arms moved up and down to select a disk, and in and out to select a recording track, all under servo control. Average time to locate a single record was 600 milliseconds. Several improved models were added in the 1950s. The IBM RAMAC 305 system with 350 disk storage leased for US$3,200 (equivalent to $29,130 in 2019) per month.

One RAMAC storage disk showing head crash damage

The original 305 RAMAC computer system could be housed in a room of about 9 m (30 ft) by 15 m (50 ft); the 350 disk storage unit measured around 1.5 square metres (16 sq ft). Currie Munce, research vice president for Hitachi Global Storage Technologies (which has acquired IBM's hard disk drive business), stated in a Wall Street Journal interview[9] that the RAMAC unit weighed over a ton, had to be moved around with forklifts, and was delivered via large cargo airplanes. According to Munce, the storage capacity of the drive could have been increased beyond five megabytes, but IBM's marketing department at that time was against a larger capacity drive, because they did not know how to sell a product with more storage.

RAMAC mechanism at Computer History Museum

Programming the 305 involved not only writing machine language instructions to be stored on the drum memory, but also almost every unit in the system (including the computer itself) could be programmed by inserting wire jumpers into a plugboard control panel.

Architecture

System architecture was documented in the 305 RAMAC Manual of Operation.[4] The 305 was a character-oriented variable "word" length decimal (BCD) computer with a drum memory rotating at 6000 RPM that held 3200 alphanumeric characters. A core memory buffer of 100 characters was used for temporary storage during data transfers.

Each character was six bits – plus one odd parity bit ("R") – composed of two zone bits ("X" and "O") and remaining four binary bits for the value of the digit in the following format:

X O 8 4 2 1 R

Instructions could only be stored on 20 tracks of the drum memory and were fixed length (10 characters), in the following format:

T1 A1 B1 T2 A2 B2 M N P Q
Field positions Function
T1 A1 B1 Source operand address – Track, low order AB character
T2 A2 B2 Destination operand address – Track, low order AB character
M N Length of operands (each operand must be entirely on its specified track)
P Program exit code; used to select test conditions, perform jumps, and initiate input/output. The 305's control panel programming determines the action(s) performed.
Q Control code; modifies the operation (similar to an op code), the default operation being a copy from source to destination. Other operations were: "1" Compare, "2" Field compare, "3" Compare & Field compare, "5" Accumulator reset, "6" Blank transfer test, "7" Compress & Expand, "8" Expand, "9" Compress

Fixed-point data "words" could be any size from one decimal digit up to 100 decimal digits, with the X bit of the least significant digit storing the sign (signed magnitude).

Data records could be any size from one character up to 100 characters.

Drum memory

The drum memory was organized into 32 tracks of 100 characters each.

The color code of this table is:

  • Yellow – Storage
  • Blue – Arithmetic
  • Green – Input/output
  • Red – Special function
Track specifier Source function Destination function
W X Y Z General storage
0 1 2 3 4 5 6 7 8 9
& A B C D E F G H I		 Instruction storage, general storage
L Read accumulator Add to accumulator
M Read & clear accumulator Subtract from accumulator
V Multiplicand (1 to 9 characters) or divisor (1 to 9 characters)
N N/A Multiply (1 to 11 characters)
Stores 2 to 20 character product
in accumulators 0 & 1
P N/A Divide (option)
K 380 Punched card input N/A
S T N/A 323 Punched card output,
370 Printer Output,
407 Printer output
Q 380 Inquiry input/output
J N/A 350 File Address
R 350 File data input/output
- Core buffer Character selector
$ 382 Paper tape input/output (option)

L and M select the same track, containing ten 10-character "Accumulators". As a destination L specifies addition, M specifies subtraction. (Numbers in these accumulators were stored in ten's complement form, with the X bit of the most significant digit storing the sign. The sign of each accumulator was also held in a relay. However the 305 automatically converted between its standard signed magnitude format and this format without the need for special programming.)

J, R, and - do not select tracks on the drum, they specify other sources and destinations.

Jumps

The 305's instruction set does not include any jumps, instead these are programmed on the control panel:

  • Unconditional jump – the program exit code (P field) specifies a Program exit hub on the control panel, which has a wire plugged into it and, via distributors, to Program entry hubs specifying the first, second and third address digit of the instruction to jump to.
  • Conditional jump – the program exit code (P field) specifies a Program exit hub on the control panel, which has a wire plugged into it and the appropriate Condition selector common hub to be tested, the corresponding two Condition selector output hubs have wires plugged into them and the Program entry hubs specifying the instructions to jump to or the Program advance hub to continue in sequence. Complicated conditions involving many Condition selectors could be wired to execute in a single instruction (e.g., Testing the sign and zero states of multiple accumulators), with one of several Program entry hubs activated.
  • Multi-way jump – the destination track (T2 field) is set to - and the appropriate Character selector hubs on the control panel have wires plugged into them and the Program entry hubs specifying the instructions to jump to or the Program advance hub to continue in sequence.

Timing

All timing signals for the 305 were derived from a factory recorded clock track on the drum. The clock track contained 816 pulses 12 μs apart with a 208 μs gap for sync.

Reading or writing a character took 96 μs.

The 305's typical instruction took three revolutions of the drum (30 ms): one (I phase) to fetch the instruction, one (R phase) to read the source operand and copy it to the core buffer, and one (W phase) to write the destination operand from the core buffer. If the P field (Program exit code) was not blank, then two (D phase and P phase) additional revolutions of the drum (20 ms) were added to the execution time to allow relays to be picked. The Improved Processing Speed option could be installed that allowed the three instruction phases (IRW) to immediately follow each other instead of waiting for the next revolution to start; with this option and well optimized code and operand placement a typical instruction could execute in as little as one revolution of the drum (10 ms).

Certain instructions though took far longer than the typical 30 ms to 50 ms. For example, multiply took six to nineteen revolutions of the drum (60 ms to 190 ms) and divide (an option) took ten to thirty seven revolutions of the drum (100 ms to 370 ms). Input/Output instructions could interlock the processor for as many revolutions of the drum as needed by the hardware.

Hardware implementation

The logic circuitry of the 305 was built of one- and two-tube pluggable units and relays.

A basic system was composed of the following units:

  • IBM 305 – Processing unit, the magnetic process drum, magnetic core register and electronic logical and arithmetic circuits
  • IBM 350 – Disk storage unit
  • IBM 370 – Printer
  • IBM 323 – Card punch
  • IBM 380 – Console, the card reader and IBM Electric typewriter model B1
  • IBM 340 – Power supply
gollark: The actual IPoAC standard requires duct-taping paper to the pigeon, I think, but if you use the nonstandard method of having them, say, carry micro-SD cards, you get better bandwidth.
gollark: IP over Avian Carriers!
gollark: `I can'tonly option.`
gollark: DDR3 what? ECC or not?
gollark: If you just basically want a service dependency tree manager thing with declarative syntax, that probably *could* be made separate...

See also

References
  1. Preimesberger, Chris (2006-09-08). "IBM Builds on 50 Years of Spinning Disk Storage". eWeek.com. Retrieved 2012-10-16.
  2. 650 RAMAC announcement The 305 RAMAC and the 650 RAMAC were internally announced on September 4, 1956.
  3. I. B. M. TO PUT OUT NEW 'THINK' UNITS, New York Times, September 14, 1956
  4. 305 RAMAC Manual of Operation, IBM, April 1957.
  5. IBM RAMAC promotional film
  6. Steven Levy, "The Hard Disk That Changed the World" Newsweek, August 7, 2006
  7. Weik, Martin H. (March 1961). "IBM 305 RAMAC". ed-thelen.org. A Third Survey of Domestic Electronic Digital Computing Systems. See SUNOCO Philadelphia.
  8. "RAMAC 305 Customer Engineering Manual of Instruction" (PDF). IBM Corp., 1959. pp. 7–8 and 85.
  9. Lee Gomes, "Talking Tech" The Wall Street Journal, August 22, 2006
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.