Jump to content

AN/FSQ-32

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by SmackBot (talk | contribs) at 04:34, 2 February 2009 (Date maintenance tags and general fixes). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.


Description

The AN/FSQ-32 was a computer made by IBM (International Business Machines) in 1960 and 1961 for the United States Air Force Strategic Air Command (SAC). IBM called it the "4020." Only one Q-32 unit was ever built.[1]

Location

The Q-32 was installed at System Development Corporation (SDC) headquarters, Santa Monica, California and was used as a development machine for the compiler and operational software for the AN/FSQ-31V, which was used as the Data Processing Element of the SAC Automated Command and Control System.

The near-death experience of the Q-32

The software for the Q-32 was developed by System Development Corporation (SDC) of Santa Monica, California. The original contract called for the Q-32 to be programmed as a solid-state replacement for the vacuum-tube Q-7 computers in the USAF's Semi-Automatic Ground Environment (SAGE) system. However, the SAGE system was abolished by the Air Force in the early 1960s,[dubiousdiscuss] before the Q32 programming for defense purposes was completed. Moving the huge monolithic Q-32 was deemed economically infeasible, and the giant computer was declared to be a surplus item and was nearly junked.

New life for the Q-32

At that point in the history of computers, available technology permitted even the largest of computers to handle just one job at a time. It was described as "One Job In – One Job Out." The entire mainframe, occupying perhaps an entire floor of a large office building and requiring massive refrigeration units to keep its electronics cooled, was consumed with each single job (batch processing), even very small jobs. That inefficiency resulted in the Q-32 and all other large mainframes having huge amounts of wasted idle time.

Q-32 becomes research machine

In about 1963, some Air Force scientists, including mathematician Dr. Joe Ward at the USAF Personnel Research Laboratory AFPRL (later renamed AF Human Resource Laboratory AFHRL), proposed that the Q-32 be taken over by the Department of Defense's Advanced Research Projects Agency (ARPA) for further research purposes. The proposal became reality, and the Q-32 remained in Santa Monica for several years to come. System Development Corporation was retained by ARPA to spearhead a large research project whose objectives included ways to permit the Q-32 to handle multiple batch tasks simultaneously. Another research objective was to design and implement ways to allow simultaneous online processing access to the Q-32 from multiple geographically-separated computer users. The methodology was dubbed "time-sharing." [2]

Architecture

The system was divided into functional sections:

  1. Central Processing Unit
  2. Memory
  3. High-Speed Input/Output
  4. Low-Speed Input/Output
  5. Operations Console

Central Processing Unit

Memory was addressed by words, which were 48 bits long. Each word was divided into eight 6-bit bytes. A 6-bit byte, as opposed to the 8-bit byte in common use today, was common in IBM and other scientific computers of the time. The address space provided a maximum of 256K words.

The ISA was rather complicated for its time. The instructions were a fixed length of one word providing 24 bits for the operation and 24 bits for the address. The address consisted of 18 bits (3 bytes) for the memory address, with other bits used for the specification of index registers and indirect addressing.

The operation field provided the operation code and a variety of modifiers. Some modifiers allowed instructions to operate only on specific bytes of a word or on specific bits of a byte without separate masking operations. Other modifiers allowed the single 48-bit ALU to operate on a pair of 24-bit operands to facilitate vector operations.

Other parts of the CPU were some sense switches, which could be used to control various software functions, the run/halt switch, and a switch, amplifier, and speaker assembly, which could be used to provide audio feedback or even play music, by connecting one of four bits in the main accumulator which could then be toggled under software control at an appropriate rate to produce whatever tones one wanted.

Memory

The Q-32 was equipped with 128k words. The memory bank was oil and water cooled. Also considered as part of the memory subsystem in that they were addressed via fixed reserved memory addresses, were 4 48 position switch banks, in which a short program could be inserted, and a plug panel, similar to the one used in IBM Unit-Record equipment, that had the capacity of 32 words, so longer bootstrap or diagnostic programs could be installed in plug panels which could then be inserted into the receptacle and used. This served as a primitive ROM.

High-Speed Input/Output

The High-Speed I/O section provided interfaces to the Drum Memory system, which consisted of a control system, and two vertical drum memory devices. Each drum read and wrote 50 bits at a time in parallel so transferring data could be done quickly. The drums were organized as 17 fields with 8192 words per field for a total capacity of 139264 words. The motors that rotated the drums required 208 VAC at 45 Hz so a motor generator unit was required to change the frequency from 60 Hz. This added to the noise level in the computer room. The other connection to/from the HSIO was to the SACCS EDTCC, which then interfaced to the rest of the SACCS.

Low-Speed Input/Output

The Low-Speed I/O section interfaced to several different devices:

  • Communications Multiplexor
  • Tape Controllers 1 and 2, connected to 16 IBM 729-V Tape Drives
  • Disk File Controller, which was a modified Tape Controller, connected to
    • Bryant Disk File, which had 25 disks that were 39" in diameter, 125 read/write heads that were hydraulically actuated, and had a total capacity of 26 megabytes
  • IBM 1401, which controlled data transfers from unit-record equipment:
  • 2 IBM Selectric Typewriters, (I/O Typewriters) one of which was used for operational messages and the other for diagnostic messages and maintenance activities.

The computers originally were part of the USAF Air Defense Command's command and control system. SDC developed the system software using JOVIAL (Jules Own Version of the International Algebraic Language), one of the first high-level complied programming languages.

References

  1. ^ Wohlman, John. "Computer-Generated Map Data: An Aid to Command and Control." Air University Review. http://www.airpower.maxwell.af.mil/airchronicles/aureview/1968/jan-feb/wohlman.html. Accessed: 6/20/2006.
  2. ^ Oral history interview with Jules I. Schwartz [1]