Peter Hunkeler wrote:
It primarily has to do with the module attributes (is it reentrant?) and
the APF authorization of the job step.
I hate to correct you, but ISTR it is RENT plus loaded from an authorized
library, no matter whether the step is actually running APF authorized or not.
David: Does you HFS module have the "a" extended attribute set, and is it really required?
--
Peter Hunkeler
Loading from the HFS seems to prefer to load RENT modules in read-only
memory; without the "a" attribute.
By default, it seems, the c99/cc/etc.. drivers set things up so that
REUSE=RENT
is specified (or perhaps that's the binder default when writing an HFS
program
object?)
And - HFS loading seems to really like putting things in read-only memory.
That's way, to debug anything with dbx, you have to specify the environment
variable (_BPX_PTRACE_ATTACH=yes) to get the programs loaded in
writable storage so dbx can set break-pts.
But - when you programatically invoke BPX1LOD; there is no way to honor
the environment variable... I suppose the exec family of functions can
examine the environment variable (since they have it) and somehow load
the module appropriately, but BPX1LOD has no similar function.
- Dave R. -
--
[email protected] Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
