Where should the type information be: in tags and descriptors 453
Where should the type information be: in tags and descriptors 456
Just a data point about what was known at the time. After the May 17th cancellation of the KL10 followon we had a session with beer and pizza; this was the friday...
of course, endicott complained long & loud ... and finally it was decided that endicott could pick up responsibility for vm370 ... however all the burlington people still had to move to POK to work on the vmtool (some claim that mvs-xa couldn't meet its schedule w-o having fully populated vmtool effort supporting them).
Where should the type information be: in tags and descriptors 454
The "mongolian horde" technique (aka "army of golems"). If you can make it work at all, the best quality you can hope for...
Where should the type information be: in tags and descriptors 457
That's correct, and at the same time it is correct that ăBell wasn't allowed to sell it to just anyone╚ -- you were allowed to buy what was essentially an evaluation (fully unsupported, as-is) license...
endicott had done ecps (vm370 microcode performance buttist)
there was actually a swipe taken out shipping every 370-148 from the factory with vm370 prebuilt on the machine. The objective was to have it integrated into normal system operation (akin to all the LPAR stuff you seen on the big mainframe iron ... and its proliferation into many other hardware product lines). The holly grail was to have it so integrated there wouldn't be any requirement for customer system support people. In the 148 time-frame that was still not quite there ... and besides the official corporate position had constantly been that the next release of vm370 was the last (and so corporate vetoed any escalation of the penetration of vm370 into the market).
Endicott took another run at vm370 as part of the basic operation of every machine with the 4341 (akin wanting to do something along the lines of current day lpars and virtualization). By that time, they had started to build up some of their own inhouse expertise ... and the holy grail was still being able to have vm370 on every 4341 and not require any customer support people for it. Given that you force a lot of defaults ... they were coming within reach of the goal. However, they still were facing the constant corporate veto of any such escalation of vm370 use (although customers ordered huge numbers of 4341s and installed vm370 on them ... endicott wasn't allowed to take the next step and make it transparent part of every machine operation).
this is one of the things that customer feedback (and SHARE reports) constantly hit endicott on ... that typical 4341 installation required a lot more customer system support resources than the typical vax-vms installation (it wasn't just a matter of turn-key, out-of-the-box operation).
recent related posts
Alt Folklore Computers Newsgroups