Abstract
The environment that may confront an operating system has lately undergone great change. For example, in its several compatible models, system/360 spans an entire spectrum of applications and offers an unprecedented range of optional devices.1 It need come as no surprise, therefore, that os/360—the Operating System for system/360—evinces more novelty in its scope than in its functional objectives.
This is a preview of subscription content, log in via an institution to check access.
Preview
Unable to display preview. Download preview PDF.
Cited References and Footnotes
-For an introduction to system/360, seeG. A. Blaauw and F. P. Brooks, Jr., “The structure of system/360, Part I, outline of the logical structure,” IBM Systems Journal 3, No. 2, 119–135 (1964).
The restrictions exclude model 44, as well as model 20. The specialized operating systems that support these excluded models are not discussed here.
C. W. Adams and J. H. Laning, Jr., “The MIT systems of automatic coding: Comprehensive, Summer Session, Algebraic,” Symposium on Automatic Coding for Digital Computers, Office of Naval Research, Department of the Navy (May 1954).
In the case of the ibm 709 and 704 computers, the earliest developments were largely due to the individual and group efforts of share installations. The first operating systems developed jointly by ibm and share were the share Operating System (sos) and the Fortran Monitor System (fms).
G. F. Leonard and J. R. Goodroe, “An environment for an operating system,” Proceedings of the I9th National ACM Conference (August 1964).
A. W. Holt and W. J. Turanski, “Man to machine communication and automatic code translation,” Proceedings Western Joint Computer Conference (1960).
G. Radin and H. P. Rogoway, “NPL: highlights of a new programming language,” Communications of the ACM 8, No. 1, 9–17 (January 1965).
Cited References and Footnote
An historic review of operating systems, with emphasis on I/O control and job scheduling, appears in Reference 4. Operating systems that provided for multiprogramming are described in References 5, 6, and 7. One on-line inventory application is described in Reference 8, and some indication of techniques used in its solution are given in References 9 and 10.
G. A. Blaauw and F. P. Brooks, Jr., “The structure of system /36o: Part I-outline of the logical structure,” IBM Systems Journal 3, No. 2, 119–135 (1964).
W. P. Heising and R. A. Lamer, “A semi-automatic storage allocation system at loading time,” Communications of the ACM 4, No. 10, 446–449 (October 1961).
T. B. Steel, Jr., “Operating systems,” Datamation 10, No. 5, 26–28 (May 1964).
E. S. McDonough, “stretch experiment in multiprogramming, ” Digest of Technical Papers, ACM 62 National Conference, 28 (1962).
E. F. Codd, “Multi-programming,” Advances in Computers, Volume 3, Edited by Franz L. Alt and Morris Rubinoff.
G. F. Leonard, “Control techniques in the CL-II Programming System,” Digest of Technical Papers, ACM 62 National Conference, 29 (1962).
M. N. Perry and W. R. Plugge, “American Airlines sabre electronic reservation system,” WJCC Proceedings, 593-601 (May 1961).
M. N. Perry, “Handling of very large programs,” Proceedings of JFIP Congress 65, Volume 1, 243–247 (1965).
W. B. Elmore and G. J. Evans, Jr., “Dynamic control of core memory in a real-time system,” Proceedings of IFIP Congress 65, Volume 1, 261–266 (1965).
Cited Reference and Footnotes
A. S. Noble, Jr., “Design of an integrated programming and operating system, Part I, system considerations and the monitor,” IBM Systems Journal 2, 153–161 (June 1963).
Although the CHECK macroinstruction includes the effect of the WAIT macroinstruction, the latter may also be used prior to CHECK.
Ordinarily, the results of a catalog search include the device type, the identification number of the desired volume, and label verification information. If the data set is a generation of a generation group (a case not considered in the main discussion), the results are the location of an index of generations and an archetype data-set label.
Generally, “logical channel” and physical channel are indistinguishable. The logical channel is taken to be the set of physical channels by which a device is accessible. All devices (independent of their type) that share exactly the same set of physical channels are associated with the same logical channel queue. For example, a set of tape drives attached to physical channels 1 and 2 would share a logical channel distinct from that of a printer attached only to physical channel 1.
In general, the control unit is initialized to inhibit seek operations that move the access mechanism. More stringent restrictions are placed on channel programs that actually refer to cylinders shared by two or more data sets. This is not to say that inter-cylinder seek operations are disallowed; rather, the I/O supervisor verifies that these operations refer to areas within the extent of the data set. During inter-cylinder seek operations, the channel and control unit are freed for other uses.
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2001 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Brooks, F., Mealy, G.H., Witt, B.I., Clark, W.A. (2001). The Functional Structure of OS/360. In: Broy, M., Denert, E. (eds) Pioneers and Their Contributions to Software Engineering. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-48354-7_6
Download citation
DOI: https://doi.org/10.1007/978-3-642-48354-7_6
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-42290-7
Online ISBN: 978-3-642-48354-7
eBook Packages: Springer Book Archive