I thought perhaps I didn't get the question because the answer seemed so obvious to me. I thought I must be missing something.
I faced this problem in 2010. My first tentative approach was an ADDR= load, solving the size problem with HLASM cleverness. Then I discovered CSVDYLPA. I had no idea whether it was new or old, but it was available for every release of z/OS I had to support. It has worked flawlessly from (my) day one. I can't imagine doing this any other way at this point (unless for some reason you need to support OS/390 or perhaps very early z/OS). Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Relson Sent: Thursday, August 8, 2019 7:35 AM To: [email protected] Subject: Re: LOADing a module into common storage Roughly forever, the way to do this has not been to do two LOADs. It had been to do a BLDL, extract the length information (and the RMODE information and the Page boundary information) from the directory entry, do a suitable storage obtain, then do a LOAD with ADDR (or even, more recently, LOAD with ADDR64). I wrote "had been" because dynamic LPA (CSVDYLPA macro) has been available for 20+ years now which accomplishes the function and also makes the named module knowable to others (including diagnostic tooling). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
