Hi Paul,
In respect of:
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
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
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
It's been several years since I actually used this but I thought //
meant skip everything from this point on until the next JOB statement.
Of course if there is no next job statement, it's effectively skip
everything after this point.
I started using // at the end of all my jobs back when my jobs really were
on card decks. We called it a hard end of job. My understanding back
then was that the system read in my card deck and would keep looking for
more cards in my job until it hit either the // hard end of job or the next
Yes, // ends the job.
However the remaining lines are being analyzed,
and if tehre is valid JOB statement then another job is started, That's
why multiple jobs can be started from single member.
--
Radoslaw Skorupka
Lodz, Poland
--
BRE Bank SA
ul. Senatorska 18
00-950 Warszawa
www.brebank.pl
6 matches
Mail list logo
