On Thu, 24 Jul 2014 15:54:28 +0000, Tim Zielke wrote: > >I had a question about how z/OS handles physical memory for the same load >module that is loaded at different virtual addresses in different virtual >address spaces. > >For example, let's say on the same z/OS system I have the following: > >CICS region A that has load module B loaded at virtual address x'3F400010'. >CICS region B that has the same load module B loaded at virtual address >x'3D400020'. > >More than likely there will be some differences in that same load module that >has been loaded at different virtual addresses, since things like ADCONs and >VCONs will resolve to different virtual addresses when the load module is >brought into memory. However, there will probably be many virtual pages that >are also identical between the two modules, if nothing in that virtual page >needed to be adjusted by the loader. > If each ADCON is made relative to a location in the module (paired relocation), the entire module is location-independent and can be mapped to any location in various address spaces. I know of no z/OS facility to exploit such a design for general programs.
I understand the convention has been used for transient areas. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
