Would PRINT ON help? That seems too simplistic though.....

Regards – Grant.

-----Original Message-----
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On 
Behalf Of retired mainframer
Sent: Thursday, September 15, 2016 6:32 AM
Subject: Re: Printing macro expansion?

The LIBMAC option will cause the assembler to embed the library macros you call 
in the input stream (and listing).  See the HLASM Programmer's Guide.  From 
there, you should be able to cut and paste what you need.

If the offending statement is an assembler or machine instruction (as opposed 
to a macro instruction such as SET), the PRINT GEN statement might show you 
what you want.  But if the macro contains a PRINT NOGEN or PRINT OFF statement, 
it will overrule your statement.

> -----Original Message-----
> From: IBM Mainframe Assembler List [mailto:ASSEMBLER- 
> l...@listserv.uga.edu] On Behalf Of Paul Gilmartin
> Sent: Wednesday, September 14, 2016 3:53 PM
> Subject: Printing macro expansion?
> I have in SYSPRINT:
>   Loc  Object Code    Addr1 Addr2  Stmt   Source Statement
>                                       1 *
>                                       2          PRINT MCALL,MSOURCE
>                                       3          MyMacro
> ** ASMA144E Begin-to-continue columns not blank - MACRO - MyMacro
> ** ASMA435I Record 72 in 
> SYS16258.T163544.RA000.BADMAC.LIBE.H01(MyMacro)
> on volume: WORK01
> What additional PRINT options must I specify to show the entire 
> expansion of the macro?  Particularly since the error is not in Record 
> 72, but a misplaced continuation mark in the previous record.
DTCC DISCLAIMER: This email and any files transmitted with it are confidential 
and intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error, please notify us 
immediately and delete the email and any attachments from your system. The 
recipient should check this email and any attachments for the presence of 
viruses.  The company accepts no liability for any damage caused by any virus 
transmitted by this email.

Reply via email to