I just tested JNOP with a constant operand of "1" and the only issue is the warning-level message which results in RC=04:
000074 A704 0001 00001 49 JNOP 1 ** ASMA056W Absolute value found when relocatable value expected - 1 IMHO that's not so bad that it should have been left out of IEABRC/IEABRCX, or perhaps provided as an option (e.g., with a GBLB setting that defaults to FALSE). The danger of NOT translating NOP to JNOP happens when the NOP operand is an actual DDD(I,B) based address, where the base is not an existing USING register. THAT results in an RC=08 error, not a warning: 000074 0000 0000 00000 49 NOP RETURN ** ASMA307E No active USING for operand RETURN OTOH, the RC=08 gives you a clear indication where you have to change the code when converting to relative branch logic. Water under the bridge, I know, and very unlikely to ever change. I can live with that. Peter From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On Behalf Of Jonathan Scott Sent: Wednesday, May 1, 2024 11:15 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: IEABRC anomaly As NOP is not a branch, I would not expect NOP to be converted by IEABRC. It is true that NOP has an address operand. If NOP is executed using EX with a suitable mask in the register it can be used for execution purposes, although this is rather obscure. However, as the address operand is not normally used for a branch, it might not work to convert it to relative. For example, I have seen code which uses NOP 1, NOP 2 etc. as markers for debugging purposes, which would definitely cause problems if changed to relative addressing. Jonathan Scott, HLASM IBM Hursley, UK -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
