misc. more about vm370 release 3 ... from Melinda's history
http://www.princeton.edu/~melinda
from her history:
Also in February, 1976, Release 3 of VM/370 became available, including
VMCF and support for 3350s and the new ECPS microcode. Edgar (the
``Display Editing System''), a program product full-screen editor
written by Bob Carroll, also came out in 1976. Edgar was the first
full-screen editor IBM made available to customers, although customers
had previously written and distributed full-screen editors themselves,
and Lynn Wheeler and Ed Hendricks had both written full-screen editors
for 2250s under CMS-67.
... snip ...
it doesn't mention DCSS being part of release 3.
... but it does mention ECPS which I worked on in conjunction with
Endicott. some old detail on studies deciding what to make part of ECPS
http://www.garlic.com/~lynn/94.html#21 370 ECPS VM microcode asssit
except, my quick & dirty recollection was that ECPS support wasn't
shipped until Release 3 PLC4
and then, of course, my resource manager release was 11May76. misc.
collected past posts on various aspects of some of the stuff that
shipped in the resource manager
http://www.garlic.com/~lynn/subtopic.html#fairshare
http://www.garlic.com/~lynn/subtopic.html#wsclock
The same person responsible for VMCF had also redone how shared segments
were protected ... which was also part of VM370 release 3. The issue was
that the decision to ship the alternative shared segment protection was
based on pre-release 3 CMS with only single shared segment with 16
shared pages.
part of the stuff that was included with the DCSS extreme subset of my
virtual memory management
http://www.garlic.com/~lynn/2006m.html#53 DCSS
was additional CMS code for a second shared CMS segment (and 16 more
shared pages). The release 3 change for shared segment/page protection
drastically increased the overhead per shared page which was offset by
enabling the use of VMA for CMS execution. However, the trade-off
decision had been based on a single CMS shared segment (and only 16
shared pages). The new shared segment protection (and enabling VMA use
for CMS virtual machines) shipped at the same time the additional shared
segment facilities shipped (typically doubling the number of shared
pages) ... invalidating the original trade-off analysis.
and repeat (from previous post) of collected posts on cms page mapped
filesystem
http://www.garlic.com/~lynn/subtopic.html#mmap
and other collected posts about effort to make cms executable code
location independent (as part of virtual memory management work)
http://www.garlic.com/~lynn/subtopic.html#adcon
