Re: Does // terminate JCL?
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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Does // terminate JCL?
I keep a lot of JCL in Unix files and submit the jobs with FTP. I often place inactive job steps, comments, notes, whatever at the end of the file, after a // line. Sometimes I even keep a description at the front: Here's what the following job does ... // //NAME JOB ... Causes no problems other than an occasional SYSLOG message: $HASP125 user INTRDR SKIPPING FOR JOB CARD ... which I don't happen to consider a problem. 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. It's probably more complicated than that. -- gil -- 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
Re: Does // terminate JCL?
Yes, nothing after the // will be processed when submitting to a JES internal reader. Paul Gilmartin wrote: I keep a lot of JCL in Unix files and submit the jobs with FTP. I often place inactive job steps, comments, notes, whatever at the end of the file, after a // line. Sometimes I even keep a description at the front: Here's what the following job does ... // //NAME JOB ... Causes no problems other than an occasional SYSLOG message: $HASP125 user INTRDR SKIPPING FOR JOB CARD ... which I don't happen to consider a problem. 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. It's probably more complicated than that. -- gil -- 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 -- 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
Re: Does // terminate JCL?
It's been several years since I actually used this but I thought // meant skip everything from this point on until the next JOB statement. Of course if there is no next job statement, it's effectively skip everything after this point. -- 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
Re: Does // terminate JCL?
I started using // at the end of all my jobs back when my jobs really were on card decks. We called it a hard end of job. My understanding back then was that the system read in my card deck and would keep looking for more cards in my job until it hit either the // hard end of job or the next job card. Your job on a card deck did not really get submitted until the card reader saw the // or the next JOB card. So I always put // at the end so my job would be submitted immediately. You didn't have to do that if the computing center was busy and there were lots of frequent jobs, but if you were there by yourself when it was quiet (as I often was) you put on the // to get your job moving right away. I assume there was some sort of timeout value in the system that would eventually submit a job with no // at the end even if there were no next JOB card for a while. I still use it today as a handy place to keep junk. For jobs that frequently change I keep alternatives for the DD cards and such below the // and they get ignored. When I edit the job I can quickly and easily change the jobs by adding or deleting // cards or moving stuff above or below the // card. It's easier than using //* to comment out blocks of lines and then uncomment them when I want them. I never tried putting it at the top like your example. --Roger On Sat, Nov 14, 2009 at 11:00 AM, Paul Gilmartin paulgboul...@aim.comwrote: I keep a lot of JCL in Unix files and submit the jobs with FTP. I often place inactive job steps, comments, notes, whatever at the end of the file, after a // line. Sometimes I even keep a description at the front: Here's what the following job does ... // //NAME JOB ... Causes no problems other than an occasional SYSLOG message: $HASP125 user INTRDR SKIPPING FOR JOB CARD ... which I don't happen to consider a problem. 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. It's probably more complicated than that. -- gil -- 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 -- 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
Re: Does // terminate JCL?
Yes, // ends the job. However the remaining lines are being analyzed, and if tehre is valid JOB statement then another job is started, That's why multiple jobs can be started from single member. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237 NIP: 526-021-50-88 Według stanu na dzień 01.01.2009 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 118.763.528 złotych. W związku z realizacją warunkowego podwyższenia kapitału zakładowego, na podstawie uchwały XXI WZ z dnia 16 marca 2008r., oraz uchwały XVI NWZ z dnia 27 października 2008r., może ulec podwyższeniu do kwoty 123.763.528 zł. Akcje w podwyższonym kapitale zakładowym BRE Banku SA będą w całości opłacone. -- 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
