DB2 Version 9.7 for Linux, UNIX, and Windows
DB2 Version 9.7 for Linux, UNIX, and Windows
Some thresholds have a built-in queue and permit you to enforce how many activities can execute concurrently by queuing all additional activities once the concurrency limit is reached, up until the set limit for the queue is exceeded.
When an activity violates the threshold boundary of a queuing threshold, new work requests are queued automatically in a first-in, first-out fashion, until the queue reaches the size specified by the queuing boundary. When the queue is full, the upper boundary is reached, and the action specified for the threshold is applied to any newly arriving work being tracked by that threshold. For example, an action of STOP EXECUTION causes the newly arriving work to be rejected.
You can also define the upper queuing boundary as being unbounded, in which case there is no upper limit to the size of the queue. In this situation, newly arriving work is added to the queue. If you define a hard limit for the upper boundary and define an action of CONTINUE as the threshold action, all newly arriving work that violates the threshold boundary is added to the queue, and the threshold behaves as if its queuing boundary were unbounded.