[email protected] (Tony Harminc) writes: > These were re-integrated only with the OS/390 bundling. I doubt any > one present -- even Lynn Wheeler -- knows all the politics behind all > these changes.
re: http://www.garlic.com/~lynn/2014d.html#54 Difference between MVS and z / OS systems OS/390 ... 1995 after we had left http://en.wikipedia.org/?title=OS/390 OS/390 was introduced in late 1995 in an effort, led by the late Randy Stelman, to simplify the packaging and ordering for the key, entitled elements needed to complete a fully functional MVS operating system package. ... snip ... marketing, service, availability, withdrawal dates; z/OS, z/OS.e, OS/390, MVS/ESA (1st OS/390 available 29Mar1996) http://www-03.ibm.com/systems/z/os/zos/support/zos_eos_dates.html recent post leading up to us being gone by aug1992 (in the wake of cluster scaleup being transferred and being told we couldn't work on anything with more than four processors) http://www.garlic.com/~lynn/2014d.html#52 the company had gone in the red and there was some work that was going to break up the company into the 13 "baby blues". leading up to leaving we saw some periodic email from the POK region about would the last person to leave POK please turn out the lights. The disk division was furthest along as ADSTAR. I've mentioned before that disk division was predicting the demise of disk division with data fleeing the datacenters and drop in disk sales, blamed on the communication group that had stranglehold on the datacenter ... some past posts http://www.garlic.com/~lynn/subnetwork.html#terminal the executive in charge of software at ADSTAR was involved in various work arounds to the communication group road blocks (fighting off client/server and distributed computing) ... paying for posix support in MVS and funding startups doing various products (that communication group wouldn't let him do inside IBM) ... and he would call us to consult (up until the time we were gone). 28dec1992 baby blue reorganizations in preparation for breakup http://web.archive.org/web/20101120231857/http://www.time.com/time/magazine/article/0,9171,977353,00.html we move on in Aug1992, doing some work on non-mainframe cluster and DBMS for non-homogeneous data ... working well for things like taxonomies and ontologies, like UMLS http://www.nlm.nih.gov/research/umls/ and works better for 3-value logic (than strict RDBMS/SQL) http://www.garlic.com/~lynn/2003g.html#40 past posts about original releational/sql System/R http://www.garlic.com/~lynn/submain.html#systemr we did get a call if we would consult with inventoring corporate inter-divisional MOUs as part of the breakup (i.e. lots of divisional relationships would have to be explicitly turned into contracts as part of breakup, like one division piggy-backing off a supplier's contract with another division). However, before we start work on the MOU inventory, the board brings in Gerstner to reverse the breakup and resurrect the company. conjecture about os/390 was help reduce the enormous skills and resources required for the care&feeding of MVS system. I've commented before about the large explosion in 4300 sales during the late 70s and first half of the 80s ... sort of the leading edge of the distributed computing tsunami ... customers ordering hundreds at a time for vm/4300 going out in departmental areas. Part of the issue was high-end disk was (CKD) 3380 ... but the entry & midrange disks were FBA (3310, 3370) which MVS continues to not support to this day (even though real CKD disks haven't been manufactured for decades). Eventually as some concession to possibility MVS playing in that exploding mid-range distributed computing market, they come out with 3375 (CKD simulated on 3370 FBA). However, that didn't address the enormous skills and resources that would have been required to support several hundred systems. old email mentioning 4300s http://www.garlic.com/~lynn/lhwemail.html#43xx -- 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
