A) Absolutely. There are several ways to convert UTF-16 to/from EBCDIC. They include system APIs such as iconv(), database logical files, and even the COBOL MOVE statement.
B) The term “Chinese” is not sufficient to answer your question. Are we talking Traditional Chinese or Simplified Chinese? More important though, I believe a better design would be to change your back-end to support UTF-16 directly rather than designing to EBCDIC. With EBCDIC you are looking at different CCSIDs (and databases) for each language. Going to UTF-16 you can have one database (encoded in UTF-16) which can support Traditional Chinese, Simplified Chinese, Korean, and Japanese in addition to the traditional SBCS-based languages.
Your C, D, and E are based on an EBCDIC implementation, which I really doubt you want to do given the other options available to you. COBOL has direct support for Unicode (UCS-2 and UTF-16). Check out the NATIONAL support of ILE COBOL. You will also find excellent Unicode support in the i database, display file, printer file, message handling, etc.
Bruce Vining (who has done a lot of Unicode work, with many companies, over the years)
<a href=”http://www.brucevining.com/”>Bruce Vining Services</a>
I can give some answers, but not all:
The CCSID in the iSeries objects must be 935 (Simplified Chinese)
The code page in the PC for Simplified Chinese is 1388
The Data Type in the DSPF/PRTF must be O (Other)
Its not possible to copy the data for existing files if the data was entered in DBCS prior to the recompilation (as it has other CCSID)
This is what I can help.