Cluster Channels

Cluster channels are the TCP pipes between queue managers that belong to the same IBM MQ cluster. While point-to-point SDR and RCVR channels implement explicitly designed routes between named partners, CLUSSDR and CLUSRCVR channels implement the cluster fabric: carrying application messages to remote instances of cluster queues, synchronizing repository data between full and partial members, and supporting cluster pub/sub propagation. Beginners conflate cluster channels with client channels—SVRCONN is for applications; CLUSSDR is queue manager infrastructure. Misconfigured CONNAME on one CLUSRCVR can break routing for dozens of logical queues. This tutorial explains channel types, manual DEFINE versus automatic creation, CLUSTER attribute, pairing and naming, TLS and CHLAUTH, DISPLAY CHSTATUS monitoring, capacity and retry behavior, and how cluster channels relate to cluster sender and cluster receiver dedicated pages.

CLUSSDR and CLUSRCVR Roles

Defining Cluster Channels Manually

1
2
3
4
5
6
7
DEFINE CHANNEL('QM_LON.QM_NYC') CHLTYPE(CLUSSDR) TRPTYPE(TCP) +
  CONNAME('nyc.example.com(1414)') CLUSTER('SALES') HBINT(300)
DEFINE CHANNEL('QM_LON.QM_NYC') CHLTYPE(CLUSRCVR) TRPTYPE(TCP) +
  CLUSTER('SALES') HBINT(300)
* On QM_NYC reciprocal CLUSSDR points to lon.example.com
START CHANNEL('QM_LON.QM_NYC') CHLTYPE(CLUSSDR)
DISPLAY CHSTATUS('QM_LON.QM_NYC') CHLTYPE(CLUSSDR)

Channel names often match between partners for clarity; IBM auto creation uses queue manager name conventions. CLUSTER('SALES') must match queue and QM cluster membership. Listener on CLUSRCVR port must be running—cluster receivers share listener infrastructure with RCVR and SVRCONN on many systems.

Automatic Versus Manual Channels

Automatic channel creation defines CLUSSDR when workload first routes to a member without an existing path—see automatic channel creation tutorial. Manual definitions suit locked-down networks and explicit SSL profiles. DISPLAY CHANNEL WHERE(CHLTYPE EQ CLUSSDR) after cluster growth reveals auto additions—govern with change control tags in DESCR field when your process requires it.

Security on Cluster Channels

• CHLAUTH QMGRMAP — allow known partner queue manager names only.
• TLS — encrypt cluster traffic; mutual TLS in zero-trust designs.
• MCAUSER — least privilege; cluster puts use delivery context per IBM rules.
• Firewall — permit cluster listener ports between all member subnets.
• No anonymous wide open CLUSRCVR on internet-facing hosts.

Monitoring and Troubleshooting

DISPLAY CHSTATUS shows RUNNING, BINDING, RETRY, or INACTIVE. Cluster put failures with reason 2xxx or channel errors often trace to CLUSSDR in RETRY—wrong CONNAME, certificate mismatch, or firewall. Sequence number errors after restore require RESET CHANNEL on both sides per IBM procedures. High MSGS counts on few CLUSSDR instances indicate hub routing—watch for channel max instances limits on busy members.

Cluster Channels vs Repository Traffic

Same channels may carry both application messages and repository synchronization depending on release and configuration—do not assume tiny message volume. Repository storms after bulk DEFINE can spike channel bytes briefly. Separate clusters (different cluster names) should not share channel definitions—CLUSTER attribute mismatch causes cross-talk confusion.

Explainer: Dedicated Lanes Between Warehouses

Cluster channels are dedicated truck lanes between warehouses in the same shipping network (cluster). Client channels are customer drop-off desks at the front door—different purpose, different rules.

Explain Like I'm Five: Cluster Channels

Cluster channels are the roads only school buses use to drive between schools in the same district—not the roads parents use to drop off kids at one school.

Practice Exercises

Exercise 1

Write MQSC for CLUSSDR plus CLUSRCVR pair between QM_A and QM_B in cluster PAY.

Exercise 2

CLUSSDR in RETRY—list five checks.

Exercise 3

How do cluster channels differ from SVRCONN?

Frequently Asked Questions

Test Your Knowledge