ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher.Mathru...@sybase.com
Subject Re: "encoding not supported"-error using iBATIS with db2 on z/os
Date Wed, 21 Nov 2007 20:21:25 GMT

<br><font size=2 face="sans-serif">I can't remember. That was almost 3
years ago and I've fortunately forgotten most of it. &nbsp;:-)</font>
<br><font size=2 face="sans-serif"><br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Christopher Lamey &lt;clamey@localmatters.com&gt;</b>
</font>
<p><font size=1 face="sans-serif">11/21/2007 12:12 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
user-java@ibatis.apache.org</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">&lt;user-java@ibatis.apache.org&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: &quot;encoding not supported&quot;-error
using iBATIS with db2 on z/os</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>On 11/21/07 1:08 PM, &quot;Christopher.Mathrusse@sybase.com&quot;<br>
&lt;Christopher.Mathrusse@sybase.com&gt; wrote:<br>
<br>
&gt; <br>
&gt; In addition, I've worked with DB2 previously on a z/OS system utilizing
the<br>
&gt; type driver supplied by IBM. The database was expecting EBCDIC and
the data I<br>
&gt; was working with in the Java world was ASCII coming in from an XML
document<br>
&gt; encoded in UTF-8. The JDBC driver did a marvelous job of converting
the ASCII<br>
&gt; to EBCDIC for me without me even needing to think about it. However,
one thing<br>
&gt; that you must be aware of is that there are ASCII characters that
do not map<br>
&gt; to EBCIDIC characters and there are EBCDIC characters that do not
map to ASCII<br>
&gt; characters. This is something that I spent a great deal of time on,
trying to<br>
&gt; map some obscure characters to the back-end system because it was
required.<br>
&gt; The end result was utilizing triggers to get around some of the issues.<br>
<br>
Out of curiosity, is EBCIDIC's lower range the same as ASCII like Unicode?<br>
<br>
Cheers,<br>
Chris<br>
<br>
<br>
</tt></font>
<br>

Mime
View raw message