Got it! Not sure exactly what the key ingredient was but I suspect that the
problem was that I had @Gil's un-externally-named entry point:
BAR DS 0D
...
END BAR
I changed that to
BAR DS 0D
ENTRY BAR
END
My experimentation took waaaay longer than it should have and I am uncertain of
the key change because IEBCOPY fails and still returns a zero return code!!! So
I was doing edit, assemble, link, copy, IEHLIST (still bad!) and not realizing
that the copy step was doing nothing and I was listing the results of a much
earlier copy.
IGW01557W MEMBER OTHERPGM NOT COPIED BECAUSE THE NAME ALREADY EXISTS IN
THE OUTPUT DATASET CAUSING A COPY GROUP NO-REPLACE CONFLICT
IGW01557W MEMBER FOO NOT COPIED BECAUSE THE NAME ALREADY EXISTS IN
THE OUTPUT DATASET CAUSING A COPY GROUP NO-REPLACE CONFLICT
IGW01558W MEMBER BAR NOT COPIED BECAUSE IT BELONGS TO A GROUP
IN WHICH A PREVIOUS NAME PROCESSED ENCOUNTERED COPY GROUP NO REPLACE CONFLICT
IGW01550I 0 OF 3 SPECIFIED MEMBERS WERE COPIED
IEB1130I A WARNING MESSAGE FROM FAMS PROCESSING APPEARS ABOVE -- DIAGNOSTIC
INFORMATION IS X'2810022D'
IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Pew, Curtis G
Sent: Tuesday, March 3, 2020 2:23 PM
To: [email protected]
Subject: Re: Two related alias entry address questions
On Mar 3, 2020, at 3:14 PM, Paul Gilmartin
<[email protected]> wrote:
>
> Relink with INCLUDE -ATTR. Module by module. Ouch. I suspect
> this is used under-the-covers by IEBCOPY PDS<-->PDSE.
>
>
Yes, I think you are going to have to use the binder for this. INCLUDE; ALIAS…;
NAME.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN