On Tue, 9 May 2017 21:39:52 +0100, David W Noon wrote:
>On Tue, 9 May 2017 14:56:33 -0500, Paul Gilmartin
>([email protected]) wrote about "Re: job
>output into dataset" (in
><[email protected]>):
>
>> 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 [email protected] with the message: INFO IBM-MAIN
