> Was there a job log message, S213-rc identifying the catenand?

Yes,

15.52.57 JOB01527  IEC141I 
013-18,IGG0191B,xxxxxxPL,PLKED,ASSEMOBJ-0009,1D41,LS050A,  325
   325             DATASET.NAME(CZAISAUT)

When I spotted that I figured out the problem. But I started out looking at the 
program (PLINK) listing. When a program says "this is my problem" it ought to 
know what it's talking about, right?
        
Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Paul Gilmartin
Sent: Monday, August 08, 2016 1:44 PM
To: [email protected]
Subject: Re: Interesting C library file open mis-diagnosis

On Mon, 8 Aug 2016 13:16:21 -0700, Charles Mills wrote:

>Not a problem or a complaint; just an observation.
>
>//ASSEMOBJ DD  DSN=DATASET.NAME(CZAARCH),DISP=SHR
>
>As luck would have it, CZAISAUT was missing. However, the diagnostic 
>from the prelinker was
>
>SEVERE ERROR EDC4001: Unable to read DD:ASSEMOBJ(CZAARCH).
> 
No, it's a problem.  A misleading diagnostic should always be considered a 
problem.  But I wonder which control block contains the relevant information.

Too many z/OS components behave as the first catenand were all.

A favorite: if the first catenand of SYSEXEC is a UNIX directory, Rexx fails (I 
forget the exact mesage).  If I make the first catenand an empty temporary PDS 
followed by the same UNIX directory, Rexx finds and executes EXECs in that 
directory.  ETR; WAD.  (Slight
misbehavior: sporadically the EXEC terminates with a program check, but it has 
completed successfully; I lose no data.)

Likewise, AMATERSE refuses to extract an archive in a UNIX file.  But if I 
catenate an empty temporary data set followed by that UNIX file, extraction 
works fine.

U:NIX is still a second class citizen but sometimes, in costume, it can pass.

Was there a job log message, S213-rc identifying the catenand?

-- gil

----------------------------------------------------------------------
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

Reply via email to