|
You bet! :-) But DASD space for the developers of 400 has never been too much of an issue. For instance, variable length fields are still rather an add-on than a native feature of the DB2/400. imho. Lo -----Original Message----- From: Clare Holtham [mailto:Clare.Holtham@btinternet.com] Sent: 16 July 2002 17:57 To: midrange-l@midrange.com Subject: Re: How to display German "extra" characters And presumably requires more disk? Clare ----- Original Message ----- From: "Raikov, Lo" <Lo.Raikov@MISYS.COM> To: <midrange-l@midrange.com> Sent: Tuesday, July 16, 2002 8:40 AM Subject: RE: How to display German "extra" characters > Well, when you program in Java on the 400, Unicode-to-EBCDIC SBCS (and back) > translation tables are normally involved. After all, Java is a Unicode beast > and as such is fully supported by AS/400. Of course, storing Unicode data > in AS/400 database (DB2/400? DB2 UDB for iSeries 400?) is much less common. > > > Lo > > -----Original Message----- > From: Clare Holtham [mailto:Clare.Holtham@btinternet.com] > Sent: 16 July 2002 17:32 > To: midrange-l@midrange.com > Subject: Re: How to display German "extra" characters > > > Lo, > Thanks for the correction! Good to see things are moving on somewhat. I > worked with an application that did use the translation tables. > I didn't know that ODBC is now aware, though I did know that Unicode is now > supported on the AS/400 - but how many applications have taken it up?? > cheers, > Clare > > ----- Original Message ----- > From: "Raikov, Lo" <Lo.Raikov@MISYS.COM> > To: <midrange-l@midrange.com> > Sent: Tuesday, July 16, 2002 8:25 AM > Subject: RE: How to display German "extra" characters > > > > 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. > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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.