Seems like the table in SQL Server was defined with unicode columns, makes
sense as I believe that's pretty much the standard for SQL Server.
You'd be best served by creating the column as unicode on the i.
If you're on a supported version of the OS, just use NCHAR or NVARCHAR data
types instead of CHAR/VARCHAR.
If on an older release, you'll have to use the GRAPHIC/VARGRAPHIC type and
assign the CCSID of 1200.
create table mytbl (
mycolA NCHAR(10)
, mycolB graphic(10) CCSID 1200
)
Both the above columns are 10 character (20 byte) Unicode columns:
Data Field Buffer Buffer Field Column
Field Type Length Length Position Usage Heading
MYCOLA GRAPHIC 10 20 1 Both MYCOLA
Allows the null value
Coded Character Set Identifier . . . . . : 1200
UCS2 or Unicode conversion . . . . . . . : *CONVERT
Normalize data . . . . . . . . . . . . . : No
MYCOLB GRAPHIC 10 20 21 Both MYCOLB
Allows the null value
Coded Character Set Identifier . . . . . : 1200
UCS2 or Unicode conversion . . . . . . . : *CONVERT
Normalize data . . . . . . . . . . . . . : No
Now the problem is, what to you intend to do with the data once it's on the
i?
If you're going to maintain it with a Java/.NET front end, you're fine.
They both handle unicode just fine.
If you think you'll be able to use a green screen program in a client
access 5250 session to maintain it...well think again.
It can be done, the 5250 data stream supports unicode. But the only 5250
emulator that does that I'm aware of is IBM's iAccess for the Web. The
regular IBM i Access for Windows emulator doesn't support unicode. I
suppose the new Java based client, IBM i Access Client Colution (
http://www-03.ibm.com/systems/power/software/i/access/solutions.html) might.
Take a look at this presentation...
http://www.think400.dk/files/Whats_with_these_ASCII_EBCDIC_Unicode_CCSIDs.pdf
Charles
On Thu, Apr 2, 2015 at 7:46 PM, Vicki Wilson <VWilson@xxxxxxxxxxxxx> wrote:
Hi all,
The saga with moving the database from SQL server to DB2 continues.
My C# code is upchucking on an update statement. One column has special
characters and I get a conversion error on the update. I tried to change
the column on DB2 to CCSID 65535 but I still get a conversion error -
different one this time.
Any thoughts? Can I do something fun with the SQL statement? Connection
String? This is a parameterized query using AddWithValue.
Regex or scanning the column every time seems like the least desirable
solution.
Thanks.
Vicki Wilson
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.