This sort of sounds like "Doctor, doctor - it hurts when I do this"
At any rate, I wonder if you could use OPSYN on those special statements and have the OPSYN replacement macro issue an MNOTE before reissuing the instruction. On Tue, 28 May 2024 12:02:48 -0400 David Clark <[email protected]> wrote: :>I think PRINT OFF is a bit too drastic. At the very least, any MACRO or :>DSECT statement that is included via COPY should be able to be shown in the :>assembler listing even if PRINT OFF is in effect. I understand why PRINT :>OFF is needed, but it also makes it difficult to identify the source of :>macros and dsects when they aren't even shown in the listing and copy names :>don't match. :>Obviously, having copy names match is desirable. But, when there are :>multiple macros or dsects in a single copy source then it is not possible. :>If y'all don't have a solution for this then it should be an enhancement :>request. -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel
