|
View previous topic :: View next topic
|
| Author |
Message |
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
I am looking for the the JES3 equivalents for these JES2 JCL statements:
| Code: |
/*ROUTE XEQ nodename
/*JOBPARM S=SYS1 |
Reading the JCL reference, I want to say it is this:
| Code: |
//*ROUTE XEQ nodename
//*MAIN SYSTEM=(SYS1) |
But the terms used in the JES3 chapter are unfamiliar, for example: 'Indicates that the job is to run on the named processor'.
I would like someone to confirm my guess. |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Yes, you are correct. The MAIN statement for JES3 indicates where to execute the job as well as what JES options are for the job. |
|
| Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
Pedro -- //*MAIN - I think your guess is correct, but you should confirm how the JES3 system names are assigned in your shop relative to the system names in JES2. Many other //*MAIN parameters seem to mimic JES2 /*JOBPARM statement parameters.
- //*ROUTE XEQ seems to mimic the JES2 /*ROUTE XEQ and /*XMIT statements. There seem to be detail differences, so you may have to experiment.
I can't say I'm a real JES3 expert. Back in my product support days we would occasionally run JES3, but never with networking or multiple JES3 "main" systems. We always hated it; this was before SDSF support of JES3 and we didn't have Flasher or an equivalent product. |
|
| Back to top |
|
|
|
|
