Not in this case.  When multiple macros are included from a single
copybook, there is no indication in that section of the listing as to from
where such macros came.  Yes, it has the name(s) of the macro but not where
it came from.  In my case, the copy code also had PRINT OFF around it.  The
following is that section of the listing.

BIT                                       Macro and Copy Code Source
Summary                                   Page   20
 Con Source                                        Volume    Members
                HLASM R6.0  2024/05/28 11.41
     PRIMARY INPUT                                           AND      ELSE
   ENDIF    IF       JK       JNK      WEND
                                                             WEXIT
WHILE    WLOOP
  L1 DAP.PROD                                      IDD031    IF       WHILE
  L6 PRD1.MACLIB                                   DOSRES    RETURN   SAVE

Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio  45439  USA
(937) 294-5331


On Fri, May 24, 2024 at 9:30 PM Ed Jaffe <
000017285f33d197-dmarc-requ...@listserv.uga.edu> wrote:

> On 5/24/2024 8:58 AM, David Clark wrote:
> > Can't find that macro, either.  Now what?   ;-)
>
> The "Macro and Copy Code Source Summary" on the HLASM listing shows from
> which library every macro and copy code member was read.
>
> --
> Phoenix Software International
> Edward E. Jaffe
> 831 Parkview Drive North
> El Segundo, CA 90245
> https://www.phoenixsoftware.com/
>
>
>
> --------------------------------------------------------------------------------
> This e-mail message, including any attachments, appended messages and the
> information contained therein, is for the sole use of the intended
> recipient(s). If you are not an intended recipient or have otherwise
> received this email message in error, any use, dissemination, distribution,
> review, storage or copying of this e-mail message and the information
> contained therein is strictly prohibited. If you are not an intended
> recipient, please contact the sender by reply e-mail and destroy all copies
> of this email message and do not otherwise utilize or retain this email
> message or any or all of the information contained therein. Although this
> email message and any attachments or appended messages are believed to be
> free of any virus or other defect that might affect any computer system
> into
> which it is received and opened, it is the responsibility of the recipient
> to ensure that it is virus free and no responsibility is accepted by the
> sender for any loss or damage arising in any way from its opening or use.
>

Reply via email to