Run utility

Process messages in a specified channel.

Syntax
imsimta run ''channel &#x5b;poll-flag &#x5b;start-time &#x5b;start-id &#x5b;channel-specific-argument &#x5b;name-filter &#x5b;min-priority:max-priority&#x5d;&#x5d;&#x5d;&#x5d;&#x5d;&#x5d;''

Restrictions
Must be the MTA user (see the  option in  ), or have superuser privileges (in which case the MTA will automatically become the MTA user) in order to use this utility.

This parameter specifies the channel to be processed.

Valid values for   are  or its  synonym   (the default), , or. By default, if neither  nor    is specified, then only the master direction of the  channel will be run. If  is specified, then first the  master and then the slave directions of the channel will be run. If   is specified, then only the slave direction of the  channel will be run.

This parameter is of historical interest only, and has no effect when the Job Controller is in use.

This parameter is of historical interest only, and has no effect when the Job Controller is in use.

This parameter is of historical interest only, and has no effect when the Job Controller is in use.

This parameter has no effect.

For TCP/IP channel master jobs and for    channel jobs, the    may be used to specify a message file name filter  and/or a (destination) host name filter, using the syntax file-name-filter@host-name-filter This parameter is not respected by other channels.

This parameter is of historical interest only, and has no effect when the Job Controller is in use.

Description
The  utility processes the messages in the  channel specified by the   parameter.

In order to run the channel "outside" normal Job Controller  processing (and the Job Controller&#x27;s normal limits on job  creation---that being one of the reasons that    is sometimes used, to force execution of a channel that the Job  Controller would not normally want to run at that moment), a sort of  light-weight, pseudo-Job Controller runs in your process, and it then  forks   the actual channel job. So some Job Controller-like output (Job Controller error output, or debug output if  you have  Job Controller debugging enabled)  may be output at your  terminal, and your terminal will be "tied up" for the  duration of the operation of the utility, though the actual channel  execution will be forked to a child process (which if  channel debugging  is enabled, will write its own debug log file, as usual).

See also the  utility (or synonymous   utility),  which, unlike ,  submits a request to start a job to the Job Controller (and the Job  Controller then forks the actual channel job, as appropriate), so these  other commands will not tie up your terminal.

As alluded to above, one of the typical purposes of using  is to start up an "extra" channel processing job,  exempt from both the Job Controller&#x27;s usual rules for triggering  creation of a new job, and its configured limits on creation of channel  processing jobs. As of MS 6.3, the  utility  will also trigger a new job creation (be exempt from the usual rules  for triggering creation of a channel job), though only within the Job  Controller&#x27;s configured limit on the maximum number of channel  processing jobs allowed. That is, either  or     may be used to attempt to trigger an  "additional" channel job---but only    guarantees that the request will in fact result in another job  (possibly an "extra" job beyond the Job Controller&#x27;s  configured limits on numbers of jobs). Triggering creation of another job might be desired, for instance, when attempting to process a  "large" backlog of messages; and creation of an  "extra" job (beyond the usual    and    limits) via    might be desired when  you know that you want "extra" jobs beyond the Job  Controller&#x27;s configured limits.

Note that since  is using special routines to  simulate Job Controller channel job creation from within your own  process, it is not typically useful for purposes of viewing/debugging  actual Job Controller operation.

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

See also:
 * Job Controller
 * TCPIP channels
 * ims-ms channels
 * maxjobs Option
 * job_limit Option
 * submit utility
 * MTA command line utilities