If it is program type job, kill the system process (using Task Manager or other tool). If it is a database SQL job, kill the database session (on the database level) or run the job detached (see next for details). If it is a script type job run it detached then you can kill it on the system level as a process. By the way, version 3.4.8 is pretty old. Consider upgrading to a more recent version, the upgrade is free. : Greetings, : If a job is stuck in the queue or mus otherwise be terminated, how do you do : it withoug shutting down either the master scheduler or the agent? This is : getting to be pretty annoying for us here. We are running Version 3.4.8 in : a master/slave configuration. : Is there a fix to this problem? If a job is stuck in the queue, the only way : to clear the queue is to restart the scheduler. This is not a normal way : to do things. Is there a way to kill an existing spawned process wihtout : doing a shutdown?
|