| Author |
Message
|
| mail2me.venky |
 Posted: Wed May 23, 2012 11:01 am Post subject: Encoding issue in ESQL MONK-urgent |
 |
|
Apprentice
Joined: 11 May 2012
Posts: 26
|
In my project, message is coming from external MQ in utf-8 encodingformat to egate monk eway.
My Monk component has input endoing as ASCII and output as ASCII.
While this monk code migrated to WMB ESQL , i want to implement same scenario. So i have set output encoding as ASCII.i.e ccsis as 819.
But while comparing old monk output and new esql cod output, i am facing encoding issue like , for the same input, different encoded characters in egate monk and WMB esql.?
How can i solve this issue? input is MRM and output is MRM for WMB.
How can i use asbitstream function ?
Please reply.
Thanks
varun  |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed May 23, 2012 11:09 am Post subject: Re: Encoding issue in ESQL MONK-urgent |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mail2me.venky wrote: |
| So i have set output encoding as ASCII.i.e ccsis as 819. |
That's not the ASCII code page, it's an ASCII code page.
| mail2me.venky wrote: |
| But while comparing old monk output and new esql cod output, i am facing encoding issue like , for the same input, different encoded characters in egate monk and WMB esql.? |
Then presumably e*Gate isn't using 819 as a code page. How did you determine this was the correct value?
| mail2me.venky wrote: |
| How can i solve this issue? |
Use the correct code page.
| mail2me.venky wrote: |
| How can i use asbitstream function ? |
Any way you want to if that's the way you need it.
Why do you want to use it? Why do you think it will help with the problem you describe? Or are you just randomly picking functions with CCSID in their parameter list in the hopes of hitting the magic one?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 23, 2012 11:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Also, if you have an urgent problem, you're better advised to raise a PMR.
We're not a support desk. We don't have an SLA.
Nor are we a training resource you can rely on because you don't know how to do the task you've been given.
Though thanks to the efforts of 1 member, you'll found countless links to where you can obtain the needed training.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed May 23, 2012 11:52 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Vitor wrote: |
| Though thanks to the efforts of 1 member, you'll found countless links to where you can obtain the needed training. |
Ah, Vitor, aren't you nice. Thanks for the complement. ... Vitor says Training !! 
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 23, 2012 12:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| Ah, Vitor, aren't you nice. |
I'd hate you to think I don't like you.
| lancelotlinc wrote: |
| Thanks for the complement. |
Not the term I'd have applied to my statement, but I can't see why my views would suddenly become relevant.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu May 24, 2012 2:20 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
You said:
| Quote: |
| message is coming from external MQ in utf-8 encodingformat |
and then you said:
| Quote: |
| My Monk component has input encoding as ASCII |
So...you are getting the full range of Unicode characters in your input message, but the downstream application can only handle 256 of those characters ( the ones that are supported by whatever ASCII code page it uses ).
Important question: What is your strategy for handling this problem? What was Monk doing when it encountered non-ASCII characters? |
|
| Back to top |
|
|
| mail2me.venky |
| Posted: Fri May 25, 2012 5:05 am Post subject: Element 'C001E_G_NM_INFO' has unbounded maxOccurs when the e |
|
|
Apprentice
Joined: 11 May 2012
Posts: 26
|
<xsd:element maxOccurs="unbounded" minOccurs="0" name="C001E_G_NM_INFO">
<xsd:complexType>
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsStructRep dataElementSeparation="FixedLength" messageSetDefaultRep="Text1"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="$~\u003ePGN-NAMEINFO\u003c~$" name="C001E_NM_INFO_L_ID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="18" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="C001E_NM_TYPE_CD" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="2" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="C001E_NM_INFO_LGG_CD" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="2" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="C001E_PTY_NM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="50" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element default="\u000d\u000a" name="Newline" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="2" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="C001G_G_FSC_NAT">
<xsd:complexType>
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsStructRep dataElementSeparation="FixedLength" messageSetDefaultRep="Text1"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="$~\u003ePGN-FISCLNAT\u003c~$" name="C001G_FSC_NAT_L_ID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="18" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="C001G_G_FSC_NAT">
<xsd:complexType>
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsStructRep dataElementSeparation="FixedLength" messageSetDefaultRep="Text1"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="$~\u003ePGN-FISCLNAT\u003c~$" name="C001G_FSC_NAT_L_ID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="18" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
The above is part of mxsd. i am getting below warnings for all unbounded segments.
Element 'C001E_G_NM_INFO' has unbounded maxOccurs when the enclosing structure has Data Element Separation 'FixedLength'. It must be the last member of the structure. Physical format: 'Text1'.
Element 'C001G_G_FSC_NAT' has unbounded maxOccurs when the enclosing structure has Data Element Separation 'FixedLength'. It must be the last member of the structure. Physical format: 'Text1'.
Can someone help me to solve this warnings? Thanks in advance. |
|
| Back to top |
|
|
| mail2me.venky |
| Posted: Fri May 25, 2012 5:12 am Post subject: Encoding issue solved |
|
|
Apprentice
Joined: 11 May 2012
Posts: 26
|
Hi Friends
Encoding issue is solved. i just pumped the input message in ASCII format in MQinput node and i viewed the output message in notepad. All the encoded characters in input as just same in output also.
Thanks to all for your kind help.
bye. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 25, 2012 5:14 am Post subject: Re: Element 'C001E_G_NM_INFO' has unbounded maxOccurs when t |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mail2me.venky wrote: |
| Can someone help me to solve this warnings? |
Can you explain what this has to do with the code page problem you originally posted?
As to the warnings, they're fairly self-explanitory. They're telling you your model doesn't make sense, which it doesn't. If you have an unbounded array of fixed length elements that isn't the last member of the structure, how do you know when it stops repeating and the next element starts?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri May 25, 2012 5:47 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Encoding issue is solved. i just pumped the input message in ASCII format in MQinput node and i viewed the output message in notepad. All the encoded characters in input as just same in output also. |
Are you sure that 'solved' is the correct word. Did you change the application that produces the MQ message to use ASCII instead of UTF-8? If not, you should change your statement to 'Encoding issue did not cause my sniff test to fail'. |
|
| Back to top |
|
|
| mail2me.venky |
| Posted: Fri May 25, 2012 10:10 am Post subject: MXSD issue |
|
|
Apprentice
Joined: 11 May 2012
Posts: 26
|
HI
The mxsd issue is completely new one.
it is not connected with encoding issue.
Regarding the encoding issue, i didnt make any single line code change.
My mistake is,i saved the output message in a file and then opened with ultraedit tool. hence there is some encoding loss.may be so
when i opened the saved message in notepad at first , i got the required result.
also earlier i pumped the message to Queue in utf-8 format instead of ascii format.
this is very tricky for me.
Lets now discuss with mxsd issue . this is new challenge for me.
Thanks
varun. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 25, 2012 10:17 am Post subject: Re: MXSD issue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mail2me.venky wrote: |
The mxsd issue is completely new one.
it is not connected with encoding issue. |
Then what's it doing on this thread?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 25, 2012 10:18 am Post subject: Re: MXSD issue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mail2me.venky wrote: |
| Lets now discuss with mxsd issue . |
I did. What more is there to "discuss"?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mail2me.venky |
| Posted: Fri May 25, 2012 11:39 pm Post subject: |
|
|
Apprentice
Joined: 11 May 2012
Posts: 26
|
Friends.
I have moved the mxsd issue to new thread.
Thanks for your support
varun |
|
| Back to top |
|
|
|
|
