Author: Robert Sample
Subject: Reply to: Route a product's job to specific lpar
Posted: Thu Mar 02, 2017 7:21 am (GMT 5.5)
JES3 makes this an easy task since the global routes work to each LPAR. JES2, it's not so easy. Can you assign the job to a particular job class? If so, start an initiator on the desired LPAR with that job class and make sure no initiators on the other LPAR have that job class. If this is not an option, you may have to write a JES2 user exit.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Subject: Reply to: Route a product's job to specific lpar
Posted: Thu Mar 02, 2017 7:21 am (GMT 5.5)
JES3 makes this an easy task since the global routes work to each LPAR. JES2, it's not so easy. Can you assign the job to a particular job class? If so, start an initiator on the desired LPAR with that job class and make sure no initiators on the other LPAR have that job class. If this is not an option, you may have to write a JES2 user exit.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth