On Tue, 9 May 2017 16:33:35 -0500, Paul Gilmartin
([email protected]) wrote about "Re: JCL
null statement (Was: job output into dataset" (in
<[email protected]>):
[snip]
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?)
The IBM term is "flushed". They never hit the spool and no console
message is issued.
At what point if any in the logic does the access method recognize INTRDR
as special, different from ordinary SYSOUT?
QSAM doesn't distinguish between INTRDR and any other SYSOUT writer.
VSAM detects on the OPEN and uses a specific form called JAM (JES Access
Method).
Does the
//
/*EOF
... that John M. mentioned cause flushing of any SYSOUT or only one with
W=INTRDR?
Only using INTRDR. Other SYSOUT streams have to tolerate any character
sequence and cannot safely reserve them for commands to the writer
(unless some custom writer can process commands). The other IBM writers
do not have internal commands, AFAIAA.
What happens if the operator issues "$TOJ W=INTRDR" on an ordinary
SYSOUT data set after the fact?
Probably nothing good.
--
Regards,
Dave [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
[email protected] (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
