CDC 3000 series

The CDC 3000 series ("thirty-six hundred" of "thirty-one hundred") computers from Control Data Corporation were mid-1960s follow-ons to the CDC 1604 and CDC 924 systems.[1]

CDC 3000 series
CDC 3000 family overview
Design
ManufacturerControl Data Corporation
DesignerSeymour Cray
Casing
DimensionsHeight : 191 cm (75 in)
Length (double) : 214 cm (84 in)
Length (single) : 114 cm (45 in)
Width : 68 cm (27 in)
System
SuccessorCDC 6000 series

Over time, a range of machines were produced - divided into[2]

  • the 48-bit upper 3000 series and
  • the 24-bit lower 3000 series.[3]

Early in the 1970s CDC phased out production of the 3000 series, which had been the cash cows of Control Data during the 1960s; sales of these machines funded the company while the 6000 series was designed.[4]

CDC 3000 series family, in basic configuration
3 views of a CDC 3000 series model 3400 with sizing
CDC 3800 console at the Udvar-Hazy Center of the Smithsonian National Air and Space Museum

Specifications
ModelWord sizeRelease DatePriceFrequencyMemory MaxMIPSPicture
CDC 3600 48-bit 06-1963 $1,200,000[5] 714 kHz (1.4μs cycle)[6] 1.536 megabyte (262144 x 48 bits)[5] 0.700 MIPS
CDC 3400 48-bit 11-1964 $680,000[6] 667 kHz (1.5μs cycle)[6] 192 kilobytes (32767 x 48 bits) 0.700 MIPS
CDC 3300 24-bit 12-1965 $220,000[6] 800 kHz (1.25μs cycle)[6] 768 kilobytes (262144 x 24 bits) 0.800 MIPS
CDC 3200 24-bit 05-1964[6] $200,000[6] 800 kHz (1.25μs cycle)[6] 96 kilobytes (32767 x 24 bits) 0.800 MIPS
CDC 3100 24-bit 02-1965[6] $120,000[6] 571 kHz (1.75μs cycle)[6] 96 kilobytes (32767 x 24 bits) 0.500 MIPS

Upper 3000 series

The upper 3000 series used a 48-bit word size. The first 3000 machine[4] to be produced was the CDC 3600; first delivered in June 1963. First deliveries of the CDC 3400 and CDC 3800 were in December 1965. These machines were designed for scientific computing applications; they were the upgrade path for users of the CDC 1604 machines. However these machines were overshadowed by the upcoming 60-bit CDC 6000 series machines when the CDC 6600 was introduced in December 1964 and delivered in 1965.[7] Some high-end computer labs purchased these machines as stopgaps, while waiting for delivery of their 6600 machine.

Lower 3000 series

The lower 3000 series used a 24-bit word size. They were based on the earlier CDC 924 - a 24-bit version of the (48-bit) CDC 1604. The first lower 3000 to be released was the CDC 3200 (May 1964), followed by the smaller CDC 3100 [1] (February 1965), and the CDC 3300 (December 1965). The final machine in the series, the CDC 3500, was released in March 1967 and used integrated circuits instead of discrete components. The 3300 and 3500 had optional relocation capabilities, floating point arithmetic, and BDP (Business + Data Processing) instructions. These machines were targeted towards business and commercial computing.

The 3150

Control Data Corporation's CDC 3150 was described as a "batch computer,"[8] and it included a FORTRAN[9] and a COBOL[10] compiler. Its console looked like this.

Instruction sets

The instruction set of the upper 3000 series was composed mostly of 24-bit instructions (packed two per word), but also contained some 48-bit instructions. The lower 3000 was based on a 24-bit subset of those available on the upper 3000 systems. It was therefore possible to write programs which would run on all 3000 systems. And as these systems were based on the prior 1604 and 924 instruction sets, some backward compatibility also existed. However the systems did diverge from each other in areas such as relocation and the BDP instructions.

Memory

All 3000 series computers used magnetic-core memory. The CDC 3500 machine used the same core memory modules as used in the CDC 6000 / Cyber 70 series computers.

CDC 3302 Core Memory

Architecture

The lower 3000 CPU was a 24-bit architecture:[11] instructions were 24 bits in length, as were the two operand registers A and Q. There were four index registers of 15 bits, B0 through B3, though B0 is always zero (zero when read; writes do not affect the value). There was no status (flags or condition code) register. Up to 32,768 words of core memory, 24 bits per word, could be directly addressed, and multiple banks could be switched in. Two or three memory bank configurations were the most common.

Each instruction contained six bits of opcode, one bit specifying whether indirect addressing used, two bits of index register address and fifteen bits of address.

Arithmetic was ones' complement, so there were two forms of zero: positive zero and negative zero. The A and Q register could function as a combined 48-bit register for certain arithmetic instructions. The E register had 48 bits.

The 3600 CPU could execute around one million instructions per second (1 MIPS), giving it supercomputer status in 1965.[4]

Much of the basic architecture design of the 3000 series was done by Seymour Cray, then passed on to others to complete as he moved on to designing the CDC 6000 series. Several of the innovative features that made the 6600 'the first supercomputer' can be seen in prototype in the 3000 series.

Software

The operating systems for the upper 3000 were called SCOPE (Supervisory Control Of Program Execution). Tape SCOPE was a serial batch OS with no buffering for card reading or print spooling. Drum SCOPE upgraded performance and featured print spooling. CDC developed a OS for the 3800 called SUMMIT (Simultaneous Usage of Multiprogramming, Multiprocessing with Interactive Timesharing) to take advantage of hardware's advanced features. Because CDC focused all its resourced in advancing the 6600 system, SUMMIT was never released.

The earliest operating system for the lower 3000 series was called RTS OS. However it was quickly replaced with MSOS (Mass Storage OS). The premier operating system for the CDC 3300 and CDC 3500 was called MASTER (Multi Access, Shared Time Executive Routine). MASTER was a multi-tasking, disk-based OS but still batch job oriented. Card jobs were cached to disk and printer output spooled. MASTER optimized memory usage with page-mapping hardware.

An operating system called REAL-TIME SCOPE existed for both lower- and upper-3000 systems. A disk-based version of SCOPE was eventually made available for the upper-3000 systems.[12]

FORTRAN, COBOL, and ALGOL[2] were available. The assembly language was called COMPASS. These were available from CDC.

An APL system for the upper 3000 series computers was developed at the University of Massachusetts Amherst. This system was made available to other users of the upper 3000 series.

Character set

The operating systems for the CDC 3xxx typically used six-bit characters, so the 64 character set did not contain lowercase letters. The character set contained (in display code order):

: A-Z 0-9 + - * / ( ) $ = (space) , . # [ ] % " _ ! & ' ? < > @ \ ^ ;

This six-bit extension of the four-bit BCD encoding was referred to as BCDIC (BCD interchange code.) IBM later extended this code further to create the eight-bit "extended BCDIC", or EBCDIC code.

Depending on the device, some characters are rendered differently, especially the lineprinter and some terminals:

character sometimes
displays as
# ≡
" ≠
_ → or {
! ∨
& ∧
' ↑
? ↓ or }
@ ≤
\ ≥
^ ¬

Note the absence of control characters, especially carriage return and line feed. These were encoded by the record structure.

Partial list of users

United States

Oregon State University offered a CDC 3300 for use from the mid-to-late 1960s up until about 1980.[4] It used a home grown operating system known as OS3 (for Oregon State Open Shop Operating System).[13]

The U.S. Internal Revenue Service used CDC 3000 series computers for many years.[4]

Northeastern University in Boston used a CDC 3300 in the early 1970s.

International Timesharing Corporation (ITS) of Chaska, Minnesota sold timesharing services using CDC 3300s. (ITS later acquired another timesharing company that used CDC 3600s, before it, in turn, was acquired by United Computing Systems of Kansas City, Missouri.)

California State University at Northridge had a dual 3170 that provided timesharing service to the California State University and College system. Many of the other campuses also had CDC 3150 machines for local batch operation.[14][15] In 1970 CDC 3150s were installed at most campuses of the California State College system. San Jose State and LA State got CDC 3300s and served as regional data centers with (very flaky) data links to the other campuses. California State Polytechnic College (San Luis Obispo) and San Diego State University had IBM System/360s. The rest got 3150s. Typical configuration was 24K words of 24-bit core memory, four 7-track tape drives, drum printer, card reader, card punch, two 8MB disc drives (removable packs). At Humboldt State College where I worked this was used for both administrative and instructional purposes. It replaced an IBM 1620.

The US Force used numerous CDC 3800 series systems in the Air Force Satellite Control Facility located at what is now Onizuka Air Force Station in Sunnyvale, California. As part of the Air Force Satellite Control Network, they were used to do orbital planning and maintenance calculations for defense satellites until they were phased out and replaced by IBM mainframes in the mid-1990s. These systems used the JOVIAL programming language to provide the accuracy necessary for these calculations.

The Center for Naval Analyses had a CDC 3800 from about 1968 until about 1975. It was used for scientific computing in support of operations research for the U. S. Navy.

Michigan State University's Department of Computer Science and Engineering had a CDC 3600[16]

CDC's South West Region had the following accounts late 1960s and early 1970s:

Long Beach Memorial Hospital, Long Beach, California (patient location tracking and billing)
Many of the California state universities (Fullerton, Los Angeles, etc.) in their engineering departments
California State College Los Angeles was also the California state southern region data center. (common admissions, etc.)
California State College San Jose, the Northern California regional data center, had a CDC 3300, as did LA State Southern Regional data center.
Jet Propulsion Lab (Pasadena, California) - test of various outer space modules
University of Texas, El Paso
Vandenburg AFB (missile launch control) (also two CDC 3600s - main base - use unknown)
Thompson-Ramo-Wollridge - Redondo Beach, California
Cal Poly, Pomona, California (engineering school)
Cal Poly Northridge, California (engineering school)
Point Magoo, Naval Air Station (weather balloon tracking/data analysis)
El Centro Naval Air Station
Camp Pendleton, California (US Marine Corps) - development/test bed for Marine Tactical Aircraft Command and Control System - MTACCS) - Initially 3300 - upgraded to a 3500 about 1973-74.
Beverly Hills Data Center - Part of the CDC Cybernet network and also a rarity for CDC - did complete bank computing for about 12 small local banks. A midpoint of the CyberNet system, it interfaced to the Los Angeles Data Center (CDC 6600). The banking accounts were acquired from Corporation for Economic, Industrial and Operations Research (C.E.I.R) - an IBM system (1401?) which was replaced with the 3300. This system had 8 or 10 CDC 854 disk drives and connected to a Burroughs model B-3000 magnetic ink character reader (MICR).

Europe

CERN used a CDC 3800 from 1966 until January 1969, when it was replaced by a CDC 6600. The 3800 was then acquired by State of Geneva and installed at the local University of Geneva.[17][18]

A number of CDC 3000s were installed in France, either in academic computing centers, in software companies or in the aeronautics, nuclear and oil industries.

The University of Oslo had a CDC 3300 (1967 - 1976)[19]

One CDC 3300 was installed in the late 1960s in England, in Computation Research & Development Ltd, a London-based subsidiary of the civil engineering designers Freeman Fox & Partners. It was used for engineering calculations and commercial computing. It was de-commissioned in 1974.

The German Meteorological Service Deutscher Wetterdienst used a CDC 3800 and CDC 3400 for Numerical weather prediction in late 1960s.

Oceania

There were many CDC 3000 series machines in Australia. CSIRO had a 3600 installed in Canberra in 1964, with satellite 3200 machines in Melbourne, Sydney, and probably Brisbane and Adelaide. The Bureau of Census and Statistics had a 3600, 3300, and a 3500 in Canberra, with a 3200 in each of the six state capitals several of which were upgraded to 3300s about 1970. Monash University had a 3200 delivered in 1964.[20] Defence Signals Directorate had at least one. BHP had two 3300 machines at each of its Newcastle and Port Kembla Data centres. They were replaced by 3500s in 1977, and remained in operation until the mid-1980s.

Communist bloc

Communist-ruled Hungary obtained a CDC 3300 machine between 1969 and 1971. It was administered by the National Academy of Sciences throughout the 1970s, mainly for running scientific computations.[21]

Other CDC 3300 systems installed in former Eastern Bloc countries[4] (list not complete):

  • Computing Research Centre, Bratislava
  • Central Statistical Office, Prague.
  • Romanian Aircraft, Bucharest (3500 System)

Standard peripherals
  • 405 - Card reader. 80 column 'high-speed' punched card reader
  • 415 - Card punch, 80 column card punch
  • 501 - Line printer, rotating drum, 136 character wide printer. Note that there were no lower case letters.
  • 505 - Line printer
  • 512 - Line printer, chain type
  • 601 - Magnetic tape drive
  • 604 - Magnetic tape drive
  • 607 - Magnetic tape drive
  • 609 - Magnetic tape drive (9-track)
  • 700 series - Optical page reader
  • 800 - Rotating magnetic memory series
  • 808 - Rotating disks, approx 32 inches per disk, approx 32-36 disks per spindle.
  • 852 - Disk drive with removable media pack, 2 to 3 million seven 7-bit characters, six disks (10 recording surfaces)/pack. Data-compatible with IBM 1311[22]
  • 853 - Similar to 852, 4 million characters. Media mechanically interchangeable with IBM 1311, but not recorded data[22]
  • 854 - Similar to 853, 8 million characters[22]
  • 915 - Optical page reader

The CDC 6000 series were also initially marketed with many of the same peripherals.

See also

References
  1. "CDC 3100 (Control Data Corporation) computer - CERN".
  2. "Compiling SIMULA".
  3. "@ 5 Control Data I Corporation" (PDF).
  4. Steve Cunningham (January 7, 2010). "Fixed-Head Disk Reader for the CDC 3300".
  5. 1964 Computer Survey
  6. 1967 Adams Report
  7. Cayton, Andrew R. L.; Sisson, Richard; Zacher, Chris (2006). The American Midwest: An Interpretive Encyclopedia. ISBN 0253003490.
  8. "CSULB's first batch computer, a Control Data Corp. (CDC) 3150""Emerities - In Memorium". 2010.
  9. "LI Bedford Institute of Oceanography L'Institut Oceanographique" (PDF).
  10. JD Mahle Jr (November 28, 1969). "ERIC - Information Retrieval System".
  11. "Real Machines with 24-bit and 48-bit words".
  12. Henley, Ernest J.; Lewins, Jeffery (2014). Advances in Nuclear Science and Technology. ISBN 1483215660.
  13. Oregon State University, Corvallis, Oregon 97331 "Primer for users of Oregon State's Open Shop Operating System (os-3)" (PDF). September 1972.
  14. "Users Manual CDC 3150 - California State University, Sacramento". 1972.
  15. "FRONT COVER, Users Manual, CDC 3150 - California State University, Sacramento". 1972.
  16. "Michigan State University".
  17. The CDC 3800 boots up temporarily, 10 August 1966
  18. CERN bulletin, 20 January 1969
  19. Bubenko, Janis; Impagliazzo, John; Soelvberg, Arne (2005). History of Nordic Computing: IFIP WG9.7. ISBN 038724168X.
  20. Video on YouTube, Video footage taken by Ron Bird of the touchdown at Essendon Airport of the Flying Tigers CL44 Swing Tail freighter and the unloading of the CDC 3200 system at the Monash Clayton campus by Wridgway Bros, 1964.
  21. "Történetünk" [Our history] (in Hungarian). Retrieved 24 February 2012.
  22. https://docs.google.com/viewer?url=http%3A%2F%2Fs3data.computerhistory.org%2Fbrochures%2Fcdc.disk-852-4.ca1970.102646314.pdf
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.