Re: JCL null statement (Was: job output into dataset)
On Tue, 9 May 2017 13:38:02 -0500, Tom Marchant wrote: >On Tue, 9 May 2017 13:25:43 -0500, Paul Gilmartin wrote: > >>On Tue, 9 May 2017 18:59:23 +0100, David W Noon wrote: >>> i) the job stream arrives at a null statement; >>>... >>I'm skeptical about that point since I often submit jobs with noise >>such as comments after a null statement and SDSF shows me >>those lines in JESJCLIN, indicating that the job was not spun until >>the SYSOUT was closed. > >I don't believe it. > >The behavior that David describes is very old. Back in the 70's, >operators would routinely add a null JCL statement to the end of >a tray of JCL to be processed so that the last job would be >processed immediately. I just submitted such a job and the >contents of JESJCLIN ends with the last statement before the >null JCL statement. > I found it. Using the Rexx API to SDSF and issuing the SJA prefix command I see a spool data set that shows the null statement and any records following it. (I had no following JOB statement.) (It has to go somewhere: https://en.wikipedia.org/wiki/Black_hole_information_paradox ) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JCL null statement (Was: job output into dataset
On Tue, 9 May 2017 21:39:52 +0100, David W Noon wrote: >On Tue, 9 May 2017 14:56:33 -0500, Paul Gilmartin >(000433f07816-dmarc-requ...@listserv.ua.edu) wrote about "Re: job >output into dataset" (in ><5975685166305075.wa.paulgboulderaim@listserv.ua.edu>): > >> On Tue, 9 May 2017 20:20:10 +0100, David W Noon wrote: >[snip] >>> What kind of null statement did you use? >>> >>> The JCL null statement is coded as two slashes followed by blanks to the >>> end of the card image (or column 72 at least). >>> >> Two slashes and nothing else; no blanks. Do I need to have blanks? > >I think you will need at least 1 blank. I have never used varying length >records for JCL, since I date back to the days of Hollerith cards, which >were always 80 bytes long. > What happens to any additional records between the null statement and the next JOB statement? are they quietly ignored (with perhaps a message to operator?) At what point if any in the logic does the access method recognize INTRDR as special, different from ordinary SYSOUT? Does the // /*EOF ... that John M. mentioned cause flushing of any SYSOUT or only one with W=INTRDR? What happens if the operator issues "$TOJ W=INTRDR" on an ordinary SYSOUT data set after the fact? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
JCL null statement (Was: job output into dataset
On Tue, 9 May 2017 14:56:33 -0500, Paul Gilmartin (000433f07816-dmarc-requ...@listserv.ua.edu) wrote about "Re: job output into dataset" (in <5975685166305075.wa.paulgboulderaim@listserv.ua.edu>): On Tue, 9 May 2017 20:20:10 +0100, David W Noon wrote: [snip] What kind of null statement did you use? The JCL null statement is coded as two slashes followed by blanks to the end of the card image (or column 72 at least). Two slashes and nothing else; no blanks. Do I need to have blanks? I think you will need at least 1 blank. I have never used varying length records for JCL, since I date back to the days of Hollerith cards, which were always 80 bytes long. -- Regards, Dave [RLU #314465] *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* david.w.n...@googlemail.com (David W Noon) *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
