-LIST@LISTSERV.UGA.EDU
Subject: Re: Printing macro expansion?
On 2016-09-14 17:27, Hardee, Chuck wrote:
> Try "COPYing" the macro into your program so that the macro source is listed.
> That may be enough to get to the bottom of it.
>
If I have the source, I can inspect it witho
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 assembl
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
On 2016-09-14 17:27, Hardee, Chuck wrote:
> Try "COPYing" the macro into your program so that the macro source is listed.
> That may be enough to get to the bottom of it.
>
If I have the source, I can inspect it without "COPYing" it/
> What line 72 in the macro?
>
In fact, it's obvious to me wh
Try "COPYing" the macro into your program so that the macro source is listed.
That may be enough to get to the bottom of it.
What line 72 in the macro?
Charles (Chuck) Hardee
Senior Systems Engineer/Database Administration
EAS Information Technology
Thermo Fisher Scientific
300 Industry Drive |
