Rashmi, I haven't been keeping up with the latest developments in JCL for, well, about 10 years or so now so I just assumed someone at the coal face would find the answer to this thread quite quickly. However this issue has been raging since Wednesday and still no resolution has been provided.
When I saw the suggestion that there should be a comma between concatenated DD statements, I reassessed my relative level of competence in this area. Of course, I could be quite wrong and the problem could lie elsewhere but I personally, with my very limited knowledge of matters JCL, would never have thought it could be possible to put a comment in the middle of a set of cards - sorry, 80-byte records - making up a JCL statement for fear of provoking an error message of some sort such as maybe "EXPECTED CONTINUATION NOT RECEIVED". Thus I would remove "//* TYPRUN=SCAN," and try again. Chris Mason P.S. My introduction to JCL was some almost 39 years ago. I had to arrange to submit, via van-based remote job entry, a compile and go job to calculate some reaction diagrams in a physical chemistry project. I went to the relevant office, was handed a coding form marked with gibberish and told to punch up the cards and stick them on the front of the program and data - and don't ask what those cards mean! ----- Original Message ----- From: "Tim Hare" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Sunday, 30 April, 2006 2:30 PM Subject: Re: Submitting job using ReXX > >> //S2C9011 JOB (S2C9,XX,TI),'', > >> // MSGCLASS=T, > >> // NOTIFY=&SYSUID, > >> //* TYPRUN=SCAN, > >> // CLASS=X > >> //* > >> //PROCLIB JCLLIB ORDER=(PROD.PROC.LIB,PROD.PROC.LIB) > >> //* > >> //JOBLIB DD DSN=POITS.BATPROD.LOAD,DISP=SHR > >> // DD DSN=PODBM.SCIC.RESLIB,DISP=SHR > >> //* > > >I don't see a comma after the first JOBLIB DD statement. I think > >that is what matches this error message you received: > >> The JESYSMSG in the spool says "EXPECTED CONTINUATION NOT RECEIVED" > > Sorry, Wade - that's incorrect. You don't put commas between two DD > statements, they are two independent statements. A comma at the end of the > line is used to indicate continuation of one statement. > > The error message means, essentially, that somewhere a new statement > starts before the old one completed. If MSGLEVEL=(1,1) usually you can > look through the JESJCL listing for the statement mentioned in the error > message and quickly determine that it has a comma after the last > parameter, and that there's a JCL statement (DD, EXEC, OUTPUT, etc.) after > it. > > > Tim Hare > Senior Systems Programmer > Florida Department of Transportation > (850) 414-4209 ---------------------------------------------------------------------- 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
