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

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.