RE: MSSQL access iSeries data (not ifs)

Jim,

Sounds as if the DB tables are (incorrectly) coded with CCSID of 65535.

The "correct" answer is to change the CCSID of the table to the right
one.

The workaround is to have the ODBC/.NET driver force translation of
CCSID 65535.

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx 
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Friday, January 12, 2007 9:04 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: MSSQL access iSeries data (not ifs)

I need to point a MS developer in the right direction. 
He is using sql to pull data from iSeries qsys.lib/.... and 
claims the data is encrypted. I assume he is looking
at ebcdic, not ascii. Is there something he can do 
in his selections to get the ebcdic to ascii?
This is a big data analysis project and will involve 
many selects, many tables. There is a possibility
Oracle is in this mix as well.
Jim Franz

-- 
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.