UNICODE on AS400

[Frank.Kolmann@xxxxxxxxxx]

Thanks for the info Bruce,
As per the manual I can set up SBS for the devices and
set the CHRID on the CRTDEV.
Perhaps you can help me with some DBCS considerations.
It seems to me that UNICODE supercedes DBCS.
UNICODE also doubles you disk space requirements,
but disk is relatively cheap, programmers cost.
We can buy a DBCS enabled version of an application.
I see that a UNICODE implementation is not
compatible with DBCS, am I right.

Frank Kolmann


>>
>>I understand the 5250 data streams do not support UNICODE,
>>so what do you do regarding  device support.
>>
>
>Frank,
>
>On the iSeries, Unicode data is typically treated as Graphic data
>using CCSID 13488.  If, in your *DSPF, you define a field as Graphic
>and 13488 then workstation data management will automatically convert
>the data from 13488 (in your program variable) to the CHRID associated
>with the device the *DSPF is attached to.
>
>So if PARTNAME is Unicode/UCS2 in your application (that is,
>x'00 500069007000650020002000200020...'); then the following line
>in your *DSPF
>
>A            PARTNAME      20G  B  9 24CCSID(13488)
>
>will cause 'Pipe   ' to show on your display device.  Likewise the
>user can type in '#2 PIPE' and your program will receive
>x'00230032002000500049005000450020...'.
>
>You are limited to the character set supported by the display device
>so that is a definite consideration in what data to present to the
>user, but this does allow a degree of Unicode access from 5250 type
>devices.
>
>Bruce