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 specific to that system. There's also the possibility the system is
down at the moment. Ask yourself what you really need.
Can all the steps run on that system (sysb). If so, assign system affinity for
the job to SYSB.
If you need jobs run in a specific sequence, you can use a job schedule (e.g.
OPS/MVS, CA-7 or ...).
Jon.
On Sunday, August 25, 2019, 11:55:38 PM PDT, K <kzafi...@gmail.com> wrote:
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 far as I know there is a
limitation in job class so all steps to be executed in the same system.
kind regards
Konstantinos Zafiropoulos
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
