Jim Mulder wrote:
IIUC, z/OS UNIX fork processing uses the OC instruction, while in PSW
key zero, to WRITE on EVERY PAGE of EVERY MODULE in the private area of
the address space!
That's a bit of an exageration. Every page of every program object
which is eligible for deferred page mode loading would be more accurate
(not sure whether this includes ones whose pages have already all been
loaded or not).
That makes sense. (I wish the APAR or even the description in my ETR had
made that clear.)
Given how long z/OS 1.9 has been out, and that NOPACK,NOPRIME is the
_default_ for binding of program objects, I would have thought *someone*
would have seen this before me. Am I the only one in the world running
with REFRPROT, sizable JPA modules loaded from PDSE, and using z/OS UNIX?
I've used the CsvRentProtect DIAG trap for many years (as you know)
under older operating system releases and never ran into this before.
The same (E)JES module(s) were certainly eligible for page protection
under that scheme. Any idea what's changed in z/OS 1.9?
Anyway, most likely, the OC will be changing to be a TM with a mask
of x'00'.
So, the need is simply to finish loading the module and not to set the
"changed" bit on every page. That makes me feel a little better about
what's being done. I think. :-\
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
