MQSeries.net :: View topic - How to interpret dlq reason code?

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » How to interpret dlq reason code?

How to interpret dlq reason code?

« View previous topic :: View next topic »

Author

Message

cots

Posted: Mon May 08, 2006 10:35 am Post subject: How to interpret dlq reason code?

Centurion

Joined: 16 Jun 2003
Posts: 105

all -

We have messages endup in DLQ. all of them showing reason#: 65536. Is there anyway to interpret that reason code to some useful meaning that I can understand?

Thanks in advance

jefflowrey

Posted: Mon May 08, 2006 10:48 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Showing that reason code where?

What does AMQSBCG show for the first 100 bytes of the message in the dlq?
_________________
I am *not* the model of the modern major general.

cots

Posted: Mon May 08, 2006 11:08 am Post subject:

Centurion

Joined: 16 Jun 2003
Posts: 105

I used MQ explore to view message in DLQ. The reason code showing in DLQ header tab. but if I do AMQSBCG, the message showing

StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 819
Format : 'MQDEAD '
Priority : 4 Persistence : 1
MsgId : X'414D5120514D2E5745424150502E414C445C3B832000E403'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'QM.WEBAPP.ALIAS.PROD '
** Identity Context
UserIdentifier : 'mqm '
AccountingToken :
X'0137000000000000000000000000000000000000000000000000000000000006'
ApplIdentityData : ' '
** Origin Context
** Origin Context
PutApplType : '28'
PutApplName : ' '
PutDate : '20060508' PutTime : '16234742'
ApplOriginData : ' '

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

wschutz

Posted: Mon May 08, 2006 11:12 am Post subject:

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

We want to see the first 100 bytes of message data....
_________________
-wayne

cots

Posted: Mon May 08, 2006 11:21 am Post subject:

Centurion

Joined: 16 Jun 2003
Posts: 105

:oops:

00000000: 444C 4820 0000 0001 0001 0000 4557 2E45 'DLH ........EW.E'
00000010: 4653 2E54 4F2E 4541 4920 2020 2020 2020 'FS.TO.EAI '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 514D 2E57 ' QM.W'
00000040: 4542 4150 502E 4252 4B31 2E50 524F 4420 'EBAPP.BRK1.PROD '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 0000 0111 ' ....'
00000070: 0000 0333 4D51 4852 4632 2020 0000 0006 '...3MQHRF2 ....'
00000080: 5765 6253 7068 6572 654D 5149 6E74 6567 'WebSphereMQInteg'
00000090: 7261 746F 7232 2020 2020 2020 3230 3036 'rator2 2006'
000000A0: 3035 3038 3136 3233 3438 3030 5246 4820 '050816234800RFH '
000000B0: 0000 0002 0000 0184 0000 0111 0000 04B8 '...............Â¸'
000000C0: 4D51 5354 5220 2020 0000 0000 0000 04B8 'MQSTR .......Â¸'
00

wschutz

Posted: Mon May 08, 2006 11:32 am Post subject:

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

Looks like MQSI is putting it there... perhaps you should check the MQSI logs for the real reason ....
_________________
-wayne

jefflowrey

Posted: Mon May 08, 2006 11:35 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

And please start migration to at least WMBIMB v5, if not straight to WMB v6! 2.1 is so far out of support it's probably dangerous to use!
_________________
I am *not* the model of the modern major general.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » How to interpret dlq reason code?

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