On Mon, 16 Jul 2018 15:25:43 +0000, Seymour J Metz wrote: >Storage keys were available all the way back to OS/360. > Would that have required two storage keys for each job, one for writable and one for REFR?
Or, REFR modules could be loaded in key 0, but that might compromise privacy (with no threat to integrity). If the OS chooses to remove a page to free the storage, I assume that if the page is valid in a page data set and has not been modified there's no need to write it out; just free it. And if the page is in a REFR module, it's an immediate candidate for replacement; no need even to check the modified flag. What if the module is marked REFR but the modified flag has been set? Shouldn't an error be reported? At the very least, the user should be given control of REFRPROT via an option on the JOB statement. >________________________________________ >From: Peter Relson >Sent: Sunday, July 15, 2018 8:54 PM > ><snip> > ... How much extra would >it have cost to load user programs as well as system programs into >write-protected storage? ></snip> > >Page protection did not exist at the time that this logic was introduced. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
