|
Hi Anwar, My answer is tempered somewhat by the age of your releases, but should be generally correct and the expected behavior. So long as the database accepts the CCSID for the data, the DBCS in your case, the database and JDBC driver should convert as normal. That is, from the native CCSID to Unicode internally in the Java program and back to the native CCSID on output.. The data in a Data Queue should be in the default system CCSID, and again, converted by the Toolbox/JTOpen classes on input and output. All of that assumes that no one tried to get cute and put data in one character set or CCSID into a database with a different CCSID without proper conversion. The JTOpen/Toolbox people have been pretty careful about backward compatibility and you can probably move to a later version to avoid possible bugs. For more information, look under National Language Support ( NLS ) in the AS/400 documentation. There are also several redbooks dealing with i18n development. HTH, Joe Sam Joe Sam Shirah - http://www.conceptgo.com conceptGO - Consulting/Development/Outsourcing Java Filter Forum: http://www.ibm.com/developerworks/java/ Just the JDBC FAQs: http://www.jguru.com/faq/JDBC Going International? http://www.jguru.com/faq/I18N Que Java400? http://www.jguru.com/faq/Java400 ----- Original Message ----- From: "Mahmood, Anwar (Cognizant)" <MANWAR@xxxxxxxxxxxxxxxxx> To: <java400-l@xxxxxxxxxxxx> Sent: Tuesday, December 09, 2003 5:11 AM Subject: DBCS to Unicode > hi all, > I need to get data from a DB2 database (on a V4R1 system). It is a japaneses system and DBCS enabled. Can some one tell me that if i use JT400Mod0 to fetch data using jdbc or DataQ, what is the character set in which i will get it? and how do i convert it to Unicode? > Any help will be apreciated... > > regards, > Anwar >
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.