Async restrictions

Hi, I have a queue called "EmailOut" which I use for dynamically created outgoing email. I am currently creating a job for each email I have to send (from a list of about 1000) so I end up with 1000 jobs in the Dynamic Jobs folder (this works perfectly). The problem is I create each job as a Sync job so that I dont get 1000 jobs all running at the same time but my server could cope ith say 10 jobs running at the same time. Is their any way to specify a job limit for Async jobs or is their a better way to limit the number of jobs or do I just have to leave them as sequential jobs?

Thanks in advance for any help.

Nathan

Please make each dynamic job to delete itself after the execution so that you don't end up with thousands of aged jobs, which if not deleted would be just a unnecessary ballast and inflate job database file.

I think a better way would be to create a job to monitor some folder for new files. Have you other processes instead of creating a new job, create a new file in that folder with "instructions" for what to do, and make the monitoring job to pick the file, read it and email what is required.

Sorry, maybe I didnt explain this very well. I do in deed delete the jobs after they have completed which all works fine. The great thing about 24x7 will be in future when I have multiple remote agents so that I can have multiple servers processing a queue and with this in mind I created some VB code that creates lots of dynamic jobs in the queue thereby allow for multiple servers and agents in future. At the present time I am running these jobs in non async so each job gets processed in turn which is fine as it only takes about 6-8 minutees for all the jobs to complete on a single server but I was just wondering if their is any way to tell the 24x7 software that it can run say 5 queued jobs at the same time on each server thereby reducing the time it would take to process all of the jobs. In reality I can change my VB code to do this but I just wondered if it was possible to set a max async job limit per queue as I am sure this would be useful to others. Thanks for your help.

Sure. You can create multiple jobs queues and assign jobs for different agents/servers to different queues. In most simplistic scenario, you can create 5 queues - 1 for each agent; and assign jobs for each server to its own queue. Or in case if you need to run the same job on multiple agents, just submit it several times once for each queue. In the latest case you would need to implement extra 5 "steps" for getting dynamically created job submitted to 5 queues.

Note that jobs in different queues run completely independently and concurrently unless they are specifically linked using semaphore files or using some other similar method.

Brilliant, thanks for your prompt response and a great product.