Submit the job in hold status and use SDSF to look at the data card(s) in the SYSIN "member". Then find that data in the dataset you submitted and determine why it was not recognized as JCL. One common reason is that columns 1 and 2 do not contain // or /*.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Paul Gilmartin > Sent: Wednesday, May 27, 2015 9:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: GENERATED STATEMENT!? > > In my JESJCL listing I see: > ... > 33 // EXPORT SYMLIST=* > 34 // SET IFSYM='' (Blank for pre-JES2 2.1.) > 35 //IFSYM EXPORT EXPSET= GENERATED > STATEMENT > 36 // SET SYMVAL='Symbol value longer than name.' > 37 //SYMVAL EXPORT EXPSET=Symbol value longer than... GENERATED > STATEMENT > //* > 38 //SYMS1 DD *,SYMBOLS=(EXECSYS,LOGDD1) > 39 //LOGDD1 DD SYSOUT=(,) > //* > 40 //SYMS2 DD *&IFSYM,SYMBOLS=(EXECSYS,LOGDD2) > IEFC653I SUBSTITUTION JCL - *,SYMBOLS=(EXECSYS,LOGDD2) > 41 //SYSIN DD * GENERATED STATEMENT > 42 //LOGDD2 DD SYSOUT=(,) > //* > 43 // > > Where does "41 //SYSIN DD * GENERATED STATEMENT" > come from? What does it mean? (I had no stray data cards.) > > I hate JCL! > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
