ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Messages reaching dead letter queue

Post new topic  Reply to topic Goto page 1, 2  Next
 Messages reaching dead letter queue « View previous topic :: View next topic » 
Author Message
ram0328
PostPosted: Sun Feb 13, 2011 11:47 am    Post subject: Messages reaching dead letter queue Reply with quote

Novice

Joined: 13 Feb 2011
Posts: 11

HI All,

I am new to MQ and i have the following query.
I am using MQ 6.0 on AIX box.
I am facing the issue when transferring messages from mainframe MQ to WMQ.
we have created a remote queue and transmission queue and sender channel at minframe end
and created a local queue and receiver channel at WMQ end.
Now if i am transferring the messages from mainframe end the messages are going into the dead letter queue at WMQ end.
any help on this??
Back to top
View user's profile Send private message
smdavies99
PostPosted: Sun Feb 13, 2011 12:31 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

There will be information about the cause in the one or more of the following:-
- event logs
- WMQ logs (AMQERR01.Log)
- Dead Letter Queue Header. This is in the actual message on the DLQ.

The most common cause in my experience is that the destination queue is not defined or incorrectly defined.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Feb 13, 2011 2:12 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

Quote:
The most common cause in my experience is that the destination queue is not defined or incorrectly defined.

Object names in MQ are case-sensitive.

Destination queue incorrectly defined means that the name of the destination queue spelled exactly the same, and in the exact same case, as the RNAME specified in the QRemote definition.

The destination queue manager name must be spelled exactly the same as it was specified in the RQMNAME of the QRemote definition.

What is the destination queue manager name?

What is the destination queue name?

If you post the DLH (Dead Letter Header) from one of the messages in the dead-letter queue, we can help.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Sun Feb 13, 2011 11:29 pm    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

Security may be another issue. However, as bruce said, look into the dead letter header to stop guessing and start knowing
_________________
Regards, Butcher
Back to top
View user's profile Send private message
ram0328
PostPosted: Mon Feb 14, 2011 8:37 am    Post subject: Reply with quote

Novice

Joined: 13 Feb 2011
Posts: 11

i serched on net and got the mq log dump and below one is the part of it.
can you please let me know whether this contains the required information?
If not can you plz let me know how can i get the required information



lrecsize 930, version 1, rmid 0, eyecatcher HLRH

LogRecdType . . : AQM Put Message (257)
Eyecatcher . . : ALRH Version . . . . : 1
LogRecdLen . . : 910 LogRecdOwnr . . : 256 (AQM)
XTranid . . . . : TranType: MQI TranNum{High 0, Low 2081}
QueueName . . . : SYSTEM.DEAD.LETTER.QUEUE
Qid . . . . . . : {Hash 1800381434, Counter: 0}
ThisLSN . . . . : <0:0:0:0>
PrevLSN . . . . : <0:0:7084:27019>

Version . . . . : 4
MapIndex . . . : 263
PrevLink.Locn . : 135176 PrevLink.Length : 8
PrevDataLink . : {High 0, Low 136192}
Data.Locn . . . : 136192 Data.Length . . : 670
Data . . . . . :
00000: 41 51 52 48 00 00 00 04 FF FF FF FF FF FF FF FF AQRH....
00016: 00 00 00 00 00 00 00 00 00 00 01 07 00 02 01 C0 ...............
00032: 00 00 00 00 00 00 00 01 00 00 00 DE 00 00 00 00
Back to top
View user's profile Send private message
exerk
PostPosted: Mon Feb 14, 2011 8:44 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Use the browse sample (amqsbcg), or one of the SupportPacs, e.g. MA96, to read off the formatted header which will contain the MQRC specific to why the message was put to the DLQ.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
ram0328
PostPosted: Mon Feb 14, 2011 8:45 am    Post subject: Reply with quote

Novice

Joined: 13 Feb 2011
Posts: 11

Thanks for that.
But i am running WMQ on a unix box and i dont have any GUI.
Is there any command by which i can get the header in a correct way?
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Mon Feb 14, 2011 8:48 am    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

dont know what that is you posted. A dump from the MQ log? IMHO it does not show what you need, and it is additional and unnecessary work digging in the logs.

The DLH (dead letter header) holds all information you need. iI is added to the message when the message is put onto the DLQ.

Just browse the DLQ. amqsbcg sample is fine for that (if you do not have anything better). Check the output with the application programmers manual about the layout of the DLH, and find out the reason code. Check that with the messages and codes manual and you know why your message has been put to the DLQ.

Post your findings here for verification if you like.
_________________
Regards, Butcher
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Feb 14, 2011 8:55 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

ram0328 wrote:
But i am running WMQ on a unix box and i dont have any GUI.


amqsbcg isn't GUI. IIRC some of the other command line support pacs (q ?) can also read the header.

Not sure on that though. You might still need to decode it.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
ram0328
PostPosted: Mon Feb 14, 2011 9:17 am    Post subject: Reply with quote

Novice

Joined: 13 Feb 2011
Posts: 11

HI When i browsed by using amqsbcg i got the below message in log

** Identity Context
UserIdentifier : 'usgm '
AccountingToken :
X'04E4E2C7D4000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '2'
PutApplName : 'USGMMQWR '
PutDate : '20110210' PutTime : '12420677'
ApplOriginData : ' '

GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'

**** Message ****

length - 222 bytes

00000000: 444C 4820 0000 0001 0000 0825 4D4D 532E 'DLH .......%MMS.'
00000010: 574D 512E 5245 4D4F 5445 2E4E 4F54 4943 'WMQ.REMOTE.NOTIC'
00000020: 452E 5245 5320 2020 2020 2020 2020 2020 'E.RES '
00000030: 2020 2020 2020 2020 2020 2020 574D 512E ' WMQ.'
00000040: 5153 3120 2020 2020 2020 2020 2020 2020 'QS1 '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 0000 0311 ' ....'
00000070: 0000 01F4 4D51 5354 5220 2020 0000 0006 '...MQSTR ....'
00000080: 616D 7172 6D70 7061 2020 2020 2020 2020 'amqrmppa '
00000090: 2020 2020 2020 2020 2020 2020 3230 3131 ' 2011'
000000A0: 3032 3130 3132 3339 3134 3830 5B5B 5B5B '021012391480[[[['
000000B0: 5B5B 5B5B 5B5B 5B5B 5B5B 5B5B 5B5B 5B5B '[[[[[[[[[[[[[[[['
000000C0: 5B5B 5B5B 5B5B 5B5B 5B5B 5B5B 5B5B 5B5B '[[[[[[[[[[[[[[[['
000000D0: 5B5B 5B5B 5B5B 5B5B 5B5B 5B5B 5B5B '[[[[[[[[[[[[[[ '



No more messages
MQCLOSE
MQDISC

can you please let me know how can i check what went wrong in this??
Back to top
View user's profile Send private message
exerk
PostPosted: Mon Feb 14, 2011 9:23 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

ram0328 wrote:
00000000: 444C 4820 0000 0001 0000 0825 4D4D 532E 'DLH .......%MMS.'


Convert the hex to decimal, then look up the code.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon Feb 14, 2011 9:24 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

So if you look up the structure of the MQDLH header, you will see that the MQRC for the failure is right after the StrucID and Version, and in your case is the hex value "0825".

So MQRC 0x0825 returns
Quote:
mqrc 0x0825

2085 0x00000825 MQRC_UNKNOWN_OBJECT_NAME


And the Object Name is "WMQ.REMOTE.NOTICE.RES".
Back to top
View user's profile Send private message
mqjeff
PostPosted: Mon Feb 14, 2011 9:24 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

exerk wrote:
ram0328 wrote:
00000000: 444C 4820 0000 0001 0000 0825 4D4D 532E 'DLH .......%MMS.'


Convert the hex to decimal, then look up the code.


Or just ask mqrc to convert it for you..
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Feb 14, 2011 9:24 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

ram0328 wrote:
can you please let me know how can i check what went wrong in this??


Mr Butcher wrote:
Check the output with the application programmers manual about the layout of the DLH, and find out the reason code

_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Feb 14, 2011 9:26 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

smdavies99 wrote:
The most common cause in my experience is that the destination queue is not defined or incorrectly defined


We have a winner!
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » General IBM MQ Support » Messages reaching dead letter queue
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.