Home

 

Cause

 

Either the remote queue manager is not available or there is an incorrect parameter in either the local manually defined cluster sender channel definition or the remote cluster receiver definition.

First check whether the problem is the availability of the remote queue manager. Are there any error messages? Is the queue manager active? Is the queue manager's listener running? Is the queue manager's channel able to start?

If the remote queue manager is available there could be a problem with a channel definition. Check the definition type of the cluster queue manager for the channel in retry state. For example:

1 : dis clusqmgr(*) deftype where(channel eq TO.QM2)

AMQ8441: Display Cluster Queue Manager details.

CLUSQMGR(QM2)

CHANNEL(TO.QM2)

CLUSTER(DEMO)

DEFTYPE(CLUSSDRA)

If the definition type is CLUSSDR the channel is using the local manual cluster sender definition. Alter any incorrect parameters in the local manual cluster sender definition and restart the channel.

If the definition type is either CLUSSDRA or CLUSSDRB the channel is using an auto-defined cluster sender channel based on the definition of a remote cluster receiver channel. Alter any incorrect parameters in the remote cluster receiver definition. For example, the conname may be incorrect.

1 : alter chl(to.qm2) chltype(clusrcvr) conname('newhost(1414)')

AMQ8016: WebSphere MQ channel changed.

Changes to the remote cluster receiver definition will be propagated out to any cluster queue managers that are interested and the corresponding auto-defined channels will be updated accordingly. We can check that the updates have been propagated correctly by checking the changed parameter. For example:

1 : dis clusqmgr(qm2) conname

AMQ8441: Display Cluster Queue Manager details.

CLUSQMGR(QM2)

CHANNEL(TO.QM2)

CLUSTER(CLUSDEMO)

CONNAME(newhost(1414))

If the auto-defined definition is now correct, restart the channel.

 

Parent topic:

Symptom — A cluster sender channel is in retry state.

qc13110_

 

Home