I think that, for a JCL concatenation, only the first DD statement would be normally be used for the DDNAME= (did you get a message IEF694I?).
However, it seems that the second DD statement does actually get picked up when the concatenated DD statements are located immediately following the invocation of the PROC (this does seem a bit of a quirk). It wouldn't work the same way if the CMSYNIN DD statement wasn't the last statement in the procedure. Conceptually, the DDNAME= parameter works as if the first SYSIN DD statement (and not the following DD statement) is moved in place of the CMSYNIN DD statement. (At least, that's my half-baked theory). Bill On Tue, 12 Aug 2008 14:41:53 -0500, Anton Britz <[EMAIL PROTECTED]> wrote: >Hi, > >Why do we not see the concatenated SYSIN when we code the JCL the >following way : > >80 XXCMSYNIN DD DDNAME=SYSIN >81 //CMWKF02 DD DSN=SYS3.APRCB.PROD.UNDUP(+1), > // DISP=(NEW,PASS,DELETE), > // UNIT=SYSDA,SPACE=(TRK,(20,2),RLSE), > // DCB=SYS3.PATTERN.RECL0020 >82 //SYSIN DD DSN=SYS3.ANATP.LOGON,DISP=SHR >83 // DD * > INPUT > /* > >But if we code it this way, the second SYSIN concatenation is seen by the >program : > >80 XXCMSYNIN DD DDNAME=SYSIN >81 //SYSIN DD DSN=SYS3.ANATP.LOGON,DISP=SHR >82 // DD * > INPUT > /* >83 //CMWKF02 DD DSN=SYS3.APRCB.PROD.UNDUP(+1), > // DISP=(NEW,PASS,DELETE), > // UNIT=SYSDA,SPACE=(TRK,(20,2),RLSE), > // DCB=HWG.PATTERN.RECL0020 > ---------------------------------------------------------------------- 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
