Detached/attached has nothing to do with queue blocking. This simply controls where the code is executed. Attached jobs execute in the memory space of the scheduling engine process (not recommended), detached - execute as a separate OS process. What affects the queue usage is job synchronous/asynchronous mode. Asynchronous jobs start and run in the background releasing the queue after start, while synchronous jobs run in the queue foreground until they are done and then release the queue. This is all pretty well documented with flow charts in the docs. It is recommended that use synchronous jobs whenever possible. If needed to run multiple jobs concurrently, use multiple queues and assign different applications (or job streams) to different queues. : Hi, : Does a "detached job" running on a queue stop/block other jobs from : running on the queue? : Thank you, : Best Regards, : Soumitra
|