× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Since this customer's files are decades old, I am certain all tables are at IBM's original 65535. It's no small deal to reset all files in an enterprise application, retesting every CA download, upload, communication process, cpyfrm.../cpyto..., other products, etc. Has everyone else but me
cleared this hurdle?
jim franz

----- Original Message ----- From: "Wilt, Charles" <CWilt@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, January 12, 2007 9:17 AM
Subject: [SPAM] 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.



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

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.