HAD SMP/E printed the card image or keyword it DID see it would have been a HUGE clue as to what the real problem was.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Charles Mills Sent: Wednesday, September 07, 2016 8:44 AM To: [email protected] Subject: Error messages and such (Was RE: FTP on z/OS sucks) Yes, I actually, personally encountered this message. Yes, it substituted the keyword which was, from memory, <GIMUNZIP>. I was kind of mystified because there in the job was //SYSIN DD * <GIMUNZIP> etc. The problem turned out to be one of my other favorite design -- umm, things I would have done differently had I written MVS -- the generated SYSIN statement. Preceding the above in the job was some misplaced non-JCL record and the interpreter or converter or whoever generated a gratuitous SYSIN DD statement, and that is the SYSIN dataset that the message was complaining about. > But I do wish that when SMP/E reports a syntax error it would print a > ruler with a pointer indicating the exact point of error OT, but may I brag? The product I DID design and implement reports errors as shown in this example. CZA0082S Error detected while processing maximum message length ('40000') of 'MAXMSGLEN' CZA0084I Near column 31 of record 5 of Parameter File CORRELOG.CZAGENT.CNTL(CZAPARMS) CZA0105I V CZA0106I SERVER 10.2.1.118 MAXMSGLEN(40000) CZA0023S Value must be numeric and between 512 and 32767 Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
