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 » Message in the dead-letter queue

Post new topic  Reply to topic
 Message in the dead-letter queue « View previous topic :: View next topic » 
Author Message
9A5YY
PostPosted: Tue May 31, 2016 8:05 am    Post subject: Message in the dead-letter queue Reply with quote

Voyager

Joined: 27 Sep 2005
Posts: 99
Location: Croatia
Does anybody can tell what happened? Message was sent from z/OS qmgr to Linux qmgr.

The message was sent to temporary reply-to-queue AMQ.559F864620176C07 but finally was sent to DLQ.

Here is message in DLQ:

MQGET of message number 20
****Message descriptor****

StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 546 CodedCharSetId : 1208
Format : 'MQDEAD '
Priority : 5 Persistence : 1
MsgId : X'C3E2D840E3F1D8F24040404040404040D0D34EF5A940E740'
CorrelId : X'414D512051543130303435202020202046869F5502701720'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : ' z/OS qmgr name '
** Identity Context
UserIdentifier : 'username '
AccountingToken :
X'0000000000000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '2'
PutApplName : 'appl_name '
PutDate : '20160531' PutTime : '15014238'
ApplOriginData : ' '

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

**** Message ****

length - 472 bytes

00000000: 444C 4820 0100 0000 0008 0000 414D 512E 'DLH ........AMQ.'
00000010: 3535 3946 3836 3436 3230 3137 3643 3037 '559F864620176C07'
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 5154 3130 ' QMXX'
00000040: 3034 3520 2020 2020 2020 2020 2020 2020 'XXX '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 1101 0000 ' ....'
00000070: B804 0000 4D51 5354 5220 2020 0600 0000 '....MQSTR ....'
00000080: 616D 7172 6D70 7061 2020 2020 2020 2020 'amqrmppa '
00000090: 2020 2020 2020 2020 2020 2020 3230 3136 ' 2016'
000000A0: 3035 3331 3135 3031 3432 3430 5630 3030 '053115014240V000'
000000B0: 3030 2020 2020 2020 2020 2020 4852 3937 '00 HR97'
000000C0: 3233 3831 3030 3931 3130 3034 3637 3735 '2381009110046775'
000000D0: 3132 3031 362D 3035 2D33 312B 3030 3030 '12016-05-31+0000'
000000E0: 3030 3030 3030 3134 3634 3935 3136 2B30 '00000014649516+0'
000000F0: 3030 3030 3030 3030 3031 3436 3439 3531 '0000000001464951'
00000100: 362B 3030 3030 3030 3030 3030 3030 3030 '6+00000000000000'
00000110: 3031 3030 2B30 3030 3030 3030 3030 3030 '0100+00000000000'
00000120: 3030 3030 3130 3020 2020 2020 2020 2020 '0000100 '
00000130: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000140: 2030 3030 3030 2020 2020 2020 2020 2020 ' 00000 '
00000150: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000160: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000170: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000180: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000190: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000001A0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000001B0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000001C0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000001D0: 2020 2020 2020 2020 ' '



No more messages
MQCLOSE
MQDISC

Last edited by 9A5YY on Tue May 31, 2016 8:15 am; edited 1 time in total
Back to top
View user's profile Send private message
tczielke
PostPosted: Tue May 31, 2016 8:14 am    Post subject: Reply with quote

Guardian

Joined: 08 Jul 2010
Posts: 939
Location: Illinois, USA
Your reason code in your DLH is 2048.

http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.tro.doc/q041190_.htm

Here is how you can find your reason code in the DLH:

00000000: 444C 4820 0100 0000 0008 0000 414D 512E 'DLH ........AMQ.'

The reason code is x'00080000'. This is in a little endian format, so you need to byte reverse it to x'00000800' = 2048.
_________________
Working with MQ since 2010.
Back to top
View user's profile Send private message
9A5YY
PostPosted: Tue May 31, 2016 8:25 am    Post subject: Reply with quote

Voyager

Joined: 27 Sep 2005
Posts: 99
Location: Croatia
Thanks for help how to find where is reason code.
Back to top
View user's profile Send private message
9A5YY
PostPosted: Tue May 31, 2016 8:42 am    Post subject: Reply with quote

Voyager

Joined: 27 Sep 2005
Posts: 99
Location: Croatia
How did you convert from little endian format x'00080000' to x'00000800' what is decimal 2048?
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue May 31, 2016 9:04 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447
The DLH is described here:
http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.dev.doc/q096110_.htm

That tells you which parts of the byte string belong to which fields in the DLH.

Numbers in the MQ DLH are always in Little Endian format.

There are quite a few online tools that will convert between big endian and little endian.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
tczielke
PostPosted: Tue May 31, 2016 10:19 am    Post subject: Reply with quote

Guardian

Joined: 08 Jul 2010
Posts: 939
Location: Illinois, USA
9A5YY wrote:
How did you convert from little endian format x'00080000' to x'00000800' what is decimal 2048?


Little endian means that the littlest byte is in the lowest address. Therefore you need to reverse the bytes to have it in a "normal" or big endian format. For example, if the bytes were x'12345678' in little endian, they would be '78563412' in big endian.

So, x'00080000' in little endian or 00 08 00 00, becomes x'00000800' in big endian or 00 00 08 00.

If you want to learn more about endianness, this MQTC session covers it in some of the earlier slides -> http://www.mqtechconference.com/sessions_v2015/MQTC_v2015_Tracing.pdf

Endianness is based on the processor. So if MQ is running on Linux x86 (x86 is a little endian processor), then the binary data will appear in a little endian format in a memory dump like a trace or amqsbcg output. If MQ is running on Linux SPARC (big endian processor), the data would be big endian.
_________________
Working with MQ since 2010.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue May 31, 2016 10:30 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447
tczielke wrote:
Endianness is based on the processor.

Oh, right. oops... Not fixed for the MQDLH.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
9A5YY
PostPosted: Tue May 31, 2016 11:25 pm    Post subject: Reply with quote

Voyager

Joined: 27 Sep 2005
Posts: 99
Location: Croatia
Guys thanks for help. I learnt how to convert little endian to big endian and find reason code in DLH.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Message in the 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.