Vinay, if you do not want to spend time to install supportpacs (like MO71) then the fastes way to check why the messages are on the dead letter queue is to use the IBM supplied browse sample program amqsbcg:
/usr/mqm/samp/bin/amqsbcg SYSTEM.DEAD.LETTER.QUEUE YOURQMGR > dlq.browse the dlq.browse then looks like this: AMQSBCG0 - starts here ********************** MQOPEN - 'SYSTEM.DEAD.LETTER.QUEUE' MQGET of message number 1 ****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'414D51204D5141444D494E3420202020C713033E12F00000' CorrelId : X'000000000000000000000000000000000000000000000000' BackoutCount : 0 ReplyToQ : ' ' ReplyToQMgr : '******** ' ** Identity Context UserIdentifier : '******* ' AccountingToken : X'160105150000009F3C2D05AC5FFA16ED7C36243D3C000000000000000000000B' ApplIdentityData : ' ' ** Origin Context PutApplType : '11' PutApplName : 'MQSeries\pgm\bin\amqsput.exe' PutDate : '20030109' PutTime : '08580248' ApplOriginData : ' ' GroupId : X'000000000000000000000000000000000000000000000000' MsgSeqNumber : '1' Offset : '0' MsgFlags : '0' OriginalLength : '-1' **** Message **** length - 184 bytes 00000000: 444C 4820 0000 0001 0000 0825 4153 4446 'DLH .......%ASDF' 00000010: 3220 2020 2020 2020 2020 2020 2020 2020 '2 ' 00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' ' 00000030: 2020 2020 2020 2020 2020 2020 **** **** ' ****' 00000040: **** **** 2020 2020 2020 2020 2020 2020 '*** ' 00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' ' 00000060: 2020 2020 2020 2020 2020 2020 0000 0222 ' ..."' 00000070: 0000 0352 4D51 5354 5220 2020 0000 0006 '...RMQSTR ....' 00000080: 616D 7163 7273 7461 5F6E 6420 2020 2020 'amqcrsta_nd ' 00000090: 2020 2020 2020 2020 2020 2020 3230 3033 ' 2003' 000000A0: 3031 3039 3038 3536 3236 3937 6173 6466 '010908562697asdf' 000000B0: 6173 6466 6173 6466 'asdfasdf ' in the message dump you can see the "DLH" identifying the dead letter header, now check from byte 9 to 12 - the value is 00000825 (hex) which is 2085 dezimal Now you can check API Return and Reason Codes in the "messages and Codes" manual or use "mqrc 2085" which should return 2085 0x00000825 MQRC_UNKNOWN_OBJECT_NAME In this case you also see the Object name that is missing (ASDF). Because of our security policies i had to wipe out some fields like user ids and queuemanager names. Hope that helps Stefan -----Ursprüngliche Nachricht----- Von: vinay_tiwari [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 9. Januar 2003 06:00 An: [EMAIL PROTECTED] Betreff: Re: AW: Help needed regarding Deadletter queue Sorry for not specifying the environment. The environment is UNIX and MQSeries version 5.2. TIA. Vinay -----Original Message----- From: Raabe, Stefan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 4:34 PM To: [EMAIL PROTECTED] Subject: AW: Help needed regarding Deadletter queue Hello unfortunately you dont tell us what platform you are on (win/nt, unix, os/390, ...), there are different tools for each platform available to browse a queue. if mq puts a message to the dlq a dlh (dead letter headder) is added. the structure is described in the application programmers reference (MQDLH), the reason is at bytes 9 -12. So browse the queue, check for "DLH" as the start of the dead letter header. In the sample below you will see reason code 000007F3 hex -> 2035 decimal "not authorized" (check with api reason codes in messages and codes manual). DLH .......3.... CDC40000000F.... 438000010073.... If you do not know how to browse the DLQ please tell us what platform you are on. For OS/390, there are ispf utilities available containing a DLQ utility (MA10 on IBM supportpac page). Other Tools (MQ Explorer, MO71) are available depending what platform you are using. Regards Stefan -----Ursprüngliche Nachricht----- Von: vinay_tiwari [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 8. Januar 2003 11:28 An: [EMAIL PROTECTED] Betreff: Help needed regarding Deadletter queue On my queue manager messages are piling up in the dead letter queue.Is there a way to browse these messages and findout the reason. TIA. Vinay Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
