A couple of items:
1. You need a 5250 emulator that supports Unicode. Access for Web and HATS are two that do have this support, but straight Client Access (at least last I looked) does not.
2. The Unicode enabled emulators support Unicode CCSID 13488 (rather than 1200) the last I looked at them (which admittedly was several months ago).
3. The second parameter of the DDS CCSID keyword, field-display-length, allows you to control the size of the Unicode enabled field for display purposes. There are also quite a few other parameters on the CCSID keyword.
4. I have a presentation available on the web,
http://www.brucevining.com/Presentations/PPT_Presentations/Whats_with_these_ASCII_EBCDIC_Unicode_CCSIDs.pdf
which includes a simple example of changing a RPG *DSPF based application from CCSID 37 to CCSID 13488. The example shows a *DSPF panel supporting English, German, Cyrillic, and Chinese concurrently.
5. For those interested, the above presentation also has a COBOL version of the Unicode enabled application.
Bruce Vining
Bruce Vining Services
Åke Olsson <ake.olsson@xxxxxx> wrote:
I am working on a unicode conversion for an existing package. The requirements are that "certain" fields such as customer names and addresses should be unicode enabled so that users could enter these in any character set.
What I have done so far is change the DDS for the physical file to this:
A A1ADR1 R G REFFLD(ADR1)
A CCSID(1200)
Data type to "G" (Graphic) and the CCSID to 1200 (Unicode).
The field length for the character field in the field reference file is 35A.
I have changed the file and verified (using excel) that I can put as well as retrieve Japanese characters from the file.
The problem is with the 5250 interface.
When I define the fields on the display with a reference to the database file like so:
A A1ADR2 R O 5 2
The field suddenly uses 70 characters on the screen instead of 35. (On output and "both" fields the first 35 of these are high-lighted).
BUT regardless of whether the display file field is defined as character or graphic I can still not make the japanese characters that I "tweaked" into the file show on a 5250 session.
It seems as if I am missing something here. OR - do I require a separate version of Client Access to display japanese characters? I have tried to create sessions with different code-page but nothing seems to work.
Any advice greatly apreciated!
Med vänlig hälsning / Best regards
Åke Olsson
Pdb DataSystem AB
Box 433 SE 551 16 Jönköping Sweden visit: Brunnsgatan 11
phone: +46 (0)36 342976 mobile: +46 (0)705 482976 fax: +46 (0)36 34 29 29
ake.olsson@xxxxxx www.pdb.se
This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.
midrange.com
