Startup utility

Start the MTA Job Controller and the MTA Dispatcher.

Syntax
imsimta startup &#x5b;component&#x5d;

Restrictions
Must have superuser privileges or use the Solaris RBAC feature in order to use this utility.

Optional parameter which specifies a specific MTA component to be started:   or. If no component name is given, then all active components will be started.

Description
The  utility starts up detached MTA  processes. If no component parameter is specified, then the MTA Job Controller  and MTA Dispatcher are started. Note that starting the Dispatcher starts all services  the Dispatcher is configured to handle,  which may include, for instance, SMTP,  SMTP SUBMIT, or  LMTP servers. If a component parameter is specified, then only detached process  associated with that component will be started. The standard component names are:

Note that the services handled by the MTA Dispatcher must be started by  starting (or restarting)   the Dispatcher itself; only services not being  handled by the Dispatcher can be individually started via the    utility. (The Dispatcher may be configured to handle various services, e.g., the SMTP,  SMTP SUBMIT, and  LMTP servers; see  Dispatcher options for details.) Thus if adding a new service under the Dispatcher, or to reenable execution of a previously shutdown service which runs under the Dispatcher, on a running system you must  restart the Dispatcher itself.

Since in Messaging Server usage, the overall Messaging Server startup command, , is normally used to start up not only  the MTA but also other components of Messaging Server, the MTA-specific    command is seldom used nowadays.

Examples
Starting dispatcher server ... 29034 Starting job_controller server. 29045 The above shows the sort of output shown as of  MS 6.3,  which includes the pids of the started Dispatcher and Job  Controller processes. dispatcher server is running already job_controller server is running already The above shows the sort of output issued in MS 6.3  if a   command is  issued when the MTA&#x27;s Dispatcher and Job Controller were already  running.
 * 1) imsimta startup
 * 1) imsimta startup

Error messages
Attempting to start up the Dispatcher when it is already running, or the Job Controller when it is already running, will be reported as an error to : dispatcher server is running already job_controller server is running already

See also:
 * Job Controller
 * Dispatcher
 * Service group
 * SMTP SUBMIT servers
 * LMTP back end TCPIP channel
 * restart utility
 * MTA command line utilities