Do you have a test system where you can bring down JES2 and then restart it with your new parms?
If not, when I had that error (and it might not be this) I had coded /* /* */ JES2 does not like this code. It likes /* */ If you have SYSLOG, there are messages that tell you exactly the error just before the REPLY END or CANCEL. A SAD will capture the SYSLOG so you could review it on a different system if need be through IPCS. Lizette -----Original Message----- >From: "Starr, Alan" <alan_st...@calpers.ca.gov> >Sent: Jul 7, 2010 5:11 PM >To: IBM-MAIN@bama.ua.edu >Subject: Re: jes2 parm syntax checking > >Tim, > >Have you tried "OPTSDEF LIST=YES" as the first statement? > >Alan > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of >Tim Brown >Sent: Wednesday, July 07, 2010 13:52 >To: IBM-MAIN@bama.ua.edu >Subject: jes2 parm syntax checking > >Is there a way to syntax JES2 statements We are trying a new config, the old >one starts ok The new one gets the cancel or end option and we cant determine >the error. > >Tim Brown > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
