zOs 1.7 JCL concatenation question ?

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), //

Re: zOs 1.7 JCL concatenation question ?

- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Anton Britz Sent: Tuesday, August 12, 2008 2:42 PM To: IBM-MAIN@BAMA.UA.EDU Subject: zOs 1.7 JCL concatenation question ? Hi, Why do we not see the concatenated SYSIN when we code the JCL the following way : 80 XXCMSYNIN

Re: zOs 1.7 JCL concatenation question ?

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

Re: zOs 1.7 JCL concatenation question ?

List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject zOs 1.7 JCL concatenation question ? 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

Re: zOs 1.7 JCL concatenation question ?

Hi vi01029, I do not normally respond with Thank you very much but this reply is worth a handshake or two.. Hal, thanks for responding too but it is nice to see vi01029 defending the way his product works. Note: Anybody saw the Microsoft blue screen of death during the opening of the