I forgot about ASMA215W because I suppress it. I don't think that message is valid on z/OS; but I don't know what other considerations there are, esp. for VSE & VM.
One of the nice things about EXTRN LARL is that there's no relocation to be done by Program Fetch. One of the less nice things is that every reference makes the Binder do a bit of fix-up. A common V-con would possibly make more sense if there are a lot of references (by lot, probably 100s at least). OTOH, LLILF/IILF of a V-con would have the disadvantages of both. sas On Fri, Jan 15, 2021 at 1:20 PM Gord Tomlin <[email protected]> wrote: > 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)." > > -- > > Regards, Gord Tomlin > Action Software International > (a division of Mazda Computer Corporation) > Tel: (905) 470-7113, Fax: (905) 470-6507 > Support: https://actionsoftware.com/support/ >
