Paul Gilmartin wrote:
On Mon, 22 Jun 2009 12:42:55 -0500, Tom Marchant wrote:
On Mon, 22 Jun 2009 12:17:19 -0500, Paul Gilmartin wrote:
On Mon, 22 Jun 2009 11:11:42 -0500, Frank Schubert wrote:
No one seems to have hit upon the exact cause of your problem. It has
nothing to do with what you have in your JCL, except for the DISP on the
IEFBR14 step. What you have done wrong, although wrong is a subjective
term in this case, is tried to create a PDS dataset using DISP=MOD, when a
PS dataset with the same name already existed. ...
In fact, if the data set does not pre-exist, I verified by
experiment that DSORG=PS causes no problem.
If the COPY step specified:
//SYSUT2 DD VOL=REF=*.ALLOC.PRTLIB,...
... would it have used the data set from ALLOC (uncatalogued;
likely not what the OP wanted)?
No, as above.
OK. I see.
Isn't there an option to cause catalog errors to ABEND or at least
cause bad RC from the step? (But this frustrates the OP's apparent
intent to make the JCL reusable.)
There is. Or was. IIRC it was a simple USERMOD. It is not needed for
SMS-managed data sets.
Would this (PARMLIB option) have caused an error for:
IEF287I user.TSTPRB.COMPILE.OUTPUT NOT RECTLGD 2
... ?
Yes, if you specify FAILJOB(YES). The job is terminated with
a JCL error, and the message:
IEF378I jobname stepname - JOB FAILED - TIME=hh.mm.mm
CATALOG DISPOSITION ERROR
--
Richard
----------------------------------------------------------------------
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
