|
Just a quick correction.... "default 65535 CCSID" IIRC, 65535 used to be the default, but new machines now default to a correct CCSID based upon the primary language. HTH, 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 rob@xxxxxxxxx Sent: Friday, January 12, 2007 9:13 AM To: Midrange Systems Technical Discussion Subject: Re: MSSQL access iSeries data (not ifs) Sounds like a CCSID issue. The data was probably stored in the default 65535 CCSID. I've just given you one hell of a clue. If you search IBM for ODBC and 65535 you'll get hits like adding a connection string keyword like TRANSLATE or ForceTranslation Specifies whether or not to convert binary data (CCSID 65535) to text. Setting this property to 1 makes binary fields look like character fields. 0 = Do not convert binary data to text 1 = Convert binary data to text Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Jim Franz" <franz400@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 01/12/2007 09:03 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To <MIDRANGE-L@xxxxxxxxxxxx> cc 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 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.