External relative addressing does work, yet HLASM still warns about this, e.g. "ASMA215W Relative Immediate external relocation in NOGOFF object text - ESTAE_RESUME "
Is there any cure for this? My production build process doesn't tolerate any return code that isn't a multiple of 0. I haven't tried it, but I'd guess that if you tried to run such a module through the old linkage-editor that it would produce a suitable error message. So there shouldn't be any need for the HLASM warning. sas On Mon, Apr 8, 2013 at 1:42 PM, John Ehrman <[email protected]> wrote: > >And only if the target is relatively addressable. I.e. In the same section > >or object. > > >sas (phone) > >>On Apr 5, 2013 7:21 PM, "John Ehrman" <[email protected]> wrote: > >> You can use LARL to replace LA only if the target is at an even address. > >> John Ehrman > > This may not be relevant to the original question, but you CAN declare an > external symbol in the operand field of a relative-immediate instruction. > > The object module encodes the "relative-adcon" type and the binder resolves > the external reference (again assuming the target is at an even address). > > John Ehrman > -- sas
