[email protected] (Shmuel Metz , Seymour J.) writes: > Except for TSO. Also, SVS dropped some features of OS/360 MVT, e.g., GJP, > RJE, and reimplimented others, e.g., loading transient SVC routines.
at various times, there were various degrees about killing off both cp67 and vm370 products. in the mad rush to get 370 products back into the pipeline ... after future system product was killed, http://www.garlic.com/~lynn/submain.html#futuresys the mvs/xa group managed to convince corporate that vm370 should be killed, the burlington mall development location be shutdown and all the people moved to pok ... or otherwise mvx/xa wouldn't be able to meet its product schedule. endicott finally managed to convince corporate to transfer vm370 product, but they effectively had to reconstitute a development group from scratch. in any case, possibly with the big upswing in vm370 4341s in the late 70s and early 80s ... the corporation was convinced to declare vm370/cms the strategic interactive solution. then i got asked by some people in the tso group, if I would consider doing a dynamic adaptive resource manager for mvs ... as part of attempting to improve tso's human factors characteristics. old email reference http://www.garlic.com/~lynn/2006v.html#email800310b in this post http://www.garlic.com/~lynn/2006v.html#23 Ranking of non-IBM mainframe builders? obviously this before I brought down the wrath of the MVS group when included reference to MVS MTBF of 15 minutes in the disk engineering & product test "testcell" environments ... recent ref http://www.garlic.com/~lynn/2009k.html#17 Bulletproof -- 40+yrs virtualization experience (since Jan68), online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
