This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
LotusScript's native string charset is Unicode - UTF-16. The same is true for Java. Notes documents' native charset is LMBCS, but the Notes classes handle conversions between UFT-16 and LMBCS. This part is all automatic.
The question is, what charset is DB2 giving you the data in? If it's not giving you UTF-16, then there needs to be a conversion somewhere. It might depend on the version of DB2 and on the configuration. There are many possibilities for Japanese data, including UTF-16, UTF-8 and several different character encodings that were designed and standaradized for the Japanese market and are still in use because they are better optimized for Japanese than any of the flavors of Unicode. If you can't find someone who can definitively tell you what charset this particular DB2 configuration is giving you, then you will need to test by querying some known data and looking at the actual byte values. You can do this in LotusScript by writing a loop that uses the Asc(). In Java, you can use the getBytes() method. You'll have to compare what you see against charts for different charsets to figure out what you're really getting.
Feedback response number WEBB9HKR94 created by ~Ned Nimfanakonyoopsi on 03/26/2014