Oppolzer - Informatik / Blog

You did use the

        SYSSTATE ARCHLVL=2
        SYSSTATE OSREL=ZOSV1R8

calls, did you?

Maybe OSREL=ZOSV1R7 in your case ...

For me, most of the issues with IBM macros disappeared, when I used this calls
...

I had some other issues with home grown macros which I couldn't fix because the
responsibility was in another department (sigh!), so I fixed this by
establishing temporary base registers around the macro call... or I moved the
macro call to another place, where I have base register addressibility (the
first 4 k of a subroutine).

Kind regards

Bernd



Am 19.04.2014 20:35, schrieb E.J.:
> hello
>
> I know this topic has been discussed before..
> Im on a Z/OS 1.7 system with HLASM R5.0
> ...
> Im trying to maintain the concept of "Baseless Code" in some programs,
> I keep running into some macros on Z/os 1.7 that use  BAL R15,*+20
> .
> .
> And as such i receive message
> ** ASMA034E Operand *+20 beyond active USING range by 185 bytes
> ** ASMA435I Record 124 in SYS1.MACLIB(IHBINNRB) on volume: S7RES1
> .
> .
> I could move the routine to another location in this module, and that
> would avoid the ASMA034E. Is there a recommended technique to use where
> I could convert the BAL instruction in the macro to another branch instruction ?
> .
> .
> P.
>