× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I really just have a single character string within the display that needs
to be converted from CCSID 13488 (unicode UCS_2) into our normal 65535
encoding so that it will be readable.

So far, nothing easy is jumping out at me. Still searching the IBM site.

Rich

--------------------------------------------------------------------------

On 4/30/2012 2:19 PM, James Lampert wrote:

I have a database file that contains GRAPHICS fields that appear to be
unicode. A DSPFFD shows the fields with the following settings:

Coded Character Set Identifier . . . . . : 13488
UCS2 or Unicode conversion . . . . . . . : *CONVERT

I can see the field contents when I look at them through SQL from
iNavigator, but I want to be able to show the field contents in a 5250
display.

You need to recognize the version of EBCDIC that the terminal is using,
and translate the Unicode to it, rendering any characters the terminal
can't display as x'1C', x'1E', or x'1F'.

<plug> QuestView will do this for US/Canada/Netherlands, Multinational,
Austria/Germany, Denmark/Norway, Finland/Sweden, Canadian French, Spain,
Italy, France, UK, and "new" Turkish. </plug>

It gets complicated if you have a DBCS terminal. More complicated than
anything I've ever had to deal with.

Pity that IBM never made, say, a Unicode-native version of a 3487.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.