| Author |
Message
|
| sumit |
 Posted: Thu Apr 26, 2007 7:09 am Post subject: Messages going to dead letter queue. |
 |
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
Hi
We are sending messages from queue manager A on Solaris to queue manager B on Mainframe. Remote queue is defined on A and it is pointing to a queue at B.
When we are sending messages from A to B, they are going to a dead letter queue instead of the local queue that we have defined at B. The logs at B are saying :
+CSQX548E )MQST CSQXRESP Messages sent to local dead-letter queue,
channel GKOPQH1GM1.USIT,
reason=2087
When I googled it, I found that it can be because of some sequence issue problem and there may be some bad data in SYSTEM.CHANNEL.SYNCQ which needs to be deleted.
I did a reset on both the channels, but result was same.
Can anyone tell what needs to be done here...
Info about Solaris :
Name: WebSphere MQ
Version: 6.0.2.0
CMVC level: p600-200-060921
BuildType: IKAP - (Production)
Info about Mainframe
WMQ 5.3.1
Also, why is it showing the error 2087  . Is it a genuine error in this regard?
_________________
Regards
Sumit |
|
| Back to top |
|
 |
| sumit |
| Posted: Thu Apr 26, 2007 7:11 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
sorry, wrong forum.. I will post this in General Support.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 26, 2007 7:11 am Post subject: Re: Messages going to dead letter queue. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sumit wrote: |
+CSQX548E )MQST CSQXRESP Messages sent to local dead-letter queue,
channel GKOPQH1GM1.USIT,
reason=2087
|
| Code: |
| 2087 0x00000827 MQRC_UNKNOWN_REMOTE_Q_MGR |
I'm not aware of this being anything to do with channels or sequence numbers......
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 26, 2007 12:52 pm Post subject: Re: Messages going to dead letter queue. |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
| sumit wrote: |
+CSQX548E )MQST CSQXRESP Messages sent to local dead-letter queue,
channel GKOPQH1GM1.USIT,
reason=2087
|
| Code: |
| 2087 0x00000827 MQRC_UNKNOWN_REMOTE_Q_MGR |
I'm not aware of this being anything to do with channels or sequence numbers...... |
It's more about default paths and qmgr aliases... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tleichen |
| Posted: Mon Apr 30, 2007 6:54 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
Read the error code definition. It says, "unknown remote queue manager". Your target queue manager is incorrect. 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| Arthur.Wang |
| Posted: Fri May 11, 2007 7:42 am Post subject: |
|
|
Newbie
Joined: 26 Apr 2007
Posts: 2
|
| Double check the remote manage's name and to see if the transmission queue name is the same as remote queue manage name |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri May 11, 2007 9:13 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| Arthur.Wang wrote: |
| Double check the remote manage's name and to see if the transmission queue name is the same as remote queue manage name |
so you think the messages are meant for another queuemanager and the mainframe one is a transit queuemanager?
it's possible, but may not be the answer...
first you need to look at the remote queue definition on the solaris box...
and know whether the mainframe qm is the final destination or not...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
|
|
