re: http://www.garlic.com/~lynn/2009i.html#26 Why are z/OS people reluctant to use z/OS UNIX? http://www.garlic.com/~lynn/2009i.html#35 SEs & History Lessons
Early on, the HONE cp67 systems, deployed csc/vm cp67 (large body internal/csc changes) with a subset of the "H" system updates. Before 370 virtual memory was announced there was a joint distributed development project between Cambridge Science Center and Endicott (leveraging network link) to provide 370 virtual machines under cp67 (running on 360/67). This required a cp67 virtual machine option to specify 370 virtual machine (rather than 360 virtual machine). The full set of "H" updates provided full 370 virtual memory architecture support ... allowing development and test of virtual memory operating systems prior to availabiilty of 370 virtual memory hardware. A subset of these changes were built for HONE, that only provided the announced 370 features (add-ons to 360, w/o unannounced virtual memory support) ... allowing branch office people to test 370 "versions" of (non-virtual memory) operating systems on HONE. However, (cms/apl) APL "AIDS" applications for sales & marketing support started being deployed on HONE ... eventually crowding out all other activity. By the time HONE migrated from cp67(H) to vm370 ... all of the activity with virtual operating systems had evaporated. Extract from some number of reference cards, including (HONE APL) '73 AIDS Reference summary card http://www.garlic.com/~lynn/2002j.html#3 HONE, Aid, misc Now this is reference about some amount of SMP activity ... including a project for doing (real) 16-way SMP in the 70s ... that was going great guns until somebody leaked to the head of POK that it would be a decade or two before the favorite son operating system supported 16-way SMP http://www.garlic.com/~lynn/2009i.html#32 There standard work on vm370 SMP product support ... but HONE with its computational intensive (APL) workload needed to upgrade their 168-3 to multiple processors as soon as possible ... so I did a flavor of my VM370 distribution with SMP support before there was a vm370 product release support. With the consolidation of US HONE datacenters in the bayarea ... they had a large loosely-coupled 168-3 configurations (with custom single-system-image support) ... which were then upgraded to 168APs (aka dasd farm with "8-tail" support ... allowing up to eight 168APs, 16 processors, having single-system image). as mentioned in the above referenced post about ("real") 16-way SMP ... the POK favorite son operating system managed to convince the corporation to kill vm370 product (because they needed all the vm370 developers to be able to make the mvs/xa delivery scheduled). Endicott eventually managed to save the product mission, but they had to reconstitute a development group essentially from scratch. The various corporate repeated attempts to kill vm370 also created a lot of problems at HONE. Starting about the time of HONE datacenter consolidation in the bayarea ... there was an approx. two year cycle; 1) somebody from branch office would get promoted to head up the organization that contained HONE, 2) they would eventually get a presentation and realize to their great dismay that HONE was a vm370 system, not the favorite son operating system, 3) they would mandate that HONE be converted to favorite son operating system, 4) everybody would stop what they were doing and diligently work on attempting a conversion, 5) the conversion would eventually fail, 6) things would almost return to normal, 6) but it was almost time to get another new executive and the cycle would be repeated. By this time, essentially the same vsapl code ran on vm370 and the favorite son opeating system ... so in theory it should have been possible ... however there is the old saying about "in theory there is no difference between theory and practice, *but* ..." In the early 80s, there was Earthquake concern about the bayarea and so a HONE datacenter was replicated first in Dallas and then another in Boulder, with single-system-image, load-balancing, and fall-over (between three sites). Starting in the late 70s ... in attempt to enable some branch office "hands-on" ... there were 370/148 (moving to 4341) "DEMO" vm370 systems installed for each of the (US) regions ... some past posts with details: http://www.garlic.com/~lynn/2002j.html#4 HONE, ****, misc http://www.garlic.com/~lynn/2002j.html#7 HONE, ****, misc misc. past posts mentioning cp67-h effort ... along with cp67-i ... cp67 system modified to run with 370 virtual memory architecture instead of 360/67 virtual memory architecture. cp67-i systems ran regularly in cp67-h virtual machines for a year before the first 370 virtual memory hardware became available ... then cp67-i was the main system running on such hardware for quite a period. http://www.garlic.com/~lynn/2002j.html#0 HONE was .. Hercules and System/390 - do we need it? http://www.garlic.com/~lynn/2004b.html#31 determining memory size http://www.garlic.com/~lynn/2004h.html#27 Vintage computers are better than modern crap ! http://www.garlic.com/~lynn/2004p.html#50 IBM 3614 and 3624 ATM's http://www.garlic.com/~lynn/2005c.html#59 intel's Vanderpool and virtualization in general http://www.garlic.com/~lynn/2005g.html#17 DOS/360: Forty years http://www.garlic.com/~lynn/2005h.html#18 Exceptions at basic block boundaries http://www.garlic.com/~lynn/2005i.html#39 Behavior in undefined areas? http://www.garlic.com/~lynn/2005j.html#50 virtual 360/67 support in cp67 http://www.garlic.com/~lynn/2005p.html#27 What ever happened to Tandem and NonStop OS ? http://www.garlic.com/~lynn/2006.html#38 Is VIO mandatory? http://www.garlic.com/~lynn/2006e.html#7 About TLB in lower-level caches http://www.garlic.com/~lynn/2006f.html#5 3380-3390 Conversion - DISAPPOINTMENT http://www.garlic.com/~lynn/2006l.html#21 Virtual Virtualizers http://www.garlic.com/~lynn/2006m.html#26 Mainframe Limericks http://www.garlic.com/~lynn/2006o.html#19 Source maintenance was Re: SEQUENCE NUMBERS http://www.garlic.com/~lynn/2006q.html#1 Materiel and graft http://www.garlic.com/~lynn/2006q.html#45 Was FORTRAN buggy? http://www.garlic.com/~lynn/2006q.html#49 Was FORTRAN buggy? http://www.garlic.com/~lynn/2006w.html#3 IBM sues maker of Intel-based Mainframe clones http://www.garlic.com/~lynn/2007b.html#20 How many 36-bit Unix ports in the old days? http://www.garlic.com/~lynn/2007f.html#12 FBA rant http://www.garlic.com/~lynn/2007i.html#16 when was MMU virtualization first considered practical? http://www.garlic.com/~lynn/2007p.html#74 GETMAIN/FREEMAIN and virtual storage backing up http://www.garlic.com/~lynn/2007q.html#23 GETMAIN/FREEMAIN and virtual storage backing up http://www.garlic.com/~lynn/2008i.html#68 EXCP access methos http://www.garlic.com/~lynn/2008i.html#69 EXCP access methos -- 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
