Not new. How is it not working? Is not // DD DDNAME=MOREDD being treated as DD DUMMY?
Bob Charles Mills wrote:
Is IEF686I DDNAME REFERRED TO ON DDNAME KEYWORD IN PRIOR STEP WAS NOT RESOLVED new in z/OS (new relative to OS/390)? I have JCL that was working in OS/390 V2R10 but is getting this error in z/OS. It's a concatenated DD: //MYDD DD DSN=SOME.DATASET.NAME(MEMBER),DISP=SHR // DD DDNAME=MOREDD Where MOREDD does not exist (in some cases -- it's a JCL INCLUDE file and sometimes I want to concatenate onto MYDD and sometimes I do not). In V2R10 I was just omitting MOREDD and OS/390 was happy. z/OS is giving me the error above. (FWIW, the JCL is actually a little more complicated with several concatenated PDS members and many intervening //* comments.) Yes, I know how to fix it (//MOREDD DD DUMMY) but I was just surprised that something that used to work had stopped working. I would be interested in a confirmation that I am not missing or imagining something.
---------------------------------------------------------------------- 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
