Starting an IBM MQ queue manager is more than launching a process—it is recovery, repository load, and preparation for channels and applications. The strmqm command on distributed platforms and started-task automation on z/OS bring the messaging engine online after planned maintenance or unplanned reboot. Beginners expect instant readiness; operators know the first start after a power loss may replay large logs while applications retry MQCONN. This page explains strmqm and automatic startup, internal startup phases, listener and channel initiation, verifying a healthy start with DISPLAY QMSTATUS and dspmq, common failures (permissions, disk full, corrupt log), and coordination with application startup order in enterprise batches.
Run strmqm QMGRNAME as the mqm user or equivalent. The command returns when the queue manager is starting; use dspmq or DISPLAY QMSTATUS to confirm RUNNING. If the queue manager was the default installation manager, some environments use strmqm without a name. Custom data paths from crtmqm -ld and -md must exist and have correct ownership—startup fails fast with AMQ8001 series errors when paths are wrong.
| Command | Purpose |
|---|---|
| dspmq | List queue managers and status |
| dspmq -m QM1 | Status of one queue manager |
| echo DISPLAY QMSTATUS | runmqsc QM1 | MQSC status inside QM |
| runmqlsr -m QM1 -l LISTENER.TCP -t TCP | Start TCP listener |
| START CHANNEL(...) | Start sender/receiver channels |
Long recovery after kill -9 or power loss indicates unclean shutdown—pair with shutdown tutorial discipline.
Register queue manager with crtmqm set of flags or post-install scripts; on Linux systemd unit files may start strmqm. Windows services panel shows IBM MQ services. Ensure file systems mount before MQ starts (NFS or SAN volumes). z/OS automation starts the queue manager address space before CICS regions that depend on MQ in many estates—job scheduling documents the order.
DEFINE LISTENER and START LISTENER (or runmqlsr) open ports for remote queue managers and clients. Sender channels may START CHANNEL automatically via channel triggering or operations scripts. After startup, verify DISPLAY LSSTATUS and DISPLAY CHSTATUS—BINDING or RUNNING states show healthy paths. TLS channels need keystores readable at listener and channel start.
Best practice: queue manager and listeners ready before application servers fire hundreds of MQCONN. Spring and Java EE containers may retry connections—tune retry to avoid log storms. Batch jobs scheduled at 00:01 should depend on MQ health checks. CICS regions may delay cold start until MQ is available on the same LPAR or channel path.
123456strmqm QM1 dspmq -m QM1 echo "DISPLAY QMSTATUS" | runmqsc QM1 START LISTENER(LISTENER.TCP) START CHANNEL(TO.PARTNER) * Test: runmqsc, DEFINE QLOCAL test, put/get sample
The library opens in the morning: staff unlock doors (strmqm), put returned books back on shelves from the overnight cart (log recovery), turn on the front desk computer (command server), and open the return slot (listener). Until then, you cannot drop off books.
After strmqm, which three checks prove readiness for remote clients?
Listener starts before strmqm. What happens?
Why is first start after kill -9 slower than after endmqm?
1. strmqm is used to:
2. After unclean shutdown, startup may:
3. Applications can connect when:
4. runmqlsr relates to: