× 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.



Hello All,

I have this situation on which i have never worked and have a limited
knowledge.

There is a double byte i-series i.e. which supports English as well
Japanese language. I have a subfile program for file maintenance where
users can enter English as well Japanese language. I am able to enter the
Japanese character on display screen fields and successfully able to
update the physical file as well. However, when i go back to the same
program to see the inserted/updated data, it doesn't show up. However, if
i do RUNQRY on the physical file i can see the updated/inserted data.

I have compiled the display file with DBCS enabled i.e. IGCDTA as *YES,
IGCEXNCHR as *YES and CCSID as 5026 (for Japanese). Also, i have mentioned
the physical file field data type as O to indicate DBCS Open-Data i.e.
CCSID as 5026 in which different language characters need to be stored.

Is there anything else that i should consider while compiling the display
file/program/physical file or what could be the probable reason preventing
the Japanese characters to appear on the screen?

TIA.


Kind Regards,

Anupam Sinha


Anyone can give up. Its the easiest thing in the world to do. But to hold
it together, when everything seems like falling apart ;Thats true
strength.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.