I stand corrected. I missed the OP's specification (in the subject as well as in the text) of loading EXTERNAL addresses via IILF. EXTERNAL relative adcons do indeed require GOFF.
My uses of LARL to date have all been for in-the-current-CSECT locations. Peter -----Original Message----- From: IBM Mainframe Assembler List <[email protected]> On Behalf Of Gord Tomlin Sent: Friday, January 15, 2021 1:20 PM To: [email protected] Subject: Re: A faster replacement for L R15,=A(EXTRN) On 2021-01-15 11:55 AM, Gord Tomlin wrote: > It's been possible to achieve the same result with LARL for many years > (requires the use of the GOFF option in the HLASM parameters). Since I got called out on the above, I ran some tests to refresh my memory. The following code: EXTRN FOO LARL R15,FOO assembles cleanly with the GOFF option specified, but without GOFF the following warning message is issued: ** ASMA215W Relative Immediate external relocation in NOGOFF object text - FOO Regardless of whether GOFF is specified on the assembly, the output object module can be used to create a load module in a PDS. Revised: "It's been possible to achieve the same result with LARL for many years (a warning message will be issued if GOFF is not specified in the HLASM parameters)." -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
