You should use
PUSH PRINT
PRINT OFF
.
.
.
POP PRINT
On Tue, 28 May 2024 16:32:01 +0000 Willy Jensen <[email protected]>
wrote:
:>Well, I have a couple of assembler copy books that are 1000+ records in size.
So normally the COPY statements are inside a PRINT OFF and PRINT ON set. Then
if I get an assembly error inside those macros, I remove the PRINT OFF,
reassemble and the I can most often identify the failing macro by the line
number, which is shown.
:>
:>Regards
:>Willy
:>
:>-----Oprindelig meddelelse-----
:>Fra: IBM Mainframe Assembler List <[email protected]> På vegne
af David Clark
:>Sendt: 28. maj 2024 18:03
:>Til: [email protected]
:>Emne: Assembler Listing PRINT OFF Issue
:>
:>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.
:>
:>Sincerely,
:>
:>Dave Clark
--
Binyamin Dissen <[email protected]>
http://www.dissensoftware.com
Director, Dissen Software, Bar & Grill - Israel
