Content deleted Content added
m v2.04b - Bot T20 CW#61 - Fix errors for CW project (Reference before punctuation - Misnested tags) |
m convert special characters (via WP:JWB) |
||
Line 342:
}}{{rp|CPU 117–129}}</ref> This was largely fallout from a bitter and highly visible political battle within IBM over the merits of [[time-sharing]] versus [[batch processing]]. Initially at least, time-sharing lost.
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 – 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
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. 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:
its mainframe servers.
== References ==
|