IBM System/360 Model 50

IBM System/360 Model 50 console and CPU with front panel

The IBM System/360 Model 50 is a member of the IBM System/360 family of computers. The Model 50 was announced in April 1964 with the other initial models of the family, and first shipped in August 1965 to the Bank of America.[1]

Models

There are four models of the 360/50.[2]:page 5 They vary by the amount of core memory with which the system is offered. The F50, or 2050F is equipped with 65,536 bytes, the G50 has 131,072 bytes, the H50 262,144 bytes, and the I50 524,288 bytes.[2] The system can also attach IBM 2361 Large Capacity Storage (LCS) modules which provide up to 8,388,608 bytes of additional storage, however with a considerably slower memory cycle time of 8 microseconds compared to the 2 microseconds of processor storage.[2]

Relative performance

The system has a CPU cycle time of 500 nanoseconds, 25% faster than the Model 40 and 40% slower than the Model 65. Processor storage is magnetic core memory that transfers four bytes per 2 microsecond cycle. It has "protected" and "local" core storage for registers and internal buffers with cycle times of 200 and 500 nanoseconds respectively.

Features

The Model 50 implements the complete System/360 "universal instruction set" architecture, including floating-point, decimal, and character operations as standard features. The "direct control" instructions are an optional feature. Optional microcode providing compatibility with either the IBM 1410/7010 or 7070/7074 systems is available.

An IBM 1052 printer/keyboard for use as an operator's console is optional. The I/O options include one channel-to-channel adapter (CTCA) and up to three selector channels. A multiplexer channel for attachment of slow-speed devices is standard on all models. The F50 has 64 subchannels, so it can attach up to 64 slow-speed devices on its multiplexer channel. The other models have 128 subchannels. This can optionally increase to 256 subchannels on the H50 and I50.[2]

Microcode

The Model 50 uses a 90 bit (or 85 bit, depending on definition) "horizontal microcode" instruction format, with each word containing 15 (or 25) separate fields.[3] There are 2816 words of microcode storage.[4]

Read-only control storage for microcode employs "balanced capacitor technology" (BCROS) with cycle time of 500 nanoseconds, designed by Anthony Proudman in IBM's Hursley laboratory and implemented by Fernando "Fred" Neves. This technology uses two capacitors to represent each bit.

B&W closeup of 360/50 console

System software

It was possible to choose DOS/360, OS/360 MFT (Multi-programming with a Fixed number of Tasks), or OS/360 MVT (Multi-programming with a Variable number of Tasks) as the Operating System of an IBM System/360 Model 50. Few chose MVT.[5]

The choice of operating system for the System/360 Model 50 was based primarily on the amount of main storage. The F50, with 65,536 bytes of main storage, can not run OS/MFT, which requires a minimum of 131,072 bytes of main storage.[6] DOS/360 has a minimum of 16,384 bytes of main storage.[7]

Systems with 131,072 or more bytes of main storage could run OS/360. Although 360/50 systems equipped with 1 MB or more[8] could and did run MVT[9][10] one IBMer described this as "[getting] blood out of the turnip", and noted that "most didn't run MVT".[5]

Reasons for a 360/50 site to run MFT[11] rather than MVT were:

Time-sharing (CALL/OS)

IBM advertised time-sharing capability by featuring what originally was known as CALL/360[18] (note the 'SLASH' - which was retained in the name of its successor) and later[19] was named CALL/OS. CALL/OS featured its own versions of BASIC [20] as well as FORTRAN IV[21] and PL/I,[22][23] rather than the versions implemented by the MFT/MVT compilers known as FORTRAN G, FORTRAN H and PL/I F. CALL/OS is sometimes referred to as "CALL-OS".[24]

Installations with a larger model of the System/360 family sometimes ran/retained the combination of MFT and CALL/OS,[21] rather than switch to MVT, a pre-requisite for TSO,[25] after an upgrade.

References

  1. ↑ Pugh, Emerson W.; Johnson, Lyle R.; Palmer, John H. (1991). IBM's 360 and Early 370 Systems. MIT Press. ISBN 0-262-16123-0.
  2. 1 2 3 4 IBM System 360 Model 50 Functional Characteristics (PDF). IBM. 1967. A22-6898-1. Retrieved Sep 20, 2016.
  3. ↑ Smotherman, Mark. "A Brief History of Microprogramming" (PDF). Retrieved Sep 26, 2015.
  4. ↑ Kent, Allen (ed); Williams, James G. (ed) (1993). Encyclopedia of Computer Science and Technology volume 28. CRC Press. p. 39. ISBN 0-8247-2281-7. Retrieved Sep 26, 2015.
  5. 1 2 William H. Blair (January 18, 2004). "Re: 40th anniversary of IBM System/360 on 7 Apr 2004". ibm-main (Mailing list). Your point is well taken. But most didn't run MVT, and many that did had LCS (Large Capacity Storage). MVT was not very popular. Nonetheless, I ran a system that ran MVT just fine with only 256MB; maximum REGION size was 114MB, which was perfectly fine for the workload. I suspect that if MVT was being used on a /65 or /75, then 512KB was installed. But, there were a lot of folks that ran MVT on a /50 with 384KB. We got blood out of the turnip back in those days.
  6. ↑ IBM System/360 Operating System: MFT Guide OS Release 21.7 (PDF). IBM. March 1972. p. 69. GC27-6939-10.
  7. ↑ IBM System/360 Disk and Tape Operating Systems Concepts and Facilities (PDF). IBM. October 1970. p. 5. GC24-5030-8. “Disk and Tape Operating Systems are comprehensive sets of language translators and service programs operating under the supervisory coordination of an integrated control program. They require an IBM System/360 with at least 16K bytes of main storage.”
  8. ↑ J. M. Graves. Using SMF and TFLOW for Performance Enhancement. Eighth Meeting of Computer Performance Evaluation Users Group (CPEUG).
  9. ↑ "Re: 360/50 microcode listing". cctalk@classiccmp.org (Mailing list). May 7, 2015.
  10. ↑ "An overview of the history of development of the EPA STORET System, with some comments on future timelines and plans." (PPT). November 7, 2001. p. 3.
  11. ↑ Gerard S. (June 1, 2001). "Re: Price of core memory". Newsgroup: alt.folklore.computers. We had to revert to MFT to get a 98K partition, plus a reader and writer.
  12. ↑ IBM System/360 Operating System: MVT Guide (PDF). IBM. August 1974. GC28-6720-5. The minimum main storage is 262,144 (256K) bytes
  13. ↑ IBM System/360 Operating System: Storage Estimates (PDF). IBM. April 1973. GC28-6551-16.
  14. ↑ "256 KB of memory... in the 1960s was quite a large amount" Ray Saunders, www.os390-mvs.freesurf.fr/mvs360.htm
  15. ↑ http://www.os390-mvs.freesurf.fr/mvs360.htm
  16. ↑ Padegs, A. (September 1981). "System/360 and Beyond". IBM Journal of Research and Development. IBM. 25 (5): 377–390. doi:10.1147/rd.255.0377.
  17. ↑ A convenience sample of ads for used 360/50 and 360/65 configurations in the back of Computerworld for the 1971 - 1973 period show mostly MVT installed on 360/65 OS and NOT EVEN ONE 360/50 with MVT
  18. ↑ CALL/360: Terminal Reference Manual (PDF). IBM. 1969.
  19. ↑ Ed Thelen. "2005 Mini GE-Reunion".
  20. ↑ CALL/360: BASIC Reference Handbook (PDF). Service Bureau Corporation. 1970.
  21. 1 2 Jerry W. Wicks (1975). "The calculation of the index of dissimilarity on a computer terminal". Behavior Research Methods & Instrumentation. 7 (4): 380. The program (Dissim) is written in Call-os Fortran IV and is now in use on an IBM 360/75 with teletypewriter remote facilities.
  22. ↑ Timothy Marino (November 1980). "Adventure (letter to the editor)". Creative Computing. 6 (11): 12. Can you or any of your readers direct me to a version of Adventure written in standard Basic, Fortran, or IBM Call-OS PL/I?
  23. ↑ CALL/360 - OS PL/I System Manual - Volume I (PDF). IBM. January 1971. GY20-0561-1.
  24. ↑ CALL-OS: learning FORTRAN; terminal-oriented self-study text. IBM. 1972.
  25. ↑ IBM System/360 Operating System: Time Sharing Option Guide (PDF). IBM. July 1972. GC28-6698-5.
This article is issued from Wikipedia - version of the 11/20/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.