Tweet
** This thread discusses the article: Oh, Those Pesky Character Sets **
** This thread discusses the Content article: Oh, Those Pesky Character Sets **
0
** This thread discusses the Content article: Oh, Those Pesky Character Sets **
0
-
-
Oh, Those Pesky Character Sets
** This thread discusses the article: Oh, Those Pesky Character Sets **
We are converting over to Unicode. The data base that we are currently working on is all English, we will be converting over a data base that is double-byte later on. The amount of work involved in modifying the programs is quite extensive. I have been in contatct with IBM and they are supposed to be modifying their internal code so you will not be required to program for using Unicode and charater fields in the same application, the data manipulation will all be done behind the scenes without any programming be required on the developers part. There currently is no date when this will be completed. In the meantime you still need to Programmatically make the changes. One of the other Gotchas IBM has is you can not use Files that have Unicode Fields in them in CL Programs. You can Declare the File (DCLF ALWGRAPHIC(*YES)) with the Allow Graphics Key Word so the program will compile but try passing in a parameter that you want to use in positioning to in the file using the OVRDBF Command,or just try reading the File using the RCVF Command. Using the Override Command will cause the application to terminate when you do the RCVF Command as the field used for positioning is character and the field in the file is Unicode. If you just read the file using the RCV File the Unicode fileds will all appear as garbage, as CL Programs do not no how to handle graphic fields. IBM has not indicated what will be done, if anything, to correct this problem. If anyone has additional information on using Unicode in CL Programs, please e-mail me at mkatz@HAVIGS.com. Regards, Mike Katz
Comment