The rules about which subpool to place a reentrant module depend on APF authorization.
My guess is that -- the module claims to be reentrant, but isn't (and yes I know that it is conceivable to have a reentrant module that stores into itself, but the rules don't care about that) -- when run out of a STEPLIB comes from a not-authorized concatenation so lands in SP251 (task key) -- when run out of the LNKLST is treated as coming from an authorized concatenation (because the system parameter LNKAUTH=LNKLST is in effect; that is the default) and lands in SP252 (key 0) so blows up on the "store into itself". Some choices: -- change the module not to be linkedited as reentrant -- don't run it as part of the LNKLST -- run with LNKAUTH=APFTAB (noting that this option has higher overhead than LNKAUTH=LNKLST in order to determine the APF state of the request, but is more protective) Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
