<snip> Problem solved by LOAD . . . GLOBAL=(YES,F) macro / parameter. Another sidebar consideration: When LOADing a module into common storage, the module cannot be linked with PAGE or an ABEND 306-10 is issued. z/OS is probably trying to conserve space. </snip>
If you truly wanted SSWITCH=NO then, yes, the target needs to be in common storage (unless you have limited the invoker to one specific address space and did the LOAD from there). Unless you are disabling in some way there is no need for having the module page-fixed (as "F" asks). Much more important, you very likely have introduced a system integrity error with use of LOAD with GLOBAL=YES, unless the address space doing the load can never terminate without the system wait-stating. The exposure is the time when the LOADing address space terminates. At that point, this storage is freed. And that means that it could then be re-allocated. Anything within the code at the time of the termination, but undispatched across that window, will get redispatched running whatever happens to be there now. That is not OK. Your valid choices for putting a module in storage after IPL (before IPL you could just put it into LPA) are: Dynamic LPA Load with ADDR In neither case would it be OK ever to free the module storage. Dynamic LPA is preferred because it helps with diagnosis (since the system has associated a module name with that storage). 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
