I gather you are COPYing a member from SYSLIB that invokes a macro
from SYSLIB? (Or is it a macro COPYing a member into the macro?)

If the COPY statement is in open code, you might want to try
capturing the &SYSLIB_MEMBER info with statements inside the COPY
file just before it invokes the macro.

Please let me know if I've misunderstood your situation.
John Ehrman
(P.S.: I'd appreciate a reply to ASSEMBLER-LIST; I only scan the
IBM-MAIN list in daily-digest form.)
    (------------------ Referenced Note Follows --------------------)
Date:         Sun, 10 Jul 2005 15:02:24 -0700
From: "Keith E. Moe" <[EMAIL PROTECTED]>

I was adding logic to one of my Macros to build a table of symbols
about the Macro Usage and one of the items I wanted to record is
the name of the COPY member that invoked the Macro. The &SYSIN_MEMBER
and &SYSLIB_MEMBER are not enough, as the &SYSIN_MEMBER and
&SYSLIB_MEMBER are always the same (same Macro each time).

Wouldn't it be nice to have an &COPY_MEMBER System Symbol (or other
suitable name)? Do others think that this would make a good
requirement against the HLASM?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to