MSSQL access iSeries data (not ifs) -- MIDRANGE-L

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

Subject: MSSQL access iSeries data (not ifs)
From: "Jim Franz" <franz400@xxxxxxxxxxxx>
Date: Fri, 12 Jan 2007 09:03:42 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: MSSQL access iSeries data (not ifs) , rob
RE: MSSQL access iSeries data (not ifs) , Wilt, Charles

This mailing list archive is Copyright 1997-2025 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.