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 [email protected] with the message: INFO IBM-MAIN
