An article in the October issue of SystemiNetwork said that when a java app accesses a DB2 character field the string must be converted from single-byte EBCDIC to double-byte Unicode. And the way to prevent the overhead associated with this conversion is to define character fields as GRAPHIC/VARGRAPHIC using a CCSID for UTF-16/UTF-8/UCS-2. It did not mention anything about RPG accessing DB2 fields defined as GRAPHIC and if it needed to convert it from double byte to single byte. Does any know if RPG needs to do this? We are using java apps for some web work but we have no database file that is only accessed by Java. Everything is a mix of Java and RPG. If Java likes double-byte over single-byte and will run faster using double-byte and RPG does not care which it uses I might consider using GRAPHIC. If RPG has to do extra work to use GRAPHIC then I need to consider where the extra overhead needs to go. Java is mostly doing single record and small record set (<100 records) work. RPG is doing the same but also does large record set (up to 5M in some cases) work
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.