[email protected] (Shmuel Metz , Seymour J.) writes: > No such animal; there was a CP-67 for the S/360, but VM was strictly > for the S/370 and its name reflected that.
re: http://www.garlic.com/~lynn/2014d.html#16 [OT ] Mainframe memories almost. one of the earliest uses of the internal network was distributed development effort between science center and endicott ... to create 370 virtual machine (including 370 virtual memory support) on cp67 running on real 360/67. this was referred to as the cp67h level updates. posts mentioning internal network http://www.garlic.com/~lynn/subnetwork.html#internalnet then there was modifications to cp67 to run on 370 virtual memory architecture instead of 360/67. this was referred to as cp67i level updates. since science center cp67 service allowed students and staff from various univ. in the boston/cambridge area ... it wasn't allowed to expose them to 370 architecture. so the production cambridge system ran cp67l systems. cp67h then ran in a 360/67 virtual machine on the production cp67i system. then under cp67h (running in 360/67 virtual machine under cp67l system), cp67i ran in a 370 virtual machine. Then it would run cms in a 370 virtual machine under cp67i system (in 370 virtual machine under cp67h which ran in 360/67 virtual machine under cp67l on real 360/67). this was in regular production use a year before the first engineering 370 processor was operational ... in fact cp67i system was used to boot on the first engineering 370 processor as test (first boot didn't work because they had reversed the op-codes for rrb and ptlb ... had to patch cp67i to correspond with the hardware bug ... until they fixed it). in fact the original multi-level source update ... mentioned here http://www.garlic.com/~lynn/2014d.html#19 Write Inhibit was originally done for the l, h, & i software system development. then some people from san jose came out for a stint at cambridge and did the cp67 software to provide 2305 & 3330 device support. for a very long time ... cp67i with sj 2305&3330 device support was the primary software that ran on 370 processors internally. this is old email reference to continuing to work on cp67 http://www.garlic.com/~lynn/2006v.html#email731212 http://www.garlic.com/~lynn/2006w.html#email750102 http://www.garlic.com/~lynn/2006w.html#email750430 during much of the FS period ... even periodically ridiculing FS activities http://www.garlic.com/~lynn/submain.html#futuresys and then finally moving lots of enhancements to vm370 base for "csc/vm" which became extensively used at internal datacenters (most of them by then having migrated from cp67 to vm370). With the failure of FS ... there was mad rush to get stuff back into 370 product pipeline ... which contributed to decision to picking up some of my enhancements for shipping in official product. -- virtualization experience starting Jan1968, online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
