Re: Modernizing code, was RE: [ASSEMBLER-LIST] GETMAIN/FREEMAIN vs. STORAGE OBTAIN/RELEASE

2010-11-02 Thread Steve Comstock
On 10/29/2010 7:45 AM, Beate Kawelke wrote: Dear all, thanks for the good advice. I forgot to mention the background of my question: I'm currently looking into "modernizing" 20-year-old code (some of which is by me, so I feel a bit old, too). While I have to add some more functions, I will al

Re: Modernizing code

2010-10-30 Thread Peter Relson
> Changed ICM to LT/L if possible Be sure that you know your target machine. z/OS runs on all z/Architecture machines, not all of which support LT (and some customers still have such machines). Peter Relson z/OS Core Technology Design

Re: Modernizing code

2010-10-29 Thread Edward Jaffe
On 10/29/2010 6:58 AM, Beate Kawelke wrote: Oh, we have that already: COPYIEABRC does this automagically ;-) Or use the IEABRCX macro. It allows you to selectively enable/disable/push/pop the conversion. We do this only around "stubborn" IBM macros. -- Edward E Jaffe Phoenix Software Int

Re: Modernizing code

2010-10-29 Thread McKown, John
> -Original Message- > From: IBM Mainframe Assembler List > [mailto:assembler-l...@listserv.uga.edu] On Behalf Of Potts, Michael > Sent: Friday, October 29, 2010 9:38 AM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: Modernizing code > > This isn't st

Re: Modernizing code

2010-10-29 Thread Potts, Michael
RC12 -Original Message- From: IBM Mainframe Assembler List [mailto:assembler-l...@listserv.uga.edu] On Behalf Of McKown, John Sent: Friday, October 29, 2010 10:05 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Modernizing code The one place where I have found that I cannot replace a branch

Re: Modernizing code, was RE: [ASSEMBLER-LIST] GETMAIN/FREEMAIN vs. STORAGE OBTAIN/RELEASE

2010-10-29 Thread Kirk Talman
May I suggest MACRO , &LABEL SHI &R,&V &LABEL AHI &R,-(&V) MEND , IBM Mainframe Assembler List wrote on 10/29/2010 09:45:51 AM: > From: Beate Kawelke > - Changed xH to xHI if possible (e.g. LH Rx,=Y(4) to LHI Rx,4) > The first two are simply a change from one state

Re: Modernizing code

2010-10-29 Thread McKown, John
Sent: Friday, October 29, 2010 8:55 AM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: Modernizing code > > Another quick win is to replace branches with jumps (B to J, BE to JE, > and so on). It will take more work to replace them in macros > and figure > out ways to handl

Re: Modernizing code, was RE: [ASSEMBLER-LIST] GETMAIN/FREEMAIN vs. STORAGE OBTAIN/RELEASE

2010-10-29 Thread Paul Gilmartin
On Oct 29, 2010, at 07:45, Beate Kawelke wrote: > > The first two are simply a change from one statement into another - no big > deal (except that there is no SHI, so I've got to use AHI ...,-nn). > With a special tweak for "SH =H'-32768'"? This can be much obscured by the use of EQUated or SETA

Re: Modernizing code

2010-10-29 Thread Beate Kawelke
A.EDU > Subject: Re: [ASSEMBLER-LIST] Modernizing code > > Another quick win is to replace branches with jumps (B to J, > BE to JE, and so on). It will take more work to replace them > in macros and figure out ways to handle branches into branch > tables. It seems like you'

Re: Modernizing code

2010-10-29 Thread Potts, Michael
Another quick win is to replace branches with jumps (B to J, BE to JE, and so on). It will take more work to replace them in macros and figure out ways to handle branches into branch tables. It seems like you're well on your way to removing base registers for addressing code! -Original Message

Modernizing code, was RE: [ASSEMBLER-LIST] GETMAIN/FREEMAIN vs. STORAGE OBTAIN/RELEASE

2010-10-29 Thread Beate Kawelke
Dear all, thanks for the good advice. I forgot to mention the background of my question: I'm currently looking into "modernizing" 20-year-old code (some of which is by me, so I feel a bit old, too). While I have to add some more functions, I will also take the opportunity to improve the code.