| Author |
Message
|
| jhidalgo |
 Posted: Mon Apr 13, 2009 9:14 am Post subject: AMQ9700: can't show the message for the hex code: 'X'2080970 |
 |
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
I am having the error AMQ9700 and the only information I get is something like this:
MQ has tried to show the message for the hex code 'X'20809700''....
The request has the insertion 32767 : 0 : Length : : .
I am not pasting the complete message because its in spanish.
Any help from here ? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Apr 13, 2009 9:19 am Post subject: Re: AMQ9700: can't show the message for the hex code: 'X'208 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jhidalgo wrote: |
I am having the error AMQ9700 and the only information I get is something like this:
MQ has tried to show the message for the hex code 'X'20809700''....
|
What version? What platform? What circumstances does the error arise in? Sometimes or for all commands?
Have you checked the language environment variables are set properly? Have you checked the message catalague is in the correct path?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jhidalgo |
| Posted: Mon Apr 13, 2009 9:33 am Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
Sorry,
Platform: iSeries V5R4
MQ: 6.0.2.5
The error seems to be related with a dynamic channel for the cluster, it never gets connected, the connection is established sometimes, and some messages go are sent but it always remains in "Retrying"
MQ logs all the events correctly, only this one is not .... available. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Apr 13, 2009 12:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jhidalgo wrote: |
Sorry,
Platform: iSeries V5R4
MQ: 6.0.2.5
The error seems to be related with a dynamic channel for the cluster, it never gets connected, the connection is established sometimes, and some messages go are sent but it always remains in "Retrying"
MQ logs all the events correctly, only this one is not .... available. |
Have you checked the error logs? On both sides of the channel. Does your channel have 'none' as mcauser? Are the sequence numbers in error? Is the channel missing the cluster name? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jhidalgo |
| Posted: Mon Apr 13, 2009 12:58 pm Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
| fjb_saper wrote: |
Have you checked the error logs? On both sides of the channel.
|
Yes, on one side I have the undocummented error I've posted, on the other side I just have AMQ9209
| fjb_saper wrote: |
Does your channel have 'none' as mcauser?
|
Yes, it is a dynamic channel, and I haven't changed the default
| fjb_saper wrote: |
Are the sequence numbers in error?
|
No, that is not logged
| fjb_saper wrote: |
Is the channel missing the cluster name? |
Its a dynamic channel |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Apr 14, 2009 2:54 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| fjb_saper wrote: |
Does your channel have 'none' as mcauser?
|
| jhidalgo wrote: |
Yes, it is a dynamic channel, and I haven't changed the default |
This is not an answer. You need to inspect the channel, preferably on the cluster receiver. If 'none' is in the mcauser you need to remove it. This is typically done to avoid people creating cluster channels willy nilly and have them work. So this value may well be in the default...
| fjb_saper wrote: |
Are the sequence numbers in error?
|
| jhidalgo wrote: |
| No, that is not logged |
| fjb_saper wrote: |
Is the channel missing the cluster name? |
| jhidalgo wrote: |
Its a dynamic channel |
So what? if the cluster receiver has not been configured correctly you will never get the channel to work...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jhidalgo |
| Posted: Mon Apr 20, 2009 1:22 pm Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
the cluster receiver is configured properly, in fact it receives information from a lot of sources. the MCA is not the problem.
there is something else wrong, but it is not the definitions of the cluster objects, the only thing I have found useful is that it works for a while after doing
REFRESH CLUSTER
on both sides (on both PRs unable to communicate)
:S |
|
| Back to top |
|
|
|
|
