Cluster Sender Channels

IBM MQ clusters group queue managers so applications can put to a queue name without hard-coding which physical machine owns it. Cluster sender channels (CHLTYPE CLUSSDR) are the outbound pipes that connect one member to another's cluster receiver, exchange repository updates, and move messages along cluster-selected paths. If you have only worked with point-to-point SDR/RCVR pairs, CLUSSDR looks familiar—CONNAME, TRPTYPE, MCAUSER—but the naming, quantity, and relationship to CLUSQMGR and the repository differ. This tutorial explains what CLUSSDR does, how it differs from SDR, how to define channels between two members, how cluster workload uses those links, and what operators monitor when cluster routing fails while local puts still work.

Clusters Need Many Pipes, Not One

A two-queue-manager cluster might define CLUSSDR on QM_A to QM_B and another CLUSSDR on QM_B to QM_A, each targeting the partner's CLUSRCVR and listener. Larger clusters grow a mesh or hub pattern of channels. Repository queue managers (full or partial) aggregate knowledge of which queues exist on which members. When you ALTER QLOCAL CLUSTER('PAYMENTS'), members learn the name through repository flow carried over cluster channels—not through manual remote queue definitions on every machine. CLUSSDR is therefore part of your platform topology, not an application integration afterthought.

Defining Cluster Sender Channels

1
2
3
4
5
6
7
8
9
10
* On QM_LONDON — sender to QM_PARIS cluster receiver
DEFINE CHANNEL('QM_PARIS') CHLTYPE(CLUSSDR) TRPTYPE(TCP) +
  CONNAME('qm_paris.corp(1414)') CLUSTER('INVENTORY') +
  MCAUSER('mqm') HBINT(300)
* On QM_PARIS — matching cluster receiver (name often matches partner QM)
DEFINE CHANNEL('QM_LONDON') CHLTYPE(CLUSRCVR) TRPTYPE(TCP) +
  CLUSTER('INVENTORY') MCAUSER('mqm')
DEFINE LISTENER('CLUSRV') TRPTYPE(TCP) PORT(1414)
START LISTENER('CLUSRV')
START CHANNEL('QM_PARIS')

CLUSTER('INVENTORY') ties the channel definition to the cluster name also used on CLUSQMGR and queue CLUSTER attributes. Channel names often mirror partner queue manager names for clarity, but what matters is consistent pairing: CLUSSDR on A targets CLUSRCVR on B with CONNAME reaching B's listener. MCAUSER must be authorized for puts on cluster-exposed queues and for protocol needs on each platform. On z/OS, review security profiles alongside UNIX IDs used on distributed members.

Explainer: Neighborhood Bulletin Board

Think of the cluster as a neighborhood where every house needs a road to every other house to share news about who sells lemonade (cluster queues). CLUSSDR is the outbound lane from your house toward a neighbor's driveway (CLUSRCVR). When you announce a new lemonade stand (CLUSTER on a queue), you send flyers along those roads so everyone updates their map (repository).

Repository Traffic and Message Traffic

Cluster channels carry two broad categories of work: administrative cluster protocol (subscriptions to repository changes, queue manager status) and application messages forwarded when a put on one member targets a queue instance on another. Both share the same TCP session types governed by channel attributes—batching, heartbeat, TLS. A saturated CLUSSDR link affects repository freshness and message latency. Capacity planning should include cluster channel count and message volume, not only point-to-point interfaces.

Workload Management Interaction

When multiple instances of a cluster queue exist, the cluster workload algorithm chooses which member receives the message. CLWLUSEQ, CLWLRANK, and network priority attributes influence whether the local instance wins. CLUSSDR must be RUNNING to partners that host the chosen instance; otherwise puts fail or reroute depending on DEFBIND and cluster configuration. Operators who tune only queue attributes without checking channel health see intermittent “works on QM2 but not QM1” reports.

Starting and Monitoring CLUSSDR

Cluster channels may start automatically when the queue manager joins the cluster or when traffic demands. DISPLAY CHSTATUS shows instances in RUNNING, BINDING, or RETRY. DISPLAY CLUSQMGR and repository commands help verify membership. Compare MSGS and BYTES on CLUSSDR with application put rates during tests. After adding a new member, verify new CLUSSDR/CLUSRCVR pairs exist to all required peers—partial mesh leaves blind spots in routing tables.

TLS, CHLAUTH, and Multi-Platform Clusters

• Apply consistent TLS policies across z/OS, Linux, and Windows members—cipher mismatch blocks BINDING.
• CHLAUTH rules should reference cluster channel names or certificate DNs agreed in standards.
• NAT and firewalls between data centers must allow return traffic for established TCP sessions.
• Document which listener ports serve cluster traffic versus application SVRCONN traffic.

Troubleshooting Cluster Senders

1. DISPLAY CHSTATUS for CLUSSDR—RETRY indicates connect or protocol failure.
2. Ping CONNAME host and port from the sending host OS, not only from MQ commands.
3. Verify partner CLUSRCVR name and CLUSTER attribute match your design.
4. Check repository availability on full repository queue managers.
5. Review error logs for sequence number or SSL handshake errors after failover.

When to Prefer Point-to-Point SDR

Clusters simplify naming and horizontal scale; they add operational surface area. Fixed partner links with explicit remote queues and SDR/RCVR remain valid for stable hub-and-spoke feeds where cluster semantics are unnecessary. Do not define CLUSSDR between queue managers that are not cluster members—use SDR instead.

Explain Like I'm Five: Cluster Sender Channels

Cluster sender channels are the paths your queue manager uses to drive messages and cluster news to other queue managers in the same club so everyone knows which queues live where.

Practice Exercises

Exercise 1

Write MQSC for CLUSSDR and partner CLUSRCVR between two fictional queue managers in cluster STOCK.

Exercise 2

List three symptoms users report when CLUSSDR to the repository host is in RETRY.

Exercise 3

Compare one advantage and one disadvantage of cluster channels versus a single SDR/RCVR pair.

Frequently Asked Questions

Test Your Knowledge