Home

 

Cause

 

Check that the queue manager where the object exists and this queue manager are still connected to the cluster. Make sure that they can each display all of the full repositories in the cluster. Also make sure that the CLUSSDR channels to the full repositories are not in retry state, as above.

Next make sure that the full repositories have enough CLUSSDR channels defined to correctly connect them together. The updates to the cluster only flow between the full repositories over manually defined CLUSSDR channels. After the cluster has formed these will show as DEFTYPE(CLUSSDRB) channels because they are both manual and automatic channels. There must be enough of these to form a complete network among all of the full repositories.

1 : display ql(SYSTEM.CLUSTER.TRANSMIT.QUEUE) curdepth

AMQ8441: Display Cluster Queue Manager details.

CLUSQMGR(QM1) CLUSTER(DEMO)

CHANNEL(TO.QM1) DEFTYPE(CLUSSDRA)

QMTYPE(NORMAL) STATUS(RUNNING)

AMQ8441: Display Cluster Queue Manager details.

CLUSQMGR(QM2) CLUSTER(DEMO)

CHANNEL(TO.QM2) DEFTYPE(CLUSRCVR)

QMTYPE(REPOS)

AMQ8441: Display Cluster Queue Manager details.

CLUSQMGR(QM3) CLUSTER(DEMO)

CHANNEL(TO.QM3) DEFTYPE(CLUSSDRB)

QMTYPE(REPOS) STATUS(RUNNING)

AMQ8441: Display Cluster Queue Manager details.

CLUSQMGR(QM4) CLUSTER(DEMO)

CHANNEL(TO.QM4) DEFTYPE(CLUSSDRA)

QMTYPE(NORMAL) STATUS(RUNNING)

 

Parent topic:

Symptom — A queue manager does not appear to have up to date information about queues and channels in the cluster.

qc13230_

 

Home