re: http://www.garlic.com/~lynn/2015.html#84 a bit of hope? What was old is new again. http://www.garlic.com/~lynn/2015.html#85 a bit of hope? What was old is new again. http://www.garlic.com/~lynn/2015.html#86 a bit of hope? What was old is new again.
part of customer facing issue was that in the aftermath of FS failure in the mid-70s http://www.garlic.com/~lynn/submain.html#futuresys and the mad rush to get stuff back into the 370 product pipelines, the head of POK convinced corporate to kill-off vm370/cms product, shutdown the burlington mall development group and transfer all the people to POK, otherwise he wouldn't be able to ship MVS/XA on schedule in the 80s. They weren't going to tell burlington until the very last minute to try and minimize the number of people that might escape ... however the information leaked and lots of the people got away (one of the jokes was that the head of POK was one of the major contributors to DEC VAX/VMS). Endicott managed to save the vm370/cms product mission ... but had to reconstitute a development group from scratch ... and lots of the stuff that was in progress in burlington never resurfaced. also it put major damper on significant enhancements in customer releases. HONE had major enhancements for single-system-image, cluster operation with load-balancing and sharing across multiple multiprocessor systems, even being able to handle fall-over between geographically distributed complexes. A little of this finally shows shows up in customer release 30yrs later in 2009. HONE was able to accomplish these enhancements despite being under enormous pressure to move to MVS platform ... repeatedly they would be directed that they had to move to MVS ... and put all resources into the effort for a year or more ... only for it to eventually be declared a complete failure. http://www.garlic.com/~lynn/subtopic.html#hone They even tried blaming me for HONE inability to move to MVS platform ... because HONE was one of my long time internal customers for enhanced production operating systems (back to cp67 days). note that in the early 70s, CERN did a share mvs/tso - vm370/cms bakeoff report ... copies internally were classified "confidential - restricted" ... aka available on need to know basis only ... because it made a mockery of what POK was claiming internally (even tho it was freely available outside IBM). CERN & SLAC were long time production vm370 customers ... and the first webserver outside of europe/cern was on the slacvm system. http://www.slac.stanford.edu/history/earlyweb/history.shtml first web pages http://www.slac.stanford.edu/history/earlyweb/firstpages.shtml somewhat topic drift, slac did a bit-slice "168E" that implemented sufficient problem state to run 370 fortran programs ... they were used to do initial data reduction from sensors along the linear accelerator. this was then upgraded to 3081E and they were used at both SLAC and CERN for offline, initial data reduction as well as online compute farm. recent post in a.f.c. with other slac references: http://www.garlic.com/~lynn/2015.html#79 -- 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
