I have a new job scheduled that runs all day(using JAL). It was running fine for a couple days but this weekend the queue filed up with a bunch of 1K files. So it quit running because the queue filled up. What are these files in the queue directory? Any ideas? Thanks!

These small files contain job definitions.
Most likely your job does not complete and more an more job instances get added to the queue. Try restarting the scheduler if this will happen again review your job definition. If you are running an external program or batch file set the job to run synchronous and set resable timeout so that the scheduler can forcedly terminate the job if it does not complete on time.

: I have a new job scheduled that runs all day(using JAL). It was running fine
: for a couple days but this weekend the queue filed up with a bunch of 1K
: files. So it quit running because the queue filled up. What are these
: files in the queue directory? Any ideas? Thanks!

It is JAL running a VB program calling SQL Server...I bet it is timing out once in a while. Is there any way to check the queue size using JAL(or other way) until I can figure out the problem?? I would like to be notified if it fills up. Thanks!

: These small files contain job definitions.
: Most likely your job does not complete and more an more job instances get
: added to the queue. Try restarting the scheduler if this will happen again
: review your job definition. If you are running an external program or
: batch file set the job to run synchronous and set resable timeout so that
: the scheduler can forcedly terminate the job if it does not complete on
: time.

You can make a job that periodically checks the total size of all files in the queue directory C:\Program Files\24x7 Scheduler\Queue\[queue name here]

You can also increase the queue size, but I am not sure if this will help to resolve the problem. Anyway, use Tools/Options/Job Queues option to configure queue properties.

A real workaround for this situation could be the following:
Create two jobs - the "worker" and the "caller". The worker job would have the VBScript and for the schedule. The caller job would have the desired schedule and type of "run program". For the command line use "24x7 /JOB worker". The caller job should be synchronious and have maximum timeout, so it kills the worker job if it does not complete in the specified time.

: It is JAL running a VB program calling SQL Server...I bet it is timing out
: once in a while. Is there any way to check the queue size using JAL(or
: other way) until I can figure out the problem?? I would like to be
: notified if it fills up. Thanks!

I'm trying to figure out the command line syntax to run another job as you suggested below. I tried a bunch of different way but no luck. Thanks!

: You can make a job that periodically checks the total size of all files in
: the queue directory C:\Program Files\24x7 Scheduler\Queue\[queue name
: here]

: You can also increase the queue size, but I am not sure if this will help to
: resolve the problem. Anyway, use Tools/Options/Job Queues option to
: configure queue properties.

: A real workaround for this situation could be the following: Create two jobs
: - the "worker" and the "caller". The worker job would
: have the VBScript and for the schedule. The caller job would have the
: desired schedule and type of "run program". For the command line
: use "24x7 /JOB worker". The caller job should be synchronious
: and have maximum timeout, so it kills the worker job if it does not
: complete in the specified time.