I was thinking of similar craziness, but I'd replace the actual HSC init
program with my own. Then like you implied, that code would dynamically
allocate the DSN and do a LOAD DCB= to get the real module into memory.
Then deallocate, restore registers (to what they were at entry),
branch, and "The OS will never know" (famous last words).
This method would also mean following a convention I've argued for over
many years: "Never use version numbers in production load library names".
Ok! Now back to the real world and just go update the doc :)
Mark Jacobs - Listserv wrote:
Here's a wild thought. Create your own dummy subsystem with its own
initialization routine that gets executed before any of the subsystems
you're concerned about. This initialization routine can load the other
modules into CSA, or even copy from one library to a linklist library.
We have an installation defined dummy subsystem that uses the
initialization routine to define system level name/token pairs during
the IPL process.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
