Only in 24-bit mode. If you do a macro, make it mode and architecture sensitive. I used to do something similar for code that could be assembler either for S/360 or for S/370; the macros only used, e.g., ICM, if they were assembling the 370 version..
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List <ASSEMBLER-LIST@listserv.uga.edu> on behalf of robi...@dodo.com.au <robi...@dodo.com.au> Sent: Saturday, May 5, 2018 7:31 AM 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
