|
I'm sorry to pop in like that, but the message quoted is not quite correct on several accounts. First of all, translation tables in QUSRSYS are used only for CHRID character conversion (I forget now what parts of OS make use of them - pre-version 3? one of them was OV/400, now extinct). Most of the CCSID-based character conversion makes use of core translation tables one cannot modify. Second, ODBC is usually CCSID-aware. Please refer to CA/400 documentation for details. Third, Unicode is now supported by AS/400 (Oops! iSeries eServer 400? eSeries iServer 400? never mind), so you can actually choose whether to store your data in Unicode, DBCS code pages (IBM double-byte coding scheme) or SBCS (single-byte coding scheme). I suggest you browse the following manuals (both available on I-net): AS/400 International Application Development AS/400 National Language Support Lo >Michael, >Welcome to the brain-bending world of NLS! Firstly, you should keep the >system code page as US (037) if you are in the US. The AS/400 translates the >characters according to the code page tables in QUSRSYS (for example >Q857A7AA3S is Windows 857 to Turkish 1026). Sometimes you have to modify etc.
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.