Comments on: Finding WMQ constants / bit-flags http://hursleyonwmq.wordpress.com/2007/11/12/finding-wmq-constants-bit-flags/ A place to talk with people who work on WebSphere MQ Wed, 20 Aug 2008 04:00:54 +0000 http://wordpress.org/?v=MU By: Tim Halbur http://hursleyonwmq.wordpress.com/2007/11/12/finding-wmq-constants-bit-flags/#comment-3571 Tim Halbur Tue, 11 Dec 2007 19:28:36 +0000 http://hursleyonwmq.wordpress.com/2007/11/12/finding-wmq-constants-bit-flags/#comment-3571 This is a good little tool, something to put into my "toolbelt" to help debug issues. Wonder if you've considered extending it further. Frequently I have an mqmd or mqgmo in a trace written out in hex. I then have to get out my trusty Application Programming Reference and figure out the MQMD structure, then count up my number of bytes, and do reverse mapping (02 00 00 00 actually = 00000002) in my head for each field, and figure out that B8 04 00 00 = 1208 which is in the encoding field and so it means Decimal normal. This tool helps, but, I need to know that the constant starts mqenc to figure out what 1208 means. If I just put in the B8 04 00 00 with no constants there are just too many options. So the extension would be, if I passed in a hex MQMD, could you translate the whole thing? 4D 44 20 20 02 00 00 00 00 00 00 00 08 00 00 00 FF FF FF FF 00 00 00 00 22 02 00 00 B8 04 00 00 4D 51 48 52 46 32 20 20 04 00 00 00 01 00 00 00 41 4D 51 20 44 49 47 50 41 51 4D 31 20 20 20 20 46 F1 82 CD 20 03 35 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 44 49 47 50 41 51 4D 31 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 6D 71 6D 20 20 20 20 20 20 20 20 20 03 31 30 36 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 1C 00 00 00 57 65 62 73 70 68 65 72 65 20 4D 51 20 43 6C 69 65 6E 74 20 66 6F 72 20 4A 61 76 61 32 30 30 37 31 30 30 38 31 36 35 39 31 39 37 32 20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF If I use M071 to browse a queue with a message on it, it basically gives me this: StrucId :'MD ' Version :2 Report :0 Message Type :8 Expiry :-1 Feedback :0 MQEncoding :0x'222' CCSID :437 Format :'MQHRF2 ' Priority :4 Persistence :1 (Persistent) Message Id :414D51204449494E464F425131202020AA03E84646713E21 Correl. Id :414D51580000000000000000000000000000000000000000 Backout Cnt. :0 ReplyToQ :' ' ReplyToQMgr :'DIINFOBQ1 ' UserId :'mqm ' AccountingTkn:0000000000000000000000000000000000000000000000000000000000000000 ApplIndentity:' ' PutApplType :26 PutApplName :'DIINFOBR1 ' Put Date :'20071128' Put Time :'21251484' ApplOriginDat:' ' Group Id :414D51204449494E464F425131202020AA03E84606873E21 Msg Seq No. :1 Offset :0 MsgFlags :24 Original Len.:-1 but if I only have the message in a trace, could I get this basic information from feeding in the hex and have it spit the formated MQMD out? No matter what, again, this is a good thing to work with. Just looking to see if it goes to the next step. This is a good little tool, something to put into my “toolbelt” to help debug issues. Wonder if you’ve considered extending it further. Frequently I have an mqmd or mqgmo in a trace written out in hex. I then have to get out my trusty Application Programming Reference and figure out the MQMD structure, then count up my number of bytes, and do reverse mapping (02 00 00 00 actually = 00000002) in my head for each field, and figure out that B8 04 00 00 = 1208 which is in the encoding field and so it means Decimal normal. This tool helps, but, I need to know that the constant starts mqenc to figure out what 1208 means. If I just put in the B8 04 00 00 with no constants there are just too many options.

So the extension would be, if I passed in a hex MQMD, could you translate the whole thing?

4D 44 20 20 02 00 00 00 00 00 00 00 08 00 00 00
FF FF FF FF 00 00 00 00 22 02 00 00 B8 04 00 00
4D 51 48 52 46 32 20 20 04 00 00 00 01 00 00 00
41 4D 51 20 44 49 47 50 41 51 4D 31 20 20 20 20
46 F1 82 CD 20 03 35 02 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 20 44 49 47 50 41 51 4D 31 20 20 20 20
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 20 6D 71 6D 20 20 20 20 20 20 20 20 20
03 31 30 36 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
1C 00 00 00 57 65 62 73 70 68 65 72 65 20 4D 51
20 43 6C 69 65 6E 74 20 66 6F 72 20 4A 61 76 61
32 30 30 37 31 30 30 38 31 36 35 39 31 39 37 32
20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00
00 00 00 00 00 00 00 00 FF FF FF FF

If I use M071 to browse a queue with a message on it, it basically gives me this:

StrucId :’MD ‘
Version :2
Report :0
Message Type :8
Expiry :-1
Feedback :0
MQEncoding :0x’222′
CCSID :437
Format :’MQHRF2 ‘
Priority :4
Persistence :1 (Persistent)
Message Id :414D51204449494E464F425131202020AA03E84646713E21
Correl. Id :414D51580000000000000000000000000000000000000000
Backout Cnt. :0
ReplyToQ :’ ‘
ReplyToQMgr :’DIINFOBQ1 ‘
UserId :’mqm ‘
AccountingTkn:0000000000000000000000000000000000000000000000000000000000000000
ApplIndentity:’ ‘
PutApplType :26
PutApplName :’DIINFOBR1 ‘
Put Date :’20071128′
Put Time :’21251484′
ApplOriginDat:’ ‘
Group Id :414D51204449494E464F425131202020AA03E84606873E21
Msg Seq No. :1
Offset :0
MsgFlags :24
Original Len.:-1

but if I only have the message in a trace, could I get this basic information from feeding in the hex and have it spit the formated MQMD out?

No matter what, again, this is a good thing to work with. Just looking to see if it goes to the next step.

]]>