I recommend using change in an editor anyway, so you keep control of the
process. YMMV

If you run into IBM or other macro problems, cross that bridge when you come
to it. IEABRCX can be "turned on" and "turned off" at various points in the
source code if necessary. No idea if it is available for VSE, but there is
nothing inherently "z/OS" about it -- pure hardware assembler, I believe. Or
you could roll your own.

Is there anything like the SYSSTATE ARCHLVL= macro in VSE? *Some* IBM macros
are responsive to it and will generate relative branches "natively" if you
are at a sufficient level.

Charles


-----Original Message-----
From: IBM Mainframe Assembler List [mailto:[email protected]]
On Behalf Of Dave Clark
Sent: Friday, April 1, 2022 12:32 PM
To: [email protected]
Subject: Re: Eliminating Base Registers (was: Inlining routines)

"IBM Mainframe Assembler List" <[email protected]> wrote on 
04/01/2022 02:51:13 PM:
> some brief comments:
> plus IBM macros have to be converted, there should be a macro to do that


        Thanks.  I did some reading at the link subsequently sent to this 
and I checked my system.  Apparently that macro (IEABRCX) was not made 
available to the z/VSE mainframe environment -- at least, not at my level. 
 We are 10 or 12 years behind on upgrades.   ;-)    We will be upgrading 
to the latest level in the next two months, though, and I can check again.


Sincerely,

Dave Clark
-- 
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio  45439  USA
(937) 294-5331





****************************************************************************
*****************
This email message and any attachments is for use only by the named 
addressee(s) and may contain confidential, privileged and/or proprietary 
information. If you have received this message in error, please 
immediately notify the sender and delete and destroy the message and all 
copies. All unauthorized direct or indirect use or disclosure of this 
message is strictly prohibited. No right to confidentiality or privilege 
is waived or lost by any error in transmission. 
****************************************************************************
*****************

Reply via email to