Using the job queue feature in Automation suite, how would you set up jobs to run single thread? Thanks - Robert

Set them to run "synchronous" and put them into the same queue.

The queue advantage is that you can setup and use multiple queues.
Perhaps you can setup a separate queue for each job batch (of course if you have such batches).
Each batch can run independently and asynchronously while jobs within that batch/queue still run synchronously, one by one.

: Using the job queue feature in Automation suite, how would you set up jobs to
: run single thread? Thanks - Robert

: Set them to run "synchronous" and put them into the same queue.

: The queue advantage is that you can setup and use multiple queues.
: Perhaps you can setup a separate queue for each job batch (of course if you
: have such batches).
: Each batch can run independently and asynchronously while jobs within that
: batch/queue still run synchronously, one by one.

: Set them to run "synchronous" and put them into the same queue.

: The queue advantage is that you can setup and use multiple queues.
: Perhaps you can setup a separate queue for each job batch (of course if you
: have such batches).
: Each batch can run independently and asynchronously while jobs within that
: batch/queue still run synchronously, one by one.

How do you set up jobs to run synchronously in a job queue? What I have done is create a Job queue, then set up multiple jobs within the same queue to run detached. Thanks - Robert

Running "detached" or "regular" does not matter. To make a job synchronous simply uncheck "asynchronous job" check box (if it is checked) in the Job Wizard.

"Synchronous run" means that the control doesn't return to the queue until the job completes so that the next job cannot start (it will await in the queue) until the current job completes. This can be also called as a job stream, where jobs are executed non-simultaneously one by one, "first come, first served".

"Asynchronous run" means that a job runs in its own space and other jobs can run simultaneously in the same queue.

Each queue is virtually independent; having multiple queues is a sort of having multiple independent job schedulers in one package.

Using multiple queues allows you to have the maximum possible flexibility in what and how you want to run, of course if you have a need to implement multiple job streams. If not, then using single queue might be sufficient in your case.

Good luck!

: How do you set up jobs to run synchronously in a job queue? What I have done
: is create a Job queue, then set up multiple jobs within the same queue to
: run detached. Thanks - Robert