Job limit job pool option

The  Job Controller   option  relates to pool configuration, rather than channel configuration: it is set either for a specific Job Controller  , or if set directly under   it becomes the default for all pools which don&#x27;t explicitly specify a. The option&#x27;s (unsigned integer) value specifies the maximum number of jobs that a pool can execute in parallel. Execution of a request will use a UNIX process, so this corresponds to the maximum number of UNIX processes you allow a pool to use. The  applies to each pool individually; the maximum total number of jobs is the sum of the   parameters for all pools.

Note that multithreaded processes, e.g., the TCP/IP client program  and the Message Store delivery channel program , may run multiple threads within a single process, hence in that sense multiple "delivery jobs" within a process. The discussion of jobs here refers to job processes.

Setting  to 0 effectively stops a pool: it can&#x27;t process any requests.

See Job Controller default configuration for examples of  values.

Channel configuration normally specifies a pool for each channel to run in via the channel  option (or in legacy configuration via the   keyword on  each channel defined in the MTA configuration file,  ). By having different channels run in different pools, they can be kept from competing with each other. By grouping "related" channels to run in the same pool, they can share (compete) for resources (processing slots) amongst each other, while not being allowed to compete for processing slots with those channel(s) running in other pools. Use of the   keyword on a channel can limit how much of the   of the pool that the channel runs in the channel is allowed to use; this is normally only of interest when multiple channels are running in the same pool, being used to limit how much of the pool&#x27;s   a particular channel is allowed to use.

In legacy configuration,  is set either within a &#x5b;POOL&#x5d; section, or globally at the top of the    file. If set outside of a section, it will be used as the default by any &#x5b;POOL&#x5d; section which doesn&#x27;t specify. This option is ignored inside of a &#x5b;CHANNEL&#x5d; section.

Note that the    utility may be used to change a channel&#x27;s effective   "on the fly".

See also:
 * maxjobs Option
 * TCPIP channels
 * ims-ms channels
 * cache -change utility
 * Job Controller options
 * Job Controller default configuration