| Author |
Message
|
| gs |
 Posted: Mon Jun 11, 2012 11:31 pm Post subject: Message parser/message set overriding MQInput node settings |
 |
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
Hi,
Messages that contain parser & message set information in the RFH2 header (Message Type: mrm, JMSType (Fmt): <SomeOtherMessageSet>) are read into a message flow.
This invalidates the XMLNSC / <MyMessageSet> settings on the MQInput node and there doesn't seem to be any way of overriding whatever is set in the message.
Is this really expected behaviour? I'd prefer not to do a workaround using BLOB parser and a ResetContentDescriptor node.
WMB version: 7.0.0.4
Platform: Windows XP
Thanks |
|
| Back to top |
|
 |
| Esa |
| Posted: Tue Jun 12, 2012 12:04 am Post subject: Re: Message parser/message set overriding MQInput node setti |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| gs wrote: |
Is this really expected behaviour? |
Yes. The settings in the message override the defaults set in the MQInput node. |
|
| Back to top |
|
|
| gs |
| Posted: Tue Jun 12, 2012 12:45 am Post subject: |
|
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
Thanks,
Apparently I didn't read the manual properly:
| Quote: |
If the incoming message has an MQRFH2 header, you do not have to set values for the Input Message Parsing properties because the values are derived from the <mcd> folder in the MQRFH2 header; for example:
<mcd><Msd>MRM</Msd><Set>DHM4UO906S001</Set><Type>receiptmsg1</Type>
<Fmt>XML</Fmt></mcd>
If you set values, and those values differ from the values in the MQRFH2 header, and the <Msd> element is a valid domain, the values in the MQRFH2 header take precedence. |
Also found this post:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/messaging/entry/wmb_parsing_messages_with_message?lang=en |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 12, 2012 4:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
It's assumed that whoever wrote out the message would code the correct values to allow the message to be parsed.
Given the number of posts on this forum where the sender of the message apparently can't even set the code page correctly, that may be a rather optimistic assumption.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 12, 2012 5:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| This is not true of the BLOB domain. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 12, 2012 11:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| This is not true of the BLOB domain. |
Though I raise my eyebrow at the use of "parse" and "BLOB" in the same line. Accepting that the BLOB is indeed converted into a message tree.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jun 12, 2012 11:41 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Though I raise my eyebrow at the use of "parse" and "BLOB" in the same line. |
Me, I raise my glass to it. If you had spent most of the last 10 years writing parsers, you would too  |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 12, 2012 11:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kimbert wrote: |
| Quote: |
| Though I raise my eyebrow at the use of "parse" and "BLOB" in the same line. |
Me, I raise my glass to it. If you had spent most of the last 10 years writing parsers, you would too |
I bow before the God Of Parsing 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
