Submit master utility

Process messages in a specified channel.

Syntax
imsimta submit_master channel &#x5b;poll-flag &#x5b;host-pattern&#x5d;&#x5d;

Restrictions
Must have superuser privileges or be logged in as the MTA user (see the  option in  )  in order to use this utility.

This required parameter specifies the channel to be processed.

Valid values for   are  or its  synonym   (the default), , or. By default, if neither  nor    is specified, the  Job Controller will be requested  to perform only a master direction execution of the channel (and the  channel will not run unless there are actually messages waiting to be  processed in that channel, whose    has expired). If   is specified, the Job Controller will be requested to  perform both master and slave direction executions of the channel. If   is specified, the Job Controller will be requested  to perform only a slave direction execution of the channel.

Specify a hostname for which to deliver. (This is not relevant for all channels, but for outgoing TCP/IP channels  marked with the    channel option, where the Job Controller  maintains separate delivery queues for each distinct destination host,  this parameter specifies which messages to consider delivering.)

Description
The  utility requests that the  Job Controller begin (consider beginning) a  delivery job for the specified channel.

Note that stopped channels (  utility&#x27;s    command) will not be run. And if there are already more than twice the    requests to run the channel,  then this additional request will be ignored. A request will also be ignored if the backlog of messages in the channel queue area is smaller  than the number of already executing jobs for that channel times the    for the channel  (unless there is only one  executing job, in which case another job will be started). Note that the channel&#x27;s    values will be respected in  determing which, if any, messages to process. Thus it is rare that the   utility is of much interest: generally, the  Job Controller&#x27;s intrinsic scheduling will already have started the  maximum-appropriate-for-the-moment number of processing jobs for the  channel, and so an   command will have no  immediate effect (other than causing the Job Controller to run through  its checks before deciding that this additional request should be  ignored). Since a limited (by ) number of such  requests will be kept pending, in the medium term this utility may be  used to attempt to influence the Job Controller to more aggressively  schedule delivery of one destination host over another (within the same  channel), via the   parameter; as the originally  existing jobs terminate, the pending requests can begin to be honored.

See also the synonymous  utility, and the    utility,  which runs at your terminal outside  the Job Controller&#x27;s normally scheduling limits and checks (for  instance, disregarding   conditions), rather than  running as a regular Job Controller child process.

,  (default)
By default, the submitted job only considers and attempts processing of newly-submitted (have not yet received a  delivery attempt) messages. To request delivery attempts for "old" messages (those that have already received one or more delivery  attempts), use.

Examples
The above UNIX command may be used to process any messages in the   channel.
 * 1) imsimta submit_master tcp_local poll

See also:
 * Channels
 * Job Controller
 * backoff Option
 * TCPIP channels
 * single_sys Option
 * qm utility
 * maxjobs Option
 * threaddepth Option
 * run utility
 * Typical TCPIP channels and servers
 * MTA command line utilities