Grand Rapids, MI 49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Allan Staller
Sent: Monday, June 15, 2020 11:29 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: JES2 remote execution
**CAUTION EXTERNAL EMAIL**
**DO NOT open atta
ssage -
From: "Allan Staller"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Monday, June 15, 2020 10:28:30 AM
Subject: JES2 remote execution
Is anyone aware of the syntax to force execution on a particular LPAR in a
remote JES2 MAS.
The NJE links are established and running.
I tr
, MI
49546
616.653.8429 | fax: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Allan Staller
Sent: Monday, June 15, 2020 11:29 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: JES2 remote execution
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click
Looks like this is your answer.
JES2 normally processes /*JOBPARM statements at the node of execution.
When you place a /*JOBPARM statement before a /*ROUTE XEQ or /*XEQ statement,
JES2 at the input node checks the /*JOBPARM statement for syntax and parameter
validity. After processing the /*RO
Is anyone aware of the syntax to force execution on a particular LPAR in a
remote JES2 MAS.
The NJE links are established and running.
I tried /*ROUTE XEQ node.lpar but this executed on an incorrect JES2 instance.
Thanks in advance,
-Original Message-
From: IBM Mainframe Discussion Lis
