Are you having any Job routing rules?
Yes i have 4 Application Server type JOB, so Job are potentialy executed on on e of the four Application server.
I don't want to discriminate application server, i just want when a job is executed on one aplication server, only its WorkItemThreads are used.
A little more details, in fact we have an issue with a shared NFS mount.
When two application server (separate physical server) use the NFS client to write in the same file, the file is corrupted.
So i want a temporary workaround to force bladelogic to use ressources only on the application server where the job is executed.
There is no way to disable work item sharing, that was removed in 8.2. why do you want to disable it? what is this issue w/ NFS writing the same file ? what file ? why will limiting what appserver a job's WIT runs on solve your problem ?
Because when i'm lauching a job (NSH script job type runscript) on 4000 server and my job is configured to run on 150 procs in parallel, the workitemthread of the other application server are used.
I have to seprate physical server, two instance of application server type job are runinf on the first server, two others on the second server. Output of the job is writing to a unique file on the NFS mounted file system.
And when two NFS client are wirting on the same file -> file is corrupted.
So i d'like to desactivate the workitemthread share....But regarding reply of Bill, we can't do this anymore.
So don’t write to the same file ? I mean, if you have multiple WIT writing to the same file concurrently from one appserver, I don’t see how the file is not being corrupted in that case.