[email protected] (DASDBILL2) writes: > Close. OS/VS2 was released having been already pre-morphed into SVS > and MVS. SVS was first called OS/VS2 Release 1, was first available > in 1974, and that's when I worked with it. MVS was first called > OS/VS2 Release 2, was first available slightly later (1975, I think), > but I didn't begin working with MVS until 1977. VM was also first > released around 1975. Other grand buzzwords that morphed were > "loosely coupled multiprocessing" and "tightly coupled > multiprocessing". The loose version became shared SPOOL, and the > tight version became simply multiprocessing (several CPUs sharing the > same central storage). And now we have SYSPLEXEs with both loosely > and tightly coupled systems comPLEXly interwoven. Your date of 1980 > for MVS is about the time when MVS's initially disappointing > performance and RAS were greatly improved.
re: http://www.garlic.com/~lynn/2014d.html#54 Difference between MVS and z / OS systems http://www.garlic.com/~lynn/2014d.html#55 Difference between MVS and z / OS systems as mentioned upthread, os/vs2 svs started out using cp67 ccwtrans crafted into EXCP processing to perform building a copy of the passed channel program with virtual addresses converted to real addresses. the science center recently had its 50th anniv (1Feb1964) http://www.garlic.com/~lynn/2014b.html#88 Happy 50th Birthday to the IBM Cambridge Scientific Center, Kendall Square Pioneer http://www.garlic.com/~lynn/2014b.html#105 Happy 50th Birthday to the IBM Cambridge Scientific Center the science center that it would be the center for virtual memory system and bid to MIT for Project Mac followon to CTSS on IBM 7094. However, that effort went to another group (TSS/360 and 360/67) and IBM loosing the big to GE645. Some of the CTSS people went to IBM science center on the 4th flr and others went to Project Max Multics (ge645) on the 5th flr. The science center decides to go ahead and work on virtual memory anyway ... getting a 360/40 and making the hardware modifications to support virtual address translation ... and builds the CP/40 system ... which turns out to also be a virtual machine system with CMS (and 360 guest operating systems) running in virtual machine. CMS borrows some amount from what was learned with the online CTSS system. CP40 talk given at SEAS (european share) meeting in 1982 http://www.garlic.com/~lynn/cp40seas1982.txt when standard virutal memory 360/67 product becomes availalbe, cp40 morphs into cp67. Science center installs cp67 on the (MIT) Lincoln Labs 360/67 in 1967 and then installs it at univ system last week of Jan1968 (where I'm undergraduate). recent posts discussing several customers were talked into ordering 360/67s to run tss/360 ... but because of production issues with tss/360, most used 360/67 for other purposes ... recent posts http://www.garlic.com/~lynn/2014d.html#16 Mainframe memories http://www.garlic.com/~lynn/2014d.html#22 Mainframe memories http://www.garlic.com/~lynn/2014d.html#23 Mainframe memories http://www.garlic.com/~lynn/2014d.html#25 Mainframe memories http://www.garlic.com/~lynn/2014d.html#26 Mainframe memories note that long ago and far away ... my wife was con'ed into going to POK to be responsible for loosely-coupled architecture ... where she developed peer-coupled shared data architecture some past posts http://www.garlic.com/~lynn/subnetwork.html#shareddata however, little uptake (except for IMS hotstandby until sysplex and parallel sysplex) and constant battles with the communication group trying to force her to use sna/vtam for loosely-coupled operation ... eventually took its toll and she leaves. then there is the issue with MVS 15min MTBF when tried in the disk engineering labs. I rewrote I/O supervisor so it would never fail ... so they could do ondemand concurrent multiple device testing ... which was enormous improvement in productivity (compared to their 7x24 stand-alone testing schedules). I wrote-up a report ... and happened to mention the MVS 15min MTBF issue ... which brings down the wrath of the MVS RAS group on my head ... some mention in these past posts getting to play disk engineer in bldgs 14&15 http://www.garlic.com/~lynn/subtopic.html#disk this is old email where FE standard error regression tests for 3380 (reasonably expected errors from 3380) results in MVS failure in all cases ... and in 2/3rds of the cases leaving no evidence of what caused the failure. http://www.garlic.com/~lynn/2007.html#email801015 -- 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
