Skip to content
Surf Wiki
Save to docs
general/ibm-system-360-mainframe-line

From Surf Wiki (app.surf) — the open knowledge base

IBM System/360 Model 30

IBM computer model from 1960s

IBM System/360 Model 30

Summary

IBM computer model from 1960s

FieldValue
nameIBM System/360 Model 30
titleIBM System/360 Model 30
logo_size120px
image_size270px
logoFile:IBM Logo 1956 1972.svg
imageFile:IBM System360 Model 30.jpg
captionIBM System/360 Model 30 at the Computer History Museum
manufacturerInternational Business Machines Corporation (IBM)
familySystem/360
releasedate
price$133,000+
discontinuedJune 22, 1970
memory8 - 64 K Core
websiteIBM Archives

The IBM System/360 Model 30 was a low-end member of the IBM System/360 family. It was announced on April 7, 1964, shipped in 1965, and withdrawn on October 7, 1977. The Model 30 was designed by IBM's General Systems Division in Endicott, New York, and manufactured in Endicott and other IBM manufacturing sites outside of U.S.

History

The Model 30 was a popular IBM mainframe which was announced in 1964 as the least powerful of the System/360s.The less powerful Model 20, offered only partial compatibility with the rest of the System/360 line. The System/360 series was the first line of computers in the world to allow machine language programs to be written that could be used across a broad range of compatible machines of different sizes. It was the smallest model that had the full System/360 instruction set (unlike the Model 20) and served as a stand-alone system, communications system or as a satellite processor of a larger system.

The first delivery of the 360/30 was in June 1965 to McDonnell Aircraft.

Along with the 360/40, these were the two largest revenue producing System/360 models,

Models

closeup (profile) of 360/30 Console

Four modelsLower case "M" of the 360/30 were initially offered. They vary by the amount of core memory with which the system was offered. The C30, D30, E30 and F30 were respectively configured with 8K, 16K, 32K and 64K of core memory.

It was little publicized that there were two versions of the Model 30, known (on the rare occasions when they were distinguished at all) as the 30-1 and the 30-2. The original 30-1 had a 2.0 microsecond storage cycle. Later, after the first 1000 30-1 were shipped, it was replaced by the 1.5-microsecond 30-2, although the 30-1 was silently retained in the sales catalog. The two were cosmetically different; the 30-1 looked like other System/360 models, with indicator lamps exposed on the front panel and labeled, but the 30-2 took a retrograde design step, putting the lights behind a stencil, as they had been on pre-360 machines like the IBM 1401.

The (faster) 30-2 had an additional model, DC30, with 24K of memory.

The 7th edition of IBM System/360 Basic Operating System Programmer's Guide, dated September 1967, lists first among major changes support for "an intermediate storage size (24K) for System/360 Model 30."

96K upgrade

In response to competitive pressures, IBM introduced a memory upgrade option, allowing 96K on a 360/30. It seems, based on the system's front panel, that a provision for supporting more than 64K had been pre-planned.

Microcode

The Model 30 CPU used an 8-bit microarchitecture with only a few hardware registers; everything that the programmer saw was emulated by the microprogram. Handling a 4-byte word took (at least) 6 microseconds, based on a 1.5 microsecond storage access cycle time.

The microcode was stored in CCROS (Card Capacitor Read-Only Storage) developed in Endicott. The Model 30 and Model 40 were originally supposed to share the transformer read-only storage (TROS) being developed at IBM Hursley, but CCROS was cheaper to manufacture. A hole punched at a specific location removed the copper tab and encoded a zero, unpunched locations were read as ones.

IBM 360 Model 30 front panel and internal components

System configuration

A typical, early, basic Model 30 system had the following configuration:
Model 30 processor
Operator console
Unit record device
Line printer
Disk storage
Tape storage
IBM 360 Model 30 front panel closeup

To keep costs down, CPU features such as the interval timer and storage-protection feature were optional.

System software

Operating System choices:

  • BPS - Basic Programming Support
  • BOS - Basic Operating System
  • TOS - Tape Operating System
  • DOS - Disk Operating System

BPS (Basic Programming Support) did not require a disk drive or tape drive. It was introduced in 1965, and has been described as "primarily a set of utilities and compilers (that) existed on cards only."

BOS (Basic Operating System) required a disk drive, but, like BPS, could run on the smallest 360/30, the 8K model C30.

The minimum memory needed to run DOS or TOS was 16 KB.

TOS (Tape Operating System), as the name suggests, required a tape drive but no disk. It shared most of the code base and some manuals with IBM's DOS/360 and went through 14 releases. TOS was discontinued when disk drives became more affordable.

DOS (Disk Operating System) was a popular choice for the Model 30.

The smaller BOS had a spooling system for queued printing, whereas DOS did not until the arrival in the late 1960s of "an add-on component called POWER."

Programming languages

Programming was mostly in the COBOL, RPG and Assembler languages for the commercial applications which were the predominant uses of this computer. Fortran could also be used for the scientific and engineering applications, and a PL/I subset compiler PL/I(D) was available. COBOL programs for other computers could be run after recompiling on the System/360, except that the INPUT-OUTPUT SECTION had to be re-written to describe to the System/360 device assignments.

Compatibility features

The ability to continue running programs designed for earlier systems was crucial to selling new hardware. Although the instruction set of System/360 was not backward compatible with earlier systems, IBM provided emulators for the earlier systems.

IBM 1400 series emulation

With the additional Compatibility Feature hardware and Compatibility Support software under DOS/360, the IBM 1401/1440/1460 object programs could be run in the emulation mode, with little or no reprogramming. Many installations included the compatibility feature, allowing older programs to be run.

IBM 1620 emulation

Although the 360/30 could be configured to emulate an IBM 1620, two factors made it less crucial than the above IBM 1400 series emulation:

  • The IBM 1130 was the preferred successor to the IBM 1620.
  • Fortran accounted for a significant part of how the 1620 was used, and IBM 1620 Fortran programs could be converted to run on System/360.

Notes

References

References

  1. (23 January 2003). "IBM Archives: System/360 Model 30".
  2. (1991). "IBM's 360 and early 370 systems". MIT Press.
  3. (1969). "Computer Usage Essentials". McGraw-Hill.
  4. (August 1971). "IBM System/360 Model 30 Functional Characteristics".
  5. (September 1967). "IBM System/360 Basic Operating System Programmer's Guide". IBM.
  6. A posted submission to Ed Thelen's 360/30 writings (http://ed-thelen.org/comp-hist/ibm-360-30.html) from December 2005, labeled "Historical Note", indicated that, in response to a 128K offering by a small company, IBM actually introduced an upgrade, allowing 96K on a 360/30. The author noted that this allowed hour-plus tape/disk-based sorts to be done in-core in minutes.
  7. "IBM System/360 Model 30 Storage Expansion Feature Manual: RPQ's EA3807, EA1527; or RPQ's Y91283 and Y91325 (World Trade)".
  8. http://www.ljw.me.uk/ibm360/links has an entry named '''Glenn's Computer Museum''' (http://www.glennsmuseum.com/ibm/ibm.html) that has the following annotation: note that this front panel has indicators for extra address bits to allow more than 64k main storage
  9. (June 1967). "Field Engineering Theory of Operation, 2030 Processing Unit, System/360 Model 30". IBM.
  10. "Model 30 Microprogramming Language". IBM.
  11. "IBM System/360 Model 40 Operating Techniques". IBM.
  12. Dave Morton. (April 2015). "IBM Mainframe Operating Systems: Timeline and Brief Explanation For the IBM System/360 and Beyond".
  13. Joe Morris. (April 25, 2005). "DOS/360: Forty years".
  14. (October 1970). "IBM System/360 Disk and Tape Operating Systems Concepts and Facilities".
  15. (August 1973). "DOS and TOS Utility Programs".
  16. Anne and Lynn Wheeler. (May 28, 2009). "Re: IBM 1401".
  17. Computerworld, Sept. 5, 1977, p.40 - quotes an IBM task force report that referred to "price alone rather than by price/performance."
  18. Of those Model 30 and Model 40 machines still around in 1981/being replaced by 4300 systems, a Computerworld survey showed that DOS was what they ran/had run, May 25, 1981, p. 26
  19. Edward L. Bosworth. "Programming Assembler Language on the IBM Mainframes: An Introduction".
  20. Ed Thelen. "IBM System 360, Model 30".
  21. "IBM 360/30".
  22. (1965). "IBM System/360 Basic Programming Support and IBM Basic Operating System/360 Programming Systems Summary".
  23. Capers Jones. (21 November 2013). "The Technical and Social History of Software Engineering".
  24. Computerworld, April 24, 1989, page 1
  25. (February 1969). "IBM System/360 Disk Operating System 1401/1440/1460 Emulator Programs: Compatibility Support/30 & /40". IBM.
  26. Edwin D. Reilly. (2003). "Milestones in Computer Science and Information Technology".
  27. Dan Ryan. "History of Computer Graphics".
  28. (1962). "Basic Programming Concepts and The IBM 1620 Computer". Holt, Rinehart and Winston.
Wikipedia Source

This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page.

Want to explore this topic further?

Ask Mako anything about IBM System/360 Model 30 — get instant answers, deeper analysis, and related topics.

Research with Mako

Free with your Surf account

Content sourced from Wikipedia, available under CC BY-SA 4.0.

This content may have been generated or modified by AI. CloudSurf Software LLC is not responsible for the accuracy, completeness, or reliability of AI-generated content. Always verify important information from primary sources.

Report