Thanks Lizette. Interesting. My work around was to use the true DDNAME and not the DDNAME= DDNAME.
And I didn't see the message. It's actually in the JESYSMG dataset and not in the JESMSGLG where I would expect such messages. Thanks. I was just so shocked to not see the expected output. (My original occurrence of the issue was with a must more important large job.) Is it just me, or does this seem like I'm expected to interrupt the message to be, we know this isn't what you expect and we might even consider it an error, but instead of fixing it, we'll produce a message. Does the message always makes everything OK? The Job runs to EOJ, and there is not a non-zero condition code set, but there really is an error IMHO. Is there a way to make the job receive a JCL Error, or abend? Chip Grantham | Ameritas | Sr. IT Consultant | cgrant...@ameritas.com 5900 O Street, Lincoln NE 68510 | p: 402-467-7382 | c: 402-429-3579 | f: 402-325-4030 From: Lizette Koehler <stars...@mindspring.com> To: IBM-MAIN@bama.ua.edu Date: 06/05/2012 04:00 PM Subject: Re: JES/2 Proc SYSIN Concat Error?? Sent by: IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> Chip, I replicated your process and had the following ERROR message in my JES MSG LOG from z/OS V1.12 IEF694I DDNAME REFERENCE TO DD CONCATENATION REFERS ONLY TO FIRST DD Explanation: THE JCL DDNAME keyword has been used to refer to a DD concatenation. When the object of a DDNAME reference is a concatenation of multiple DDs, only the first DD in the concatenation is actually referenced. System Action: The system issues message IEF677I and continues processing the job. The first DD in the referenced concatenation is associated with the referencing DD. The remaining (unlabeled) DDs in the referenced concatenation are concatenated to the labeled DD immediately preceding the concatenation. User Response: If the DDNAME reference was intended to refer to the entire concatenation, move the concatenated DDs to follow the referencing DD rather than the referenced DD. This will ensure that the concatenation is correctly defined to the system. So you need to have your input last. Lizette > >I'm wondering if anyone else has seen this phenomenon. Doesn't seem right >to me. > >I have a proc that looks like this > >//SHOWIT PROC >//STEP010 EXEC PGM=IEBGENER >//SYSPRINT DD SYSOUT=* >//SYSUT1 DD DDNAME=INPUT >//SYSIN DD DUMMY >//SYSUT2 DD SYSOUT=* >//SHOWIT PEND > >in the dataset ISCLG.JCL(SHOWIT) > >I execute it with JCL like >//ISCLGTES JOB 3432000, >// 'CHIP GRANTHAM X7382', >// CLASS=S, >// MSGCLASS=X >// JCLLIB ORDER=ISCLG.JCL >//STEP010 EXEC SHOWIT >//INPUT DD * > * ------------------------------------------------------------------ * > * THIS IS THE PROC YOUR EXECUTING * > * ------------------------------------------------------------------ * >// DD DISP=SHR,DSN=ISCLG.JCL(SHOWIT) > >I only receive the DD * data in SYSUT2, not the copied ISCLG.JCL(SHOWIT) >proc. > * ------------------------------------------------------------------ * > * THIS IS THE PROC YOUR EXECUTING * > * ------------------------------------------------------------------ * > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN ******* This message may contain confidential information intended only for the use of the addressee(s) named above and may contain information that is legally privileged. If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message immediately thereafter. Thank you. ******* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
