There is no "thus". I've dealt with plenty of LPA-resident code that
wasn't reentrant; in fact, I've dealt with LPA resident code that was
neither reentrant nor refreshable.
I don't doubt you but I am trying to figure out how this could occur.
The LPA is (by default) store protected so an LPA module can't modify
itself (there is an IPL option to make it store enabled).
A non-reentrant or non-refreshable module in a regular library implies
that a fresh copy will be loaded for each use. But being in LPA
implies that the same copy is always used, even by multiple callers.
So perhaps you can educate us on how an LPA module could be norent
and/or norefresh. Thanks
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.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
