| Author |
Message
|
| nikhil.laghave |
 Posted: Wed Jun 13, 2007 4:41 am Post subject: Unexpected error 2087 |
 |
|
Newbie
Joined: 09 Mar 2007
Posts: 5
Location: Pune, India
|
Hello All,
I got a weird 2087 error. This is what happened..
I put a message on a remote q on mainframe which pointed to a local q on AS400 machine...
what happened is that the message reached the AS400 qmgr and instead of going to the intended local q, it went to the dead letter queue...
i have no clue what to do here...can somebody please help me |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jun 13, 2007 4:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
The message was clearly addressed to a queue manager not known to the AS400. Check the remote queue definition on your mainframe and the DLH on the misrouted message.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Jun 13, 2007 8:50 am Post subject: Re: Unexpected error 2087 |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| nikhil.laghave wrote: |
| I put a message on a remote q on mainframe which pointed to a local q on AS400 machine... |
Hi,
If the above statement is true then there is a typo in the Queue-Manager-Name attribute of the Remote Queue definition.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| tecbi |
| Posted: Wed Jun 13, 2007 11:46 am Post subject: |
|
|
Newbie
Joined: 06 Nov 2001
Posts: 5
|
| have you checked to see if the AS400 queue is not full and/or is not put disabled? |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Jun 13, 2007 12:34 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hello tecbi,
Please check your facts before making these kinds of posts because they do more harm than good. "nikhil.laghave" said
| nikhil.laghave wrote: |
I got a weird 2087 error.
...
and instead of going to the intended local q, it went to the dead letter queue |
2087 is MQRC_UNKNOWN_REMOTE_Q_MGR
| tecbi wrote: |
| have you checked to see if the AS400 queue is not full and/or is not put disabled? |
2051 is MQRC_PUT_INHIBITED
2053 is MQRC_Q_FULL
2055 is MQRC_Q_NOT_EMPTY
Hence, your answer is completely misleading. The number one manual everyone should have is the WMQ Messages manual. It is freely available in PDF from IBM MQ's Library web page.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| tecbi |
| Posted: Wed Jun 13, 2007 4:09 pm Post subject: |
|
|
Newbie
Joined: 06 Nov 2001
Posts: 5
|
You're right of course. We faced a very similar problem recently where messages went to the DLQ and that was due to a put disable.
Just didn't see the 2087 in the post -Sorry. |
|
| Back to top |
|
|
| nikhil.laghave |
| Posted: Mon Jul 02, 2007 11:53 pm Post subject: It got resolved |
|
|
Newbie
Joined: 09 Mar 2007
Posts: 5
Location: Pune, India
|
Hello All,
Thanks a lot for ur posts...
The 2087 i received got resolved when i put the messages on the same AS400 queue but thru the same queue manager on AS400 instead of the remote mainframe queue manager....Hereafter the messages from Mainframe were correctly routed to the destination AS400 queue...
Can anyone advise as to how this must have happened....
Also, since the messages were reaching the AS400 qmgr correctly, then how did i get the MQRC_UNKNOWN_REMOTE_Q_MGR....shouldn't the error be sth related to a queue instead of qmgr... |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jul 03, 2007 7:18 am Post subject: Re: It got resolved |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| nikhil.laghave wrote: |
| Can anyone advise as to how this must have happened.... |
Looks at Roger's first reply to you.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
