The midseventies SHARE survey 66
 |
there was a 360 DAT box available on the 360-65 ... it was called the 360-67. DAT-virtual memory was really expensive in 360 technology and tended to consume larger...
i have some recollection of being in pok machine room (705-706?) 3rd shift and working around ludlow(?) on a 360-67 ... he was building the aos2 (prototype for os-vs2 ... svs) ... basically taking MVT and with a little stub code to set-up virtual memory tables and handle page-faults ... and wiring CCWTRANS (taken from CP67) onto the side of MVT IOS to handle all the channel program translation.
I'm sure one reason for those 360s hanging around so long when faster-better-cheaper alternatives were available was a result...
the detailed mvs history page URL that I had recently went 403.
but this appears to be the same-similar
some number of notes about the above
... it refers to os-vs1 having single virtual memory and os-vs2 having multiple virtual memories.
os-vs1 was essentially os-360 mft with single virtual memory crafted on the side and os-vs2 was initially "SVS" ... os-360 mvt with single virtual memory crafted on the side.
OS-VS2 initial release was called SVS for single virtual storage and was later enhanced to MVS for multiple virtual storage.
OS-VS2 release 3 ... i believe was the first MVS ...
starting with unbundling, june 23rd, 1968 plus 1 ... application software started being charged for ... but the operating system continued to be "bundled" (free) with the hardware.
1977 is pretty early for such user groups, and give a window onto another era. In retrospect...
with the appearance of clone mainframes there was push to start charging for operating system.
I got to be the original guinee pig for this with the resource manager
and spend six months with the business and planning people working out the guidelines for charging for operating system stuff. The revised rules was that if the software was needed for direct hardware support (aka device drivers, etc), then it was still bundled ... but all other operating stuff (like performance management) or the resource manager could be priced.
This led to a problem when they went to put-out SMP support the next release. I had all sorts of guodies in the resource manager software ... including a bunch of stuff that SMP was dependent on. The business rules had SMP support being "free" ... since it was directly needed for hardware support ... however it wouldn't be quite following the rules if there was free software that had a pre-requisite of priced software. The solution was to take about 80percent of the code in the original resource manager and move it into the "base" free operating system.
--