Channel status tells operators whether distributed IBM MQ can move messages between queue managers right now. A payment hub may show healthy queue depths locally while a sender channel sits in RETRYING—funds messages pile on the transmission queue invisible to teams watching only application queues. DISPLAY CHSTATUS is the authoritative MQSC view; Prometheus exporters and APM tools like Instana and Dynatrace surface the same states as metrics for paging and trends. This tutorial explains channel instance versus definition, common CHSTATUS values and what each means for operations, monitoring sender versus receiver versus server-connection channels, mapping status codes in metrics systems, alert design for not RUNNING conditions, pairing channel status with XMITQ depth and listener health, and beginner troubleshooting when status flaps during network or TLS changes.
DEFINE CHANNEL creates PARIS.TO.LONDON with CHLTYPE(SDR) and attributes like CONNAME and XMITQ. Starting the channel or automatic start when messages arrive creates an instance recorded in CHSTATUS. Multiple instances can exist for some channel types in advanced scenarios; beginners focus on one SDR instance per name per queue manager. If CHSTATUS shows no instance, the channel may be INACTIVE—not an error if no messages trigger start and policy uses trigger or manual START.
| Status | Meaning | Typical action |
|---|---|---|
| INACTIVE | No active instance | START if work pending; else normal idle |
| BINDING | TCP/TLS handshake in progress | Wait briefly; check TLS and firewall if stuck |
| RUNNING | Session up, messages can flow | None if MSGS moving; verify rates |
| RETRYING | Failed connect or break; retry timer active | Check partner listener, CHLAUTH, sequence numbers |
| STOPPED | Stopped by operator or error | Read AMQERR, RESET CHANNEL if needed, fix root cause |
| PAUSED | Flow paused by operator command | RESUME when maintenance complete |
12345678DISPLAY CHSTATUS('PARIS.TO.LONDON') ALL * Key fields for monitoring: * STATUS — RUNNING, RETRYING, etc. * CHTYPE — SDR, RCVR, SVRCONN, etc. * MSGS — messages sent or received on instance (direction depends on type) * BYTES — volume indicator * LASTMSGDT — time of last message (staleness check) * CONNAME — partner address for outbound types
Run DISPLAY CHSTATUS on both queue managers during incidents. Sender RETRYING on QM_PARIS while receiver shows no BINDING attempt suggests firewall blocking outbound CONNAME or wrong port. Receiver BINDING forever with sender RUNNING may be CHLAUTH on inbound MCAUSER.
Do not alert on every test channel in RETRY left intentionally down in development. Tag objects in documentation or use separate queue managers for non-production noise isolation.
Exporters translate STATUS to integers for PromQL comparisons. Document the mapping in your runbook: for example 2 equals RUNNING in a given exporter version—never assume across versions without checking release notes. Grafana stat panels color red when status not equal RUNNING for channel label in tier1 list. Combine with ibmmq_channel_msgs_total rate to detect zombie RUNNING sessions that are up but not moving messages—status green but MSGS flat while XMITQ grows suggests stuck protocol or inhibited puts.
Channel events to the event queue can notify on state changes when CHINT and event configuration enable them—useful when scrape interval is sixty seconds and you need faster notification on STOPPED. Channel accounting records give historical bytes and batch counts for capacity planning, complementing real-time CHSTATUS metrics.
Planned STOP CHANNEL during certificate rotation should silence alerts in Alertmanager or Grafana for the maintenance window. Document expected BINDING duration during TLS renegotiation tests so NOC does not escalate brief yellow states. After DR failover, channels may need RESET CHANNEL and sequence number alignment—status may show STOPPED until operators complete runbook steps.
Channel status is the ramp meter light on the freeway on-ramp—RUNNING means cars merge; RETRYING means the meter keeps flashing red because the merge failed; XMITQ is cars stacked on the ramp.
Channel status is whether the tunnel between two toy rooms is open, closing, or broken. If it is broken, toys pile up in the tunnel entrance waiting room (transmission queue).
Write an alert rule in plain English: SDR PAY.TO.HUB not RUNNING for five minutes, severity critical.
Given RUNNING but XMITQ depth rising for one hour, list four checks beyond restarting the channel.
Map five CHSTATUS values to colors for a NOC dashboard legend.
1. Healthy transferring sender channel status is usually:
2. DISPLAY CHSTATUS shows:
3. RETRYING status often means:
4. When SDR not RUNNING, check XMITQ because: