Hi Paul, In respect of:
"But today I happened to glance at one of my jobs with SDSF SJ. The "//" and all the following stuff are visible. So, from the SJ display I issued SUBMIT. The "//" and following are not shown by SJ for that submitted job. So, I try writing the content of the edit buffer to DD SYSOUT(,INTRDR) (I have a macro for that). Again, the "//" and following stuff are visible in that submitted job. So, I conclude that breaking of jobstreams at "//" is perormed not by JCL processing, but by TSO SUBMIT." In the bad old days with real card readers, many had an EOF button, and if that button was not pressed the reader task did not accept the input stream as complete and hence job would not be eligible to be processed. Rather than press the EOF button which would close the reader task, jobs would have a // as the last card, to mark the end of the job. The reader would then stay open and the input stream would be deemed complete and thus the job would process. >From a TSO perspective when I store JCL in TSO for submission I do not have terminating // statements as I rely on the logical EOF that occurs when SUBMIT reads the last input record. When submitting to the internal reader either from a batch program or CICS transaction then the last statement on each JCL set is a /*EOF to ensure the reader is closed. I hope this is of some value. Kind regards - Terry Terry Sambrooks Director KMS-IT Limited 228 Abbeydale Road South Dore, Sheffield, S17 3LA, UK Tel: +44 (0)114 262 0933 WEB: www.legac-e.co.uk Company Reg: 3767263 at the above address All outgoing E-mail is scanned, but it remains the recipient's responsibility to ensure their system is protected from spy-ware, trojans, viruses, and worms. ---------------------------------------------------------------------- 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
