| Author |
Message
|
| ycae |
 Posted: Tue Aug 01, 2006 6:10 am Post subject: Need your help |
 |
|
Newbie
Joined: 01 Aug 2006
Posts: 7
|
Dear all,
I am now looking since 2 days to find a solution but now i think i am at the end of any ideas. Here is the problem:
I've set up a local queue on a solaris box and everything seems to be defined correctly. Put if the guys from the i5 team tries to send me a message to my queue i get an error message that the sent message could not be delivered to the destination queue and was stored in the dead-letter queue.
Is there any possibility to see what's in the dead-letter queue. Is there any possibility to better trace the message and having may be a better explanation about why the message didn't go the the destination queue?
thanks a lot for your support
Yves |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Aug 01, 2006 6:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
First - the dead letter queue is just a local queue assigned to a particular purpose. It can be viewed with any tool capable of reading messages.
Second - the message will have had a header prepended by the queue manager, which explains why it's there. You'll find the structure in the documentation and it's a much better starting point for the resolution of this problem than a trace!
Have fun 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ycae |
| Posted: Tue Aug 01, 2006 6:18 am Post subject: |
|
|
Newbie
Joined: 01 Aug 2006
Posts: 7
|
hi,
but when i use the amqsget to read the message in the dead.letter queue, i get an error.....what tool do you use to view your messages??
Thanks,
yves |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 01, 2006 6:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What error code do you get? Not 2080 by any chance??
I use RFHUTILC or my own version of amqsget
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 01, 2006 6:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
try amqsbcg.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 01, 2006 6:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| try amqsbcg. |
Which has the added advantage of leaving the messages on the queue of course.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ycae |
| Posted: Tue Aug 01, 2006 6:39 am Post subject: |
|
|
Newbie
Joined: 01 Aug 2006
Posts: 7
|
Hi,
Ok the tool helped a lot but i don't really see an error message...
here is the output of one of the messages in the dead letter queue.
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 819
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'C1D4D840D5C1E3C1C3C8C1404040404044CF542220000E07'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'BLABLA '
** Identity Context
UserIdentifier : 'testetsesset '
AccountingToken :
X'0F40404040404040404040404040404000000000000000000000000000000008'
ApplIdentityData : ' '
** Origin Context
PutApplType : '8'
PutApplName : 'B59868B1 testsetetest 017447 '
PutDate : '20060801' PutTime : '14305726'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 174 bytes
00000000: 444C 4820 0000 0001 0000 0827 5445 5354 'DLH .......'TEST'
00000010: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 534F 4C41 ' SOLA'
00000040: 5249 5330 3120 2020 2020 2020 2020 2020 'RIS01 '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 0000 0111 ' ....'
00000070: 0000 01F4 4D51 5354 5220 2020 0000 0006 '....MQSTR ....'
00000080: 616D 7163 7273 7461 5F6E 6420 2020 2020 'amqcrsta_nd '
00000090: 2020 2020 2020 2020 2020 2020 3230 3036 ' 2006'
000000A0: 3038 3031 3134 3335 3132 3937 8585 '080114351297.. '
No more messages
thanks,
yves |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 01, 2006 6:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's not an error message, it's a return code.
It's in the MQDLH. In your message, it's the following "00000000: 444C 4820 0000 0001 0000 0827 5445 5354 'DLH .......'TEST' "
This is 2087 (X'0827')MQRC_UNKNOWN_REMOTE_Q_MGR
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 01, 2006 6:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ycae wrote: |
Ok the tool helped a lot but i don't really see an error message...
|
If you look the DLH structure up as I suggested, you'd see the 2087 reason code..... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Hassan |
| Posted: Tue Aug 01, 2006 9:33 am Post subject: |
|
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
i5 (or the system formerly known as AS/400  ) by default converts all Queue Manager, Queue, etc. names to UPPER CASE unless they are in 'quotes'.
A possibility you may want to look into.....
Cheers! |
|
| Back to top |
|
|
| ycae |
| Posted: Wed Aug 02, 2006 12:13 am Post subject: |
|
|
Newbie
Joined: 01 Aug 2006
Posts: 7
|
Starting from version 6 of MQ even the queue manager has to be in UPPERCASE .
we have older versions of MQ running here and there the qmgrs are in lower case and everything works fine but it seems that starting from version 6.....it is case sensitive.
Thanks for all your help.
Yves |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 02, 2006 1:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
MQ has been case-sensitive since at least v5.0.
If you've been getting away with ignoring that, it's been luck more than anything else.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Hassan |
| Posted: Wed Aug 02, 2006 4:31 am Post subject: |
|
|
Voyager
Joined: 01 Apr 2004
Posts: 81
Location: Toronto, Canada
|
AS/400's converts all parameters into uppercase unless specified inside ' ' it is not specific to MQ on AS/400.
You can still name queue managers using lowercase or mixed case as long as all references to these queue managers are made inside ' ' |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 02, 2006 4:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That's not specific to AS/400. That's standard behavior for MQ on all platforms, since version 5 at least.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 02, 2006 4:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
How did this get duplicated? 
_________________
I am *not* the model of the modern major general.
Last edited by jefflowrey on Wed Aug 02, 2006 6:22 am; edited 2 times in total |
|
| Back to top |
|
|
|
|
