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 [email protected] 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 [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
