edgould1...@comcast.net (Ed Gould) writes: > Lynn: > > Good Point. > I believe ISPF (formally SPF) was written at a customer site (MY > faulty memory says it was PLAYTEX but I could be wrong). > Another (less known was PCF) also I *THINK* SDSF was the same.
re: http://www.garlic.com/~lynn/2014h.html#99 TSO Test does not support 65-bit debugging? folklore is that person responsible for much of TSO ... came out of MIT with some CTSS & MULTICS background. Of course, at the science center ... cp67/cms (later vm370/cms) had much more CTSS direct lineage/content. some past posts http://www.garlic.com/~lynn/subtopic.html#545tech later starting in 1979 with the rise of huge number of vm/4300s ... in the early 80s, the company declared vm370/cms as the corporate strategic interactive product. The TSO product administrator then contacted me about porting my vm370 scheduler to MVS ... but I declined since to fix TSO for interactive computing would require significantly more than just fixing the MVS scheduler. old email http://www.garlic.com/~lynn/2006b.html#email800310 As an aside, I had originally done dynamic adaptive resource management back in the 60s as undergraduate ... and IBM picked up and shipped first with cp67/cms. some past posts http://www.garlic.com/~lynn/subtopic.html#fairshare note that mainstream IBM (especially POK) had hard time adapting to rules regarding charging for software (monthly lease had to cover costs) ... some of this possibly outgrowth of Brook's "Mythical Man Month". http://en.wikipedia.org/wiki/The_Mythical_Man-Month cp67/cms and later vm370/cms (before being moved out of mass) had significantly lower cost infrastructure. One of the first was eventually announcing JES2 networking as joint product with vm370 vnet (being able to do combined revenue to cover combined costs) ... this even when some of the original JES2 networking code had carried the letters "TUCC" out in cols 68-71 (carried over from HASP days). the folklore is that then happened in the 80s with ISPF but even more creative bookkeeping. They combined ISPF and VM370 performance tools in the same "development" group ... even tho they weren't joint products. The had 200 people on ISPF group and stablized vm370 performance tools with just 3people so that the income of vm370 performance tools effectively underwrites ISPF. The story for graphical netview is straight-out of "truth is stranger than fiction" ... past post http://www.garlic.com/~lynn/2013d.html#61 What Makes an Architecture Bizarre? -- 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
