I am afraid there is no easy way to do that. If you are running a detached script type job you can try killing it on the master scheduler side. The remote job should abort as soon as it completes executing the current command or system-level call. If you are running remote program type job you can try running another job to kill the launched process on the system level, but in order to do that you either need to know remote process ID (the number reported in the Task Manager) or run KillProcess utility to kill all processes with the same name. If it is a database type job you can kill database session on the database level : Hi, : Is there a way to terminate a job running remotely on a remote agent from the : master scheduler server : if you cannot get connected to the remote console ? : Thanks, : Jim
|