Comment # 9
on bug 9229
from robionekenobi
It is already a FT_BYTES, but for better reading, i used this to display also
an information (without having to expand the Parameter)
MQPrm[ 1] { 9-BYTE_STRING } 1b5c/ 7004-MQBACF_RESPONSE_ID
A(...@....@@@.........N...) E(CSQ DM1S RDM1S..LT+...)
ParmTyp..: MQCFT_BYTE_STRING (9)
ParmLen..: 40
ParmID...: MQBACF_RESPONSE_ID (7004)
ParmStrLn: 24
ByteStr..: c3e2d840c4d4f1e2404040d9c4d4f1e2cbb3d3e34e9def80
I don't know how it is coded because it's a BYTE_STRING, but I know that MQMID
can contain usefull information, so I display as string in both ASCII/EBCDIC
and put DOT for non-printable charaters to improve the reading.
For the second case, it seems to be a bug in the returned MQ packet, because
the header say ASCII/Little Endian, and really it is EBCDIC/Big Endian
18 2013-07-23 14:30:31.280630000 10.50.216.41 10.47.116.214 MQ
450 MQCONN_REPLY App=...m......m......[......K...
QM=....@@@@@@@@@@@@@@@@@@@@@@@@
So, for not having an unreadable data with escape like this in the detail
display
MQCONN
QMgr....: \304\324\360\342@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
ApplName:
\311\342\340m\304\205\202\244\207\340m\346\211\225\363\362\340[\324\330\303\224\204\302K\205\247\205
ApplType: Unknown (184549376)
AccntTok: 1601051500000085e77e2f2ad0375c43170a324329000000...
Version.: Unknown (50331648)
Options.: 0x00000000
I display a more readable string with dot for non-printable char, in the COL
Info, again for better reading.
Reason of this patch
You are receiving this mail because:
- You are watching all bug changes.
