Point-to-point channels that sit in RETRY are painful; a stuck cluster channel can be worse because one CLUSSDR instance between a partial member and a full repository may block catalog updates, auto-definition of further paths, and every cluster put that needs a remote instance. Operators see DISPLAY CHSTATUS showing BINDING for hours on QM_APP1.QM_REPO while CURDEPTH on cluster transmission-related queues grows, or cluster puts fail with reason codes tied to unavailable destination while CLUSCH shows channels that never leave STARTING. Cluster channels share the same TCP, TLS, CHLAUTH, and sequence number failure modes as SDR and RCVR, but troubleshooting must include repository role, auto-defined names, and whether multiple clusters share a listener port. This tutorial covers stuck CLUSSDR and CLUSRCVR diagnosis, difference from the channel-stuck-in-retry page for general channels, STOP and RESET discipline, partner coordination, firewall and listener checks specific to cluster mesh, impact on cache and repository sync, and prevention through monitoring channel state to full repositories.
BINDING means the channel is attempting to establish a session—often listener unreachable, wrong port, or TLS handshake hang. RETRY means a failed attempt is cycling through SHORTRTY and LONGRTY timers—read LASTCHLERR and LASTCHLERRM for the repeating error. STARTING may appear briefly at activation; if permanent, investigate channel initiator or queue manager limits. RUNNING is healthy. INACTIVE after retries may mean exhaustion—do not assume the problem fixed itself. Compare STATUS on both ends when possible via operations bridge to partner team.
| Category | Examples | Fix direction |
|---|---|---|
| Network | Connection refused, timeout | Firewall, DNS, listener PORT |
| Security | CHLAUTH blocked, MCAUSER | CHLAUTH, CONNAUTH, certs |
| TLS | Cipher mismatch, expired cert | SSLCIPH, GSKit renewal |
| Sequence | Sequence error after restore | Coordinated RESET both sides |
| Definition | Wrong CONNAME from repo | Fix CLUSQMGR NETNAME, refresh |
12345678DISPLAY CHSTATUS('QM_APP1.QM_REPO') ALL DISPLAY CLUSCH('QM_APP1.QM_REPO') CLUSTER('SALES') ALL DISPLAY LSSTATUS(LISTENER.TCP) ALL * Partner queue manager: DISPLAY CHSTATUS('QM_REPO.QM_APP1') ALL * All cluster channels not RUNNING: DISPLAY CHSTATUS(*) WHERE(STATUS NE RUNNING) + WHERE(CHLTYPE EQ CLUSSDR)
CLUSCH shows repository-published definition including CONNAME and CLUSTER list. CHSTATUS shows the live instance. Mismatch—CLUSCH CONNAME hostA but DNS now points hostB after migration—explains endless BINDING. For auto-defined channels, note whether manual ALTER is allowed or will be overwritten on next repository publish.
While CLUSSDR to full repository is stuck, partial members may run on old cache—see cluster cache issues tutorial. Auto-defined channels to new members may not appear. Workload may hide instances on unreachable queue managers until channels RUNNING. Pub/sub cluster topics may stop propagating subscription updates. Prioritize repository paths in severity-1 incidents before application-only paths that have alternate full repository routes.
Cluster channels are highways between city halls that share the phone book. One closed highway means some towns never get updated phone books and cannot deliver mail to addresses they no longer know.
The tunnel between two playgrounds is blocked, so kids on one side never get the updated list of who moved to which playground—and they keep sending balls to the wrong place.
CLUSDR in RETRY with RC 2540—list five checks in priority order.
When is RESET CHANNEL justified versus forbidden?
Draw impact diagram: one stuck channel from partial to full repo.
1. Stuck cluster channel often blocks:
2. CLUSDR stuck in BINDING—check:
3. RESET CHANNEL risk:
4. DISPLAY to compare definition vs runtime: