On Fri, 7 Dec 2012 11:16:45 +0100, Bernd Oppolzer wrote: > >As long as the tables are not bigger than 2 GB, I would use relative adresses >(related to the table origin) instead. This way 4 byte relative addresses are >sufficient, and you have to store the table origin only once and you need >simply add the table origin every time when you follow such a relative >address. > And these may sometimes be generated in HLASM with constructs such as "A(TARGET-*)" which contains an abolute address expression; no RLDs are necessary. But if "TARGET" and "*" reside in different CSECTS, will HLASM accommodate the doubly-relocatable construct? I think so, but relocation of a module above the bar may create transitory out-of-range values. Should these be reported as errors? The final result is valid when treated modulo 2^32.
-- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
