AN/FSQ-32

From Wikipedia, the free encyclopedia
  (Redirected from Q32)
Jump to: navigation, search
AN/FSQ-32
Command, control, and coordination system
CFB Entrance.JPG
The USAF planned an underground "Super Combat Center" with AN/FSQ-32 in the Ottawa sector to be completed by August 1, 1962, for use as a Direction Center,[1] but after the solid-state AN/FSQ-32 was cancelled, the underground bunker completed in 1963 was instead equipped with a vacuum tube AN/FSQ-7.
Planned for the SAGE computer network
Location 23rd & Colorado Blvd, Santa Monica, California[2]
Hardware design IBM Kingston Engineering [3]
Planned Complete hardened capability by 1 April 1964[4] [citation needed]

The AN/FSQ-32 SAGE Solid State Computer (AN/FSQ-7A before December 1958,[5]:27 colloq. "Q-32") was a planned military computer central for deployment to Super Combat Centers in nuclear bunkers and to some above-ground military installations. In 1958, Air Defense Command planned to acquire 13 Q-32 centrals[4] for Air Divisions/Sectors at Ottawa, St Louis, San Antonio, Raleigh, Syracuse, Chicago, Spokane, Minot, Portland, Phoenix, Miami (above-ground), Albuquerque (above-ground), and Shreveport (above-ground). (During 1959 SAGE/FAA "boundary alignments", the total was reduced to 12.**)

Background[edit]

In 1956, ARDC sponsored "development of a transistorized, or solid-state, computer" by IBM and when announced in June 1958,[6] the planned "SAGE Solid State Computer...was estimated to have a computing capability of seven times" the AN/FSQ-7.[5] ADC's November 1958 plan to field—by April 1964—the 13 solid state AN/FSQ-7A[5] was for each to network "a maximum of 20 long-range radar inputs [40 LRI telephone lines[3]] and a maximum dimension of just over 1000 miles in both north-south and east-west directions."[4] "Low rate Teletype data" could be accepted on 32 telephone lines[3] (e.g., from "Alert Network Number 1"). On 17 November 1958, CINCNORAD "decided to request the solid state computer and hardened facilities",[4] and the remaining vacuum-tube AN/FSQ-8 centrals for combat centers were cancelled (one was retrofitted to function as an AN/FSQ-7).

"Each [sic] AN/FSQ-7A computer would be"* used:[7]:21

1. for "a combat center" (as with the vacuum-tube AN/FSQ-8),
2. to accept "radar and weapons connections" for weapons direction as with the AN/FSQ-7--e.g., for backup CIM-10 Bomarc guidance or manned interceptor GCI if above-ground Direction Center(s) could not function,[4] and
3. for "air traffic control functions".[7]:21

"Air Defense and Air Traffic Control Integration" was planned for airways modernization after the USAF, CAA, and AMB agreed on August 22, 1958, to "collocate air route traffic control centers and air defense facilities"[7]:24 (e.g., jointly use some Air Route Surveillance Radars at SAGE radar stations). The May 22, 1959, agreement between the USAF, DoD, and FAA designated emplacement of ATC facilities "in the hardened structure of the nine U. S. SCC's",[7]:24 and SAGE Air Defense Sectors and FAA regions were to have coincident boundaries in a June 19, 1959, air defense plan used to create a new SAGE Implementation Schedule on July 1, 1959.[7]:20

On December 21, 1959, the Office of Defense Research and Engineering informed NORAD a stop order had been placed on AN/FSQ-32 production and in January 1960, the Office of the Secretary of Defense recommended the SCC program be cancelled.[8] The AN/FSQ-32, as part of the SCC Program, was cancelled by March 18, 1960,[8] and the SAGE Air Traffic Integration (SATIN) was similarly cancelled by the DoD.[9] Back-Up Interceptor Control eventually with smaller solid-state computers at above-ground SAGE radar stations was instead implemented for survivability.

Prototype[edit]

The prototype of the AN/FSQ-32 was the largest transistor (solid state) computer ever made and was said[who?] to weigh 250 tons.[10] The Q-32 prototype was installed at System Development Corporation (SDC) headquarters in Santa Monica, California, and SDC developed the prototype software using JOVIAL. The mainframe occupied nearly an entire floor of a large office building (refrigeration units were also in the building).[dubious ] The prototype used batch processing of the military data.

ARPA research[edit]

In the early 1960s, the AN/FSQ-32 prototype was taken over by the Advanced Research Projects Agency and remained in Santa Monica.[specify] SDC's research included ways to permit the prototype to handle multiple batch tasks simultaneously ("time-sharing") and to simultaneously process data multiple geographically-separated computer users.[11]

On April 23, 1963, Dr. J.C.R. Licklider, ARPA Director of Behavioral Sciences Command & Control Research, identified early challenges[specify] in establishing a time-sharing network of computers with the software of the era.[12] An early remote user of the prototype was the Augmentation Research Center at the Stanford Research Institute.[13]

Time-sharing[edit]

By June 1963 the Time-Sharing System (TSS) Model Zero was demonstrated after magnetic drums were added to the time-sharing. Each user was given a priority-based time slice, measured in milliseconds, when the user's program was written from the magnetic drums into much higher speed memory, processed, and then written back to the magnetic drums with any computational changes that had occurred. It was influenced by early experiments at Bolt, Beranek, and Newman, and the CTSS project at MIT.[14] Terminals included several Teletype Model 33 ASRs.

Computer network[edit]

After the SAGE Sector Warning Network for the 1st operational SAGE direction center used the 1st operational computer network[5] (cf. the experimental networks for Bomarc test launches and SAGE compatibility tests), in October 1965 Lincoln Labs' used a TX-2 solid-state computer tied to the Q-32 prototype for the first telecommunication of time packets.[citation needed]

Description[edit]

The prototype was an IBM 4020 Military Computer[10][not in citation given] that included a Central Processing Unit, memory, High-Speed Input/Output, Low-Speed Input/Output, and for both computer operations and maintenance,[15] an Operations Console. The AN/FSQ-32 central would have included additional equipment such as display and console equipment for use by Air Defense Command, Army Air Defense Command, Federal Aviation Administration, and other personnel (e.g., at SCC/DCs, weapons direction consoles for dispatching/guiding manned interceptors, launching/guiding CIM-10 Bomarcs, and launching Nike surface-to-air missiles).

Central Processing Unit[edit]

The Instruction set used 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. CPU controls included sense switches to control various software functions, a run/halt switch, and a switch, amplifier, and speaker assembly, 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[edit]

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 prototype was equipped with 128k words (48 bits plus two parity bits) of memory that 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 as a primitive ROM. The memory had a cycle time of 2.5 microseconds,[16] and the lack of memory management was a limitation in the computer.[12]

Input/Output[edit]

High-Speed Input/Output 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 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 a 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: IBM 1402 Card Reader/Punch, IBM 1403 Line Printer, & 2 IBM 729-V Tape Drives
  • 2 IBM Selectric Typewriters, (I/O Typewriters) one of which was used for operational messages and the other for diagnostic messages and maintenance activities.

References[edit]

*The AN/FSQ-32 planned for the "Canadian" 35th Air Division (in the Ottawa Air Defense Sector) was to have the "DC program only",[5]:27 and the 3 centrals for Albuquerque, Miami, and Shreveport were planned for use only in Direction Centers (rather than Super Combat Centers or SCC/DCs).[5]

**The 1959 plan retained AN/FSQ-32 deployments for the Albuquerque DC, Chicago SCC, Great Falls SCC, Ottawa SCC/DC, and San Antonio SCC/DC but redesignated 7 of the sector names for the deployments: 1958 plan Portland, Spokane, Minot, St Louis, Syracuse, Raleigh SCC/DC, Miami DC 1959 plan San Francisco SCC, Seattle SCC, Denver SCC/DC, Ft Knox (SCC/DC), Boston SCC,[where?] Atlanta SCC/DC, Montgomery DC and in effect, the Shreveport Q-32 (for a sector between the San Antonio and Miami/Montgomery sectors) was eliminated, reducing the planned AN/FSQ-32 deployments to 12.

  1. ^ "1958 NORAD/CONAD Historical Summary: July-December" (PDF). Table 2 Solid State Computer Deployment Schedule: Operational Dates (p. 27). 
  2. ^ Young, David Evan (Oct 4, 2011). "web posting". Retrieved 2013-05-12. "Number of AN/FSQ-32 computers manufactured: 2...1 at SDC; 1 at IBM" 
  3. ^ a b c The AN/FSQ-7A Computer (Report). IBM. January 20, 1959. p. 14. http://bitsavers.informatik.uni-stuttgart.de/pdf/ibm/4020/The_AN_FSQ7A_Computer_Jan59.pdf. Retrieved 2013-05-12.
  4. ^ a b c d e ADC Operational Employment Plan (military plan -- cf. the "The Super Combat Center Plan" with the same dates). Air Defense Command. 5 November 1958: NORAD approval 20 December 1958. (cited by 1958 Jul-Dec NORAD/CONAD history: "A complete hardened back-up capability by 1 April 1964 -- the scheduled operational end point -- about nine months later than Schedule 7 (Improved). The AN/FSQ-7A was to be installed at 13 locations. Ten of these were to be what ADC termed Super Combat Centers (SCC). ... criteria for the AN/FSQ-7A...included a maximum of 20 long-range radar inputs and a maximum dimension of just over 1000 miles in both north-south and east-west directions. ... On 17 November [1958] CINCNORAD decided to request the solid state computer and hardened facilities. "
  5. ^ a b c d e f Preface by Buss, L. H.—Director.  (Report).
  6. ^ Schaffel, Kenneth (1991). "Emerging Shield: The Air Force and the Evolution of Continental Air Defense 1945-1960" (45MB pdf). General Histories (Office of Air Force History). ISBN 0-912799-60-9. http://www.airforcehistory.hq.af.mil/Publications/Annotations/schaffelemerging.htm. Retrieved 2011-09-26. "the improved computer would not only do more, it would occupy less space. ... A presidential committee decided that, while it might be possible to harden the centers sufficiently, their communications systems would still be highly susceptible to blast damage, especially to electromagnetic pulse...31" (Schaffel pp. 265/315 cites:
    • McMullen, Richard F. (1965). Command and Control Planning, 1958-1965 (Report). ADC Hist Study 35. pp. 1-12.
    • cf. Sturm, Thomas A. (January 1965). Command and Control for North American Defense, 1959-1963 (Report). USAF Hist Div Liaison Ofc.]
  7. ^ a b c d e Preface by Buss, L. H.—Director.  (Report).
  8. ^ a b NORAD CONAD Historical Summary: July–December 1959 "On 18 March 1960, the JCS advised NORAD that they had approved cancellation of the SCC program for the U.S."
  9. ^ Missile Master Plan (described by Schaffel p. 260: "…the Defense Department to issue, on June 19, 1959, the Master Air Defense Plan. Key features of the plan included a reduction in BOMARC squadrons, cancellation of plans to upgrade the interceptor force, and a new austere SAGE program. In addition, funds were deleted for gap-filler and frequency-agility radars.21" and publicized as the "Missile Master" Plan [1][2]
  10. ^ a b http://ed-thelen.org/comp-hist/vs-ibm-sage.html
  11. ^ Oral History interview with Jules I. Schwartz, Charles Babbage Institute, University of Minnesota. Schwartz worked for the Rand Corporation on time-sharing for the prototype.
  12. ^ a b J. C. R. Licklider (April 23, 1963). "Memorandum For: Members and Affiliates of the Intergalactic Computer Network; Topics for Discussion at the Forthcoming Meeting". Washington, D.C.: Advanced Research Projects Agency. Archived from the original on 4 June 2011. Retrieved April 21, 2011. 
  13. ^ Douglas C. Englebart (June 1986). "The Augmented Knowledge Workshop". Proceedings of the ACM Conference on The history of personal workstations (Palo Alto, California: ACM). doi:10.1145/12178.12184. ISBN 0-89791-176-8. Retrieved April 20, 2011. 
  14. ^ Schwartz, Jules I.; Coffman, Edward G.; Weissman, Clark (1964). "A general-purpose time-sharing system". Proceedings of the AFIPS April 21–23, 1964, spring joint computer conference. doi:10.1145/1464122.1464163. 
  15. ^ Baker, C. L.; Haverty, J. P. (February 6, 1959). U. S. Air Force Project RAND: Some Thoughts on the IBM Military Computer as a Data Processor (Report). http://bitsavers.informatik.uni-stuttgart.de/pdf/ibm/4020/B-100_Some_Thoughts_on_the_IBM_Military_Computer_as_a_Data_Processor_Feb59.pdf. Retrieved 2013-05-12. "The IBM Military Products Computer is described in the Kingston Military Products Division Document SAC-11, dated 17 November 1958, entitled, "Program Instructions Specifications for the SAC Data Processing System. A somewhat revised description has appeared as Lincoln Laboratory "Advanced Sage Computer Memo #23," dated 18 November 1958. ... utilizing 10 megapulse circuitry...permitting a maximum instruction rate of approximately 400,000 per second.*""
  16. ^ The IBM 4020 Military Computer. IBM General Systems Division. October 1959. 
External images
central processor (p. 2)