Use mqsistart to start a WebSphere Message Broker component. If the queue manager associated with this component (defined in the corresponding create command) is not already running, it is also started by this command. However, no listeners, channels, or channel initiators associated with the started component are started. If you have WebSphere MQ Version 6.0 installed, use the WebSphere MQ Explorer to start any required listeners, channels, or channel initiators. For earlier supported versions of WebSphere MQ, use the WebSphere MQ Services snap-in.
Successful completion of this command indicates that the Windows service, or Linux or UNIX daemon has started successfully, and that the component startup has been initiated. Check the Windows system event log or the Linux or UNIX syslog to determine if the component and all related software have started successfully, are initially active, and remain in an active state. Any errors that have prevented successful startup, that are detected by the component, are recorded in the log. Continue to monitor the Windows system event log or Linux or UNIX syslog.
On Windows platforms, the queue manager is not started as a service and stops if you log off. To avoid this happening, either remain logged on, or change the startup status of the queue manager service as described in Creating a Configuration Manager on Windows. (If you lock your workstation, the queue manager does not stop).
All of the names are case sensitive on Linux and UNIX systems.
Do not use the mqsistop command on a DatabaseInstanceMgr unless you are using the Derby database.