| Author |
Message
|
| satya2481 |
 Posted: Mon Oct 28, 2013 6:24 am Post subject: WMB V7 MQInput Node Conversion Issue From 1146 |
 |
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi All,
We are facing an issue while trying to convert the message from 1146 to 1208 Code page. We are using WMB V7 and the Broker is Running on zLinux. Our development Broker is on Windows Platform.
1. Message is sent from an Application with Code Page = 1146 Format = MQSTR
2. Using MQInput Node with XMLNSC Domain and selecting the Conversion option with Convert encoding = 273 and Convert CCSID = 1208
3. Message is not getting parsed with this configuration
We tried below options as well and nothing working. In all cases getting parser error 5209 or BIP error code 1504 (Which is not having and description in help)
Convert encoding = Blank
Convert CCSID = 1208
Convert encoding = 473
Convert CCSID = 1208
We found below option, which is working fine. But is there any way to fix the issue using MQInput node only, instead of PARSE in ESQL?
1. Read message as BLOB without any conversions set in MQInput node
2. Convert the BLOB Message to required domain using below ESQL Statement
CREATE LASTCHILD OF OutputRoot DOMAIN 'XMLNSC' PARSE(InputRoot.BLOB.BLOB ENCODING 273 CCSID 1208 );
3. Proceed further with Logic
We are inbetween System Integration testing and as of now testing is stopped because of this conversion issue. Any kind of help is much appreciated.
Regards
Satya |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Oct 28, 2013 6:52 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Disable conversion on the MQInput node. |
|
| Back to top |
|
|
| satya2481 |
| Posted: Mon Oct 28, 2013 9:30 am Post subject: |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
| Tried that option as well... Its not working... Hence ended up Parsing in ESQL code using a Compute node Just after the MQInput node.... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 28, 2013 7:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Which would mean that the incoming message is not in the CCSID it claims to be! Get back to the producer and have him fix it! 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| satya2481 |
| Posted: Tue Oct 29, 2013 9:58 pm Post subject: |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
| Quote: |
| Which would mean that the incoming message is not in the CCSID it claims to be! |
If Message is not in the CCSID it claims then how ESQL code mentioned below able to convert it into to 1208? My understanding is its able to convert because its encoded correctly in 1146 hence able to convert from BLOB to MRM using 1208 code page. Correct me if I am wrong.
Mean time I will try to speak with the Consumer application team.
So basically you are trying to tell that Broker should be able to automatically understand the Code page and no need to use any conversion option at the MQInput node as well as in the ESQL code. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Oct 30, 2013 12:04 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| satya2481 wrote: |
| Quote: |
| Which would mean that the incoming message is not in the CCSID it claims to be! |
If Message is not in the CCSID it claims then how ESQL code mentioned below able to convert it into to 1208? My understanding is its able to convert because its encoded correctly in 1146 hence able to convert from BLOB to MRM using 1208 code page. Correct me if I am wrong.
Mean time I will try to speak with the Consumer application team.
So basically you are trying to tell that Broker should be able to automatically understand the Code page and no need to use any conversion option at the MQInput node as well as in the ESQL code. |
Yes that is correct. By reading the messages as a BLOB and then converting it in ESQL you are ensuring that the CCSID/Encoding values that are defined in the MQMD are ignored.
You have encountered a common problem here. A lot of people do not really understand the proper use of Code Pages and Encoding values. Sometimes they stick some value on them and get rid of the data thinking that someone else can deal with it...
The problem is that 'Sods Law' will always strike here. you might have found a solution in this case but what happens is there is a new release of the software that is sending you the data and they decide to encode the data in EBCIDIC? Your conversion in ESQL will fail.
It is far better to educate the people sending you the data so that they get it right in the first place.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| satya2481 |
| Posted: Wed Oct 30, 2013 12:33 am Post subject: |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Thank you very much for the detailed explanation, it helps us to inform sender application.
We are going to have a discussion with the Sender application team and try to provide complete details.
Will keep posted on the end results and solutions. |
|
| Back to top |
|
|
| satya2481 |
| Posted: Sun Nov 03, 2013 7:44 am Post subject: |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi All,
Consumer/Source application is updated (Not sure about what changes are done). Now our flow able to read the message and parse it correctly even when code page is 1146. So the issue got resolved and we are able to proceed with testing.
- Satya |
|
| Back to top |
|
|
|
|
