Re: Problems opening files with different CCSID's

That makes sense. Is there a work-around?




Violaine Batthish <batthish@xxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
11/15/2005 08:41 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] Problems opening files with different CCSID's






Hi Chris,

There are a couple of things to consider.
1) Certain DBCS CCSIDs  do not contain the lower case English characters.
I know for sure that this is true for CCSID 290.  I have been unable to
find out about CCSID 5026 so far.
2) When using SEU in an emulator session, source is displayed in the CCSID
of the job (usually determined by the emulator preferences).  So for
example, with CCSID 290, in a Personal Communication emulator session,
which is configured for CCSID 37, you will see lower case English letters
in a file with CCSID 290, BUT, when you load in Remote Systems Editor, you
should see the actual Japanese characters in CCSID 290 that have the same
HEX value as the lower case English letters.  Thus RSE actually displays
the source using the CCSID of the file, not the CCSID of the job.

I hope this helps.

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab

You know you've achieved perfection in design, not when you have nothing
more to add, but when you have nothing more to take away. - Antoine de
Saint-Exupéry



wdsci-l-bounces@xxxxxxxxxxxx wrote on 15/11/2005 08:12:56:

> Thank you for your extremely long-winded albeit completely useless post.
I
> am fully aware of how computers store information and I am fully aware 
of

> what CCSID's are and how they work. What I don't understand is how seu
can
> properly render file members of different CCSID's (sda can do this too)
> while WDSC, a purportedly superior product to seu, cannot. Client access
> a\has nothing to do with this and I if the only way to make this work is
> to have one pc configured in Japanese and one in English then the
solution
> is absolutely unacceptable. WDSC should be able to translate the member 
I

> want to open based on the CCSID of the file that contains it. I thought
> that maybe someone on this board would have met this challenge before me
> and found a solution or at the very least I wanted someone on the WDSC
> development team to become aware of the problem.
>
> Thank you
> Chris