>If I change the proc so that SYSUT1 is last statement, everything works >fine
I think it's a coincidence (more or less) that it works. The "orphan" DD's get concatenated to the previous DD, which just happens to be SYSUT1 in this case. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Shmuel Metz (Seymour J.) Sent: Tuesday, June 05, 2012 7:12 PM To: IBM-MAIN@bama.ua.edu Subject: Re: JES/2 Proc SYSIN Concat Error?? In <of4c5d492a.3aca1a06-on86257a14.0070c48f-86257a14.00717...@ameritas.com>, on 06/05/2012 at 03:39 PM, Chip Grantham <cgrant...@ameritas.com> said: >Subject: JES/2 Proc SYSIN Concat Error?? It has nothing to do with JES2. >I only receive the DD * data in SYSUT2, not the copied >ISCLG.JCL(SHOWIT) proc. That's the way DDNAME= has always worked; you cannot forward reference a concatenation. >If I change the proc so that SYSUT1 is last statement, everything works >fine Are you a betting man? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
