Use the mqsistart command to start a broker.
If the queue manager associated with this broker (defined by the mqsicreatebroker command) is not already running, it is also started by this command. However, no listeners, channels, or channel initiators associated with the started broker are started. Use WebSphere® MQ Explorer to start any required listeners, channels, or channel initiators.
Successful completion of this command indicates that the Windows service, or Linux or UNIX daemon, has started successfully, and that the broker startup has been initiated. Check the Windows system event log or the Linux or UNIX syslog to determine if the broker and all related software have started successfully, are initially active, and remain in an active state.
All errors that have prevented successful startup, that are detected by the broker, 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 Starting a WebSphere MQ queue manager as a Windows service. (If you lock your workstation, the queue manager does not stop).
On Linux and UNIX systems, all names are case sensitive.
mqsistart IB9NODE