JES2 also has /* commands, such as:

/*JOBPARM
/*MESSAGE
/*NETACCT
/*NOTIFY
/*OUTPUT
/*PRIORITY
/*ROUTE
etc.


So I would imagine those look like comments to you.

MVS has JCL so does VSE. Each of them has a "spooler" system (JES2|JES3 for MVS and POWER for DOS type systems last I did a DOS/VSE-ESA migration to z/OS such as
* $$ SLI xxx   ).


But depending on whether or not you have JES3 installed and/or JES2 installed (JES3 had to be the PRIMARY subsystem, JES2 can be secondary) would determine if //*MAIN (and such) was just a comment or directed the JES3 system to do something.

JES3 also has a command to cause a JOB to run on a specific "LPAR" (Back in the day, CEC).

//*MAIN says which MVS system(s) to select from to schedule this JOB to run/execute.

You should really look at a JCL REF manual. All of this is documented there. But the JES3 DOC may be gone. I don't know when IBM will (or already has) pulled the JES3 JCL doc (z/OS 2.4 has it). I haven't needed (yet) to get a full copy of the 3.1 manuals to look at new stuff.

Steve Thompson


On 4/14/2024 8:36 PM, Paul Gilmartin wrote:
On Sun, 14 Apr 2024 19:47:38 -0400, Steve Thompson wrote:

JES3 is not retarded.

I may have judged hastily from such as that the OUTPUT JCL statement
came to JES2 before JES3.  You could pay extra to not get the feature.

JES3 has this:
//*DATASET parameters.....

//*ENDDATASET

Those look like comments.  I guess it provides a sort of compatibility
in that JES2 will ignore them.  At the cost of making it harder to
detect and report typos.

Can the delimiter be changed to allow such lines within instream data?


This is what the z/OS MVS JCL REF has for the parameters:
   ...
//*DATASET DDNAME=ddname[,parameter]...
This allows one to put that data in-stream, define what DD will
be using it..... And then the JOB Step that gets it, the data is
encapsulated better than JES2 does it.

I see little use in the feature.  But if I don't like it, or dln't
understand it, I don't have to use it.

So I think this can handle the problem of "IEBUPDTE".

No.  The problem is not in JES[23], but in IEBUPDTE, which
has nothing like a DLM= parm which would allow data lines
resembling IEBU{DtE commands to appear instream.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to