There are several issues here. First, if you do a BLDL then there's no reason to do a trial LOAD; the size is in the DE.
Second, RENT controls the subpool, but since you're doing a directed load, that doesn't matter. Third, the behavior o RENT and REFR depend on whether you use the Linkage Editor or the Binder and on what you have in PARMLIB, but, again, you're doing a directed LOAD. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Tony Harminc <[email protected]> Sent: Wednesday, August 7, 2019 6:55 PM To: [email protected] Subject: LOADing a module into common storage Roughly forever we've loaded modules into 24- or 31-bit CSA by first LOADing the module normally into private storage, obtaining the actual length from the LOAD, DELETEing the module, getting the necessary CSA storage, and finally using LOAD with ADDR=. This works fine, but seems unduly complicated. We can't use GLOBAL=YES because the module will be gone at EOM, at best. We also need to store into the module right after loading it, and even if there was an EOM=NEVER or the like to say not to ever delete the module, I'm not sure any store into it would be remembered (if RENT is effectively treated as REFR). So... Just wondering if there's a Modern method of doing this that I've missed. We just want the code in common storage; we don't need its name to be made known via a CDE. Thanks! Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
