1 of 1 people found this helpful
It’s entirely random, unless you setup the job routing rules so that the job will always run on a specific appserver.
I found the rules, didn't know about them. Is there a way to know which appServer is running a NSH Script Job once that has been launched?
If you don’t use the rules to send a job to a certain appserver, after the job starts running you can look in the job run log to see which appserver picked up the job, and the work item thread(s) associated w/ the job.
In the log you will see a message like: ‘running job xxx on appserver yyy’ and ‘running work item thread for job xxx on appserver yyy’. If you have multiple targets for the job and it’s not a type 2 nsh job, then you may have multiple appservers involved w/ running the job.