Hi all, I have a silly question that I'm pretty sure I know the answer to but want verification in case there's some obscure reason for having this. We have multiple batch job steps that close and open CICS files within the JCL. They look similar to this:
//STEP010 EXEC PGM=IEBGENER //CTRNORST DD DUMMY //SYSUT1 DD DATA,DLM='**' /*$VS,'F CICSA,CESN USERID=********,PS=********' /*$VS,'F CICSA,FOCT C,FILEABC;' ** //SYSUT2 DD SYSOUT=(*,INTRDR) //SYSIN DD DUMMY /*$ <<<<<< my question //SYSPRINT DD SYSOUT=* /* FOCT is a home-grown transaction that closes or opens CICS files. At the end of the job step is a JES2 command line that appears to do absolutely nothing. Am I correct in thinking this does nothing and can be removed? We run a pretty much vanilla JES2 system with no obscure user exits or anything that would be looking for something like this. The JCL reference manual says nothing about having an empty JES2 command statement. TIA, Rex ---------------------------------------------------------------------- The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
