you can setup job-routing rules and all the WIT for the job will run on the same appserver that picked up the job. otherwise you can't disable work item sharing.
what issue are you trying to work around ?
Thanks for the answer to my question.
Is not usal for me to manage job-routing rules, so how can I specifiy that all WIT for a job will run on the same AppServer ?
Our issue is about a multi-instances AppServer working with Proxy Socks. When an AppServer start the connection to a Proxy Socks threads of the other instance are not able to address server behind the Proxy Socks. We receive an error message "Remote hosts is unknown".
You don’t need to do anything special here for the routing rule. you can create a rule like ‘JOB.NAME’ equals xxx and set the target appserver you want the job to run on.
Is the socks issues a known defect you have a support ticket for ? do you have the ‘resolve on proxy’ option set or are you using the appserver to resolve the target names ? if the later, are both appservers using the same dns servers ?
Was the job routing of patching job's child jobs fixed in 8.5 SP1+ ? It used to ignore job routing and there was a defect for it.
Otherwise, what Bill suggested should work. I've done this before. The ideal way to do this is using a new JOB property (i.e. PREFERRED_JOB_SERVER) with a limited list of choices, one value instance for each app server, and one for Any.
Set the default value to Any so that by default, any job will spawn on any of the app servers unless you specify otherwise. Then set one routing rule for each app server like this:
??JOB.PREFERRED_JOB_SERVER?? = 'JOB_SERVER1' route to JOB_SERVER1
??JOB.PREFERRED_JOB_SERVER?? = 'JOB_SERVER2' route to JOB_SERVER2
??JOB.PREFERRED_JOB_SERVER?? = 'Any' route to JOB_SERVER1,JOB_SERVER2,...
Make sure the catch-all "Any" rule is last.
Patching jobs not correctly obeying job routing rules
Yes we have a ticket open to the support on the Socks issue N° ISS04466316.
We have the resolution option set to ‘resolve on proxy’.