MQSeries.net :: View topic - Message corrupt

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 » Message corrupt

Message corrupt

« View previous topic :: View next topic »

Author

Message

2189

Posted: Tue Oct 10, 2006 7:35 am Post subject: Message corrupt

Apprentice

Joined: 22 Oct 2002
Posts: 31

Hi,

We're sending a message from a mainframe to an AIX server and part of our messages are getting corrupted. If I view the message at the destination, the message header is readable is is the majority of the data, except for the start which looks like this:

Code:

00000000: 5246 4820 0000 0002 0000 00C8 0000 0111 'RFH .......Ãˆ....'
00000010: 0000 0333 4D51 5354 5220 2020 0000 0000 '...3MQSTR ....'
00000020: 0000 04B8 0000 00A0 4C94 8384 6E4C D4A2 '...Â¸... L...nLÃ”Â¢'
00000030: 846E 9194 A26D A385 A7A3 4C61 D4A2 846E '.n..Â¢mÂ£.Â§Â£LaÃ”Â¢.n'
00000040: 4CE2 85A3 6ED3 E3E2 C2C3 D9D4 4C61 E285 'LÃ¢.Â£nÃ“Ã£Ã¢Ã‚ÃƒÃ™Ã”LaÃ¢.'
00000050: A36E 4CE3 A897 856E C997 F493 D389 A585 'Â£nLÃ£Â¨..nÃ‰.Ã´.Ã“.Â¥.'
00000060: 4C61 E3A8 9785 6E4C C694 A36E A794 934C 'LaÃ£Â¨..nLÃ†.Â£nÂ§..L'
00000070: 61C6 94A3 6E4C 6194 8384 6E40 4040 4040 'aÃ†.Â£nLa...n@@@@@'
00000080: 4040 4040 4040 4040 4040 4040 4040 4040 '@@@@@@@@@@@@@@@@'
00000090: 4040 4040 4040 4040 4040 4040 4040 4040 '@@@@@@@@@@@@@@@@'
000000A0: 4040 4040 4040 4040 4040 4040 4040 4040 '@@@@@@@@@@@@@@@@'
000000B0: 4040 4040 4040 4040 4040 4040 4040 4040 '@@@@@@@@@@@@@@@@'
000000C0: 4040 4040 4040 4040 3C61 7069 3E3C 7265 '@@@@@@@@<api><re'
000000D0: 7175 6573 743E 3C68 6561 6465 723E 3C75 'quest><header><u'
000000E0: 7365 7249 643E 3133 3334 3235 303C 2F75 'serId>1334250</u'
000000F0: 7365 7249 643E 3C75 7365 7249 6465 6E74 'serId><userIdent'
.
.
.

You can then see the data becomes readable again at line 000000C0.

I initially suspected this may be a converstion issue between ebcidic and ascii however I can't understand why only the header of the message is corrupt. Apparently if the message is sent to a local queue on the mainframe it is presented correctly.

I'd be grateful for any suggestions.

thanks

Gareth
_________________
2189 errors make me

jefflowrey

Posted: Tue Oct 10, 2006 7:37 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It's not a conversion problem at all.

The message has an MQRFH2 header on it, that's why it starts with "RFH".
_________________
I am *not* the model of the modern major general.

2189

Posted: Tue Oct 10, 2006 7:46 am Post subject:

Apprentice

Joined: 22 Oct 2002
Posts: 31

jefflowrey

Yeah I see that header. I'm infrastructure support, not app support so I don't know the implications of all the different header types, though I know you need MQSTR to enable convertion. I had however concluded that it was unlikely to be a converstion issue as most of the message was readable.

Can you suggest why the RFH header is corrupt. I've viewed other messages on this qmgr which have similar message structures and these messages are ok, though I can't be sure they're sent from the mainframe as I have no visibility to that service.

Gareth
_________________
2189 errors make me

jefflowrey

Posted: Tue Oct 10, 2006 7:47 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Are you sure the RFH header is actually corrupt?

What are the application teams telling you is the problem with it? Maybe the receiver just isn't expecting an MQRFH2....
_________________
I am *not* the model of the modern major general.

2189

Posted: Tue Oct 10, 2006 7:54 am Post subject:

Apprentice

Joined: 22 Oct 2002
Posts: 31

The app team are telling me it's corrupt and considering it looks like this:

Code:

and a message on another queue looks like this:

Code:

00000000: 5246 4820 0000 0002 0000 0140 0000 0111 'RFH .......@....'
00000010: 0000 0333 4D51 5354 5220 2020 0000 0000 '...3MQSTR ....'
00000020: 0000 04B8 0000 0034 3C6D 6364 3E3C 4D73 '...Â¸...4<mcd><Ms'
00000030: 643E 6A6D 735F 7465 7874 3C2F 4D73 643E 'd>jms_text</Msd>'
00000040: 3C54 7970 653E 5364 6E44 6576 5473 743C '<Type>SdnDevTst<'
00000050: 2F54 7970 653E 3C2F 6D63 643E 0000 00E0 '/Type></mcd>...Ã '
00000060: 3C6A 6D73 3E3C 4473 743E 7175 6575 653A '<jms><Dst>queue:'
00000070: 2F2F 4352 4D43 4844 5132 2F43 524D 4348 '//CRMCHDQ2/CRMCH'
00000080: 4F52 442E 4352 532E 454E 5155 4952 592E 'ORD.CRS.ENQUIRY.'

it would appear that there's an issue.
_________________
2189 errors make me

jefflowrey

Posted: Tue Oct 10, 2006 8:00 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Another message on another queue may have come from another system and be destined for another system that is expecting there to be an MQRFH2.

Confirm that the receiving application is expecting an MQRFH2 (or a "JMS header").

Then ask the sending application team to confirm that they aren't doing anything funny with NameValueCCSID or trying to put noncompliant data into the JMS header/MQRFH2 (adding properties that aren't in allowable character sets, for example).
_________________
I am *not* the model of the modern major general.

mvic

Posted: Tue Oct 10, 2006 12:51 pm Post subject:

Jedi

Joined: 09 Mar 2004
Posts: 2080

2189 wrote:

The app team are telling me it's corrupt and considering it looks like this:

Please also post the MQMD for the "good" and "bad" messages. It will describe the encoding and CCSID the MQRFH2 header is intended to be in.

fjb_saper

Posted: Tue Oct 10, 2006 3:05 pm Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

And can you confirm that there was no conversion exit on any channel the message has travelled through?
_________________
MQ & Broker admin

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Message corrupt

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