@LISTSERV.UA.EDU
Subject: Re: SEVERE ERROR EDC4002: Unable to write to map file from Prelinker
Thanks. If that is your PMR you could update them with the fix which is shown
below. Do not know if both RECFM and LRECL are necessary; I only tried with
both.
Charles
-Original Message-
From: IBM
Sent: Friday, November 9, 2018 6:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SEVERE ERROR EDC4002: Unable to write to map file from Prelinker
Hi Charles,
We experienced the same thing several weeks ago. It is documented in PHO3870.
http://www-01.ibm.com/support/docview.wss?crawler=1
Sent: Thursday, November 8, 2018 5:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SEVERE ERROR EDC4002: Unable to write to map file from Prelinker
Good thought. I suppose that might account for it.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN
Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>Behalf Of Charles Mills
>Sent: Thursday, November 8, 2018 9:00 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: SEVERE ERROR EDC4002: Unable to write to map file from Prelinker
>
>I'm getti
IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>Behalf Of Charles Mills
>Sent: Thursday, November 8, 2018 9:00 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: SEVERE ERROR EDC4002: Unable to write to map file from Prelinker
>
>I'm getting "SEVERE ERROR EDC4002: Unabl
On Thu, 8 Nov 2018 09:42:59 -0800, Charles Mills wrote:
>And the answer is
>
>//SYSOUT DD SYSOUT=*,LRECL=80,RECFM=FB
>
>Kind of pathetic if you ask me.
>
A well-designed program will supply defaults for any such attributes
the programmer omits.
A mal-designed program (there are many,
Subject: SEVERE ERROR EDC4002: Unable to write to map file from Prelinker
I'm getting "SEVERE ERROR EDC4002: Unable to write to map file" from the XLC
C/C++ prelinker. This is a job that was running successfully on another
system and has now been moved to a new and unfamiliar system.
A
I'm getting "SEVERE ERROR EDC4002: Unable to write to map file" from the XLC
C/C++ prelinker. This is a job that was running successfully on another
system and has now been moved to a new and unfamiliar system.
Anyone have any clues on what the specific complaint might be?
According to
