IPM and SPM work fine for this. We use it all the time. Sent from my iPad
> On May 5, 2018, at 11:23 AM, Pieter Wiid <pw...@mweb.co.za> wrote: > > Will only work in AMODE 24. > IPM is better > > -----Original Message----- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] > On Behalf Of robi...@dodo.com.au > Sent: 05 May 2018 13:31 > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: storing and restoring condition code > > BALR with second operand 0 will give you the condition code. > > ----- Original Message ----- > From: "IBM Mainframe Assembler List" <ASSEMBLER-LIST@LISTSERV.UGA.EDU> > Sent:Sat, 5 May 2018 06:22:32 -0400 > > In 20+ years of heavy assembler coding, I never needed to store and restore > the condition code, until now. > > I have some 'standard' macros I use that allow me to turn some debug code on > and off during testing. Yesterday, I was using some of this code and had a > program failure due to the fact that it uses code that sets > > the condition code. The program code has many places where a BALR function > returns not a R15 value, but instead returns a condition code setting. > > So, what methods do some of you use that will equate to a save and restore a > condition code? My code will be in a macro, so it can be a little > 'dicey'/'unreadable' if needed. > > -- > Tony Thigpen > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus
