paulgboul...@aim.com (Paul Gilmartin) writes: > OS simulation was implemented only to the extent necessary > to support (some of) the supported utilities. For example, > PDS member statistics (the user info area) were deemed > unnecessary and not implemented. ISPF/VM goes to outrageous > gyrations with side-files to simulate them. > > Long ago, a co-worker said VM would do well to abandon CMS > and support MVT proper in a VM. But he's an acknowledged > OS partisan.
cp67/cms group split off from science center, moved to the 3rd flr absorbing the ibm boston programming center (had been responsible for lots of stuff included cps ... converstational programming system that ran under mvt supporting both conversational basic & PLI) ... and then morphing into vm370/cms group and growing fast. it outgrew the 3rd floor and moved out to the old sbc bldg in burlington mall (sbc going to control data in legal settlement). some of the people significantly enhanced o/s simulation ... at least doubling the amount of cms o/s simulation code .. creating joke that it simulated mvt much better than mvs (for less than 1% the code). provided o/s simulation both on cms filesystem as well on os/360 formated disks. now in the aftermath of future system failure ... some past posts http://www.garlic.com/~lynn/submain.html#futuresys and mad rush to get stuff back into 370 product pipelines (lots of 370 efforts had been killed off and/or at least suspended during future system period). part was q&d 3033 ... remapping 168-3 logic to faster chips overlapped with 3081 which was some left-over pieces from future system effort. some more detail here http://www.jfsowa.com/computer/memo125.htm also head of POK convinced head of POK convinced corporate to kill off vm370, shutdown the burlington mall group, and move all the people to POK to work on mvs/xa (or otherwise mvs/xa wouldn't meet its ship date). they were woking on not letting vm370 group know until the last possible minute to minimize the number that might be able to escape the move. unfortantely the information leaked early, there was big witch hunt for the source of the leak ... and numerous excaped to various vendors in the area (joke that as result, head of POK was one of the major contributors to dec vax/vms). in all of the commotion, the o/s simmulation enhancements evaporate ... never to be seen again. endicott eventually managed to salvage the vm370/cms product mission, but had to reconstitute a development group from scratch. some amount of code quality comments on vmshare during the period reflects growing the new group. http://vm.marist.edu/~vmshare/ later when company declared CMS strategic interactive platform (and abondoned TSO for that purpose) ... there was quite a bit of efforts getting CMS running on MVS. it was operational but because of all sorts of structural issues in MVS ... it would never achieve human factors and interactive characteristics. -- virtualization experience starting Jan1968, online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
