The strmqm command can be used to start a queue manager. In this example, the queue manager named MANAGER01 is started.

strmqm MANAGER01

Something like this should be displayed.

IBM MQ queue manager 'MANAGER01' starting.
The queue manager is associated with installation 'Installation1'.
6 log records accessed on queue manager 'MANAGER01' during the log replay phase.
Log replay for queue manager 'MANAGER01' complete.
Transaction manager state recovered for queue manager 'MANAGER01'.
IBM MQ queue manager 'MANAGER01' started using V9.1.0.3.

The dspmq command can be used to determine if the queue manager is running.

QMNAME(MANAGER01)    STATUS(Running)

And the queue manager log should contain the following event.

AMQ8352I: IBM MQ queue manager 'MANAGER01' becoming the active instance.
AMQ8003I: IBM MQ queue manager 'MANAGER01' started using V9.1.0.8.

Clustered queue managers

Let's say you have 2 queue managers, where the queue manager on server1.example.com should be the active queue manager and the queue manager on server2.example.com should be the standby queue manager. In this scenario, you will first want to start the queue manager on server1.example.com, using the -x option.

[mqm@server1 ~] strmqm -x MANAGER01

Then start the queue manager on server2.example.com.

[mqm@server2 ~] strmqm -x MANAGER01

In this scenario, the queue manager on server1.example.com should have a status of running.

[mqm@server1 ~] dspmq
QMNAME(MANAGER01)    STATUS(Running)

And the queue manager on server2.example.com should have a status of running as standby.

[mqm@server2 ~] dspmq
QMNAME(MANAGER01)    STATUS(Running as standby)

And the queue manager log should contain the following event.

AMQ8060I: IBM MQ queue manager 'MANAGER01' started as a standby instance.

Be aware that even when the dspmq command returns "running", the systemctl command or service commands may show that the queue manager is not running.

Job for example.service failed because the control process exited with error code. See "systemctl status example.service" and "journalctl -xe" for details.

If your system is using systemd, use the systemctl command to start and enable the queue manager.

systemctl enable MANAGER01
systemctl start MANAGER01
systemctl status MANAGER01

If your system is using init, use the chkconfig and service commands to start and enable the queue manager.

chkconfig MANAGER01 on
service MANAGER01 start
service MANAGER01 status

The qmstatus command can be used to show when the queue manager was started.

echo "display qmstatus startda startti" | runmqsc MANAGER01
. . .
QMNAME(MANAGER01)                       STATUS(Running)
STARTDA(2021-02-25)                     STARTTI(21.30.58)