In <[EMAIL PROTECTED]>, on 12/15/2006
at 01:30 PM, Bruce Black <[EMAIL PROTECTED]> said:
>I don't doubt you but I am trying to figure out how this could occur.
Because there was an IPL parameter that allowed it. Had I been allowed
to I would have killed the infamous thing.
>A non-reentrant or non-refreshable module in a regular library
>implies that a fresh copy will be loaded for each use.
No. You get a fresh copy if it is not linked as REUS. You get
serialized if you LINK to a module with REUS but not RENT. Program
Management (née Contents Supervision) pays no attention to the REFR
flag.
>So perhaps you can educate us on how an LPA module could be norent
>and/or norefresh.
By allowing it in your IEASYSxx and by not serializing the resources
you use. BTW, have they finally made MLPA write protect mandatory in
1.8?
--
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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
