When the Job Scheduler agent attempts to connect to an instance to execute a scheduled job and the instance is too busy, the Workload Manager may redirect the connection to another instance, so any instance in the cluster can perform the scheduled jobs. This happens automatically and does not require you to reconfigure Job Scheduler.
Generally speaking, the Workload Manager takes care of login redirection. You can affect how connections are redirected by setting rules at the logical cluster level. However, if you do not want a scheduled job to be redirected, set the new job property that allows redirection:
From Adaptive Server plug-in – unselect the Allow Redirection option in the Job Properties dialog box.
The default behavior is to allow the Workload Manager to redirect a scheduled job connection according to the workload rules that exist at the time the connection is made.
From the command line – set the redirection property no_conn_redirection when you create or modify a job. For example, to set the property for a job named find_old_logins using sp_sjobcreate, enter:
sp_sjobcreate @name='jname=find_old_logins', @option='jcmd=exec sp_find_old_logins,jproperties=no_conn_redirection=true'
