I run a VB script that searches a directory and emails
files. After a couple of days I notice that multiple
instances of the scheduler are in my system tray. The
job last less than 30 seconds. I have it asynchronous
in its own queue. What could be causing this? Runs as
an NT service on NT.

Each detached job displays an icon in the system tray. If you rest your mouse pointer over an icon it will display a help tip like "24x7 Scheduler job #256 -- my vb script"

The reason this icon doesn't disappear is either because the job hangs or you forcibly terminate the process and because of that 24x7 gets no chance to remove the job icon. If the job hangs you should see multiple instances of 24x7.exe in the Task Manager (Processes).

For jobs running less then 10 minutes I highly recommend using "synchronous" run option. This will eliminate the problem with multiple instances (you still need to figure out why the job hangs or terminates abnormally). Asynchronous option causes each asynchronous job to run in a separate background thread outside of the job queue.

: I run a VB script that searches a directory and emails
: files. After a couple of days I notice that multiple
: instances of the scheduler are in my system tray. The
: job last less than 30 seconds. I have it asynchronous
: in its own queue. What could be causing this? Runs as
: an NT service on NT.

Thanks.

Does Exit Sub quit the job if there are no more Procedures
to run? This scheduler will terminate the job, right? Or do
I need to use jalscript.execute "exit".

: Each detached job displays an icon in the system tray. If you rest your mouse
: pointer over an icon it will display a help tip like "24x7 Scheduler
: job #256 -- my vb script"

: The reason this icon doesn't disappear is either because the job hangs or you
: forcibly terminate the process and because of that 24x7 gets no chance to
: remove the job icon. If the job hangs you should see multiple instances of
: 24x7.exe in the Task Manager (Processes).

: For jobs running less then 10 minutes I highly recommend using
: "synchronous" run option. This will eliminate the problem with
: multiple instances (you still need to figure out why the job hangs or
: terminates abnormally). Asynchronous option causes each asynchronous job
: to run in a separate background thread outside of the job queue.

"Exit Sub" surely ends the script, which is not the end of a job process. If the job has no notification actions setup "on finish" event then 24x7 exists the job process. If the job looses system resources the process can hang on the system level. If you open any files, load nay COM objects, etc make sure to close/destroy them before Exit Sub.

Try version 3.4.21 that will be released today. This new version uses a different "terminate" method. Basically if it cannot quit gracefully it kills itself as a process.

: Thanks.

: Does Exit Sub quit the job if there are no more Procedures
: to run? This scheduler will terminate the job, right? Or do
: I need to use jalscript.execute "exit".