IBM System/360 Model 67: Difference between revisions

Content deleted Content added
Legacy: Go with the -1 version of the M145 processing unit theory manual, as it's online at Bitsavers. IBM published it; one or more people *working for* IBM wrote it. Use the page numbers that appear at the bottom of the page.
Legacy: And just like that, the Model 145's associative memory was used for paging.
Line 338:
The S/360-67 had an important legacy. After the failure of [[TSS/360]], IBM was surprised by the blossoming of a time-sharing community on the S/360-67 platform ([[CP/CMS]], [[Michigan Terminal System|MTS]], [[MUSIC/SP|MUSIC]]). A large number of commercial, academic, and service bureau sites installed the system. By taking advantage of IBM's lukewarm support for time-sharing, and by sharing information and resources (including source code modifications), they built and supported a generation of time-sharing centers.
 
The unique features of the S/360-67 were initially ''not'' carried into IBM's next product series, the [[System/370]], although the [[IBM System/370 Model 145|370/145]] had an [[Content-addressable memory|associative memory]] that appeared more useful for paging than for its ostensible purpose.<ref name=SY24-3581-1>{{cite manual
| url = http://www.bitsavers.org/pdf/ibm/370/fe/3145/SY24-3581-1_3145_Processing_Unit_Theory-Maintenance_Oct71.pdf
| title = IBM Maintenance Library 3145 Processing Unit Theory - Maintenance
Line 347:
However, IBM faced increasing customer demand for time-sharing and virtual memory capabilities. IBM also could not ignore the large number of S/360-67 time-sharing installations &ndash; including the new industry of [[time-sharing]] vendors, such as [[National CSS]]<ref>[http://www.computerhistory.org/corphist/documents/doc-42ae226a5a4a1.pdf "A technical history of National CSS"], Harold Feinleib, Computer History Museum (March 2005)</ref><ref>[http://www.computerhistory.org/corphist/documents/doc-422fd82791f26.pdf "From the very beginning... from my vantage point — early history of National CSS"], Dick Orenstein, Computer History Museum (January 2005)</ref> and [[Interactive Data Corporation]] (IDC),<ref>Varian, op. cit., pp. 24, Note 76 – IDC systems (quoting Dick Bayles)</ref> that were quickly achieving commercial success.
 
In 1972, IBM added virtual memory features to the S/370 series, a move seen by many as a vindication of work done on the S/360-67 project.; Thethe survivalmicrocode andin successthe of370/145 IBM'swas [[VMupdated (operatingto system)|VM]]use family,the andassociative ofmemory virtualizationfor technologyvirtual inaddress general,translation.<ref alsoname=SY24-3581-4>{{cite owe much to the S/360-67.manual
| url = http://www.bitsavers.org/pdf/ibm/370/fe/3145/SY24-3581-4_3145_Processor_Theory_Maintenance.pdf
| title = IBM Maintenance Library 3145 Processing Unit Theory - Maintenance
| id = SY24-3581-4
| publisher = IBM
}}{{rp|CPU 139}}</ref> The survival and success of IBM's [[VM (operating system)|VM]] family, and of virtualization technology in general, also owe much to the S/360-67.
 
In 2010, in the technical description of its latest mainframe, the [[IBM zEnterprise System|z196]], IBM stated that its software virtualization started with the System/360 model 67.<ref>[http://publibfp.dhe.ibm.com/epubs/pdf/sg247832.pdf SG24-7832-00: IBM zEnterprise System Technical Introduction], page 57: "Starting in 1967, IBM has continuously provided software virtualization in