You could have stepa run on systemA and have a step a1 submit a job via the
internal reader which has a /*route exq to systemB, then have that job on
systemB submit the rest of the job that needs to run on systemA (also via
internal reader).
We had a product which we were in beta test back
Class=A and class=B has nothing to do with system. The job card has a system
affinity parameter to run that job on a specific system.
Running a step on another system is rarely the correct answer. You would be
blocking the initiator. Additionally, resources are shared so that job is
probably
Nope. The controls are at the JOB level. There is no way to run stepXY on any
other LPAR.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of K
Sent: Monday, August 26, 2019 1:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: CLASS parm for EXEC statement?
Dear all,
I am
t; To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: CLASS parm for EXEC statement?
>
> Dear all,
>
> I am running JES2 (z/OS 2.2) in my parallel sysplex environment. Is there
> any utility-trick so to submit a job in SYSA (using job CLASS=A) but a
> stepXY in this job to be executed in SYSB? I wou
Dear all,
I am running JES2 (z/OS 2.2) in my parallel sysplex environment. Is there any
utility-trick so to submit a job in SYSA (using job CLASS=A) but a stepXY in
this job to be executed in SYSB? I would like to prevent from submitting a
separate job to SYSB (jobclass=B) including stepXY. As
