In <listserv%200911181224379387.0...@bama.ua.edu>, on 11/18/2009
at 12:24 PM, Paul Gilmartin <paulgboul...@aim.com> said:
>My understanding is that is what REFR was intended to mean. (Etym.: If a
>memory page physically failed, that page could be REFReshed from a
>pristine copy, perhaps in a page data set.)
The original use of REFR was for the Machine Check Handler in OS/360,
which had no paging. It used a data set called SYS1.ASRLIB to back up
refreshable csects in the nucleus. It reloaded refreshable SVC routines
into the SVC transient area from SYS1.SVCLIB.
>I agree with your analysis: REFR and RENT should be independent.
Yes, at the system level. But IMHO we should be writing code that is both
refreshable and reentrant.
>One can contrive scenarios to populate each quadrant of the truth
>table.
And IBM did, more often than I liked. However, such programs are best used
as examples of what the concepts are, not as code to be moved into
production.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
