Problems opening files with different CCSID's

You are welcome Chris.
I often get the response you gave so I try to explain in detail.
The short answer, is I dont think what you are asking for is possible 
unless the AS400 uses a UNICODE type encoding methodology. How are you
running SEU, if it is Client Access then I dont believe it does what you
claim. When I configue my Client Access session as code page 1399 I see
both Japanese and LC Latin case but the Japanese SBCS is not rendered 
properly.
If you have a SEU solution I am interested so I can go back to one PC on 
my desk.

You are asking WDSCi to on-the-fly switch to different CCSIDs.  I dont
think that is possible. You need to have loaded on the PC every possible
CCSID for every language. That is why MS Windows uses UNICODE.  It may be 
possible to on-the-fly translate AS400 CCSIDs to MS UNICODE but I guess
that is beyond the scope of WDSCi.

Frank Kolmann

>date: Tue, 15 Nov 2005 06:20:58 -0700
>from: michael@xxxxxxxxxxxxxxxxxx
>subject: RE: [WDSCI-L] Problems opening files with different CCSID's
>
>So you opened a PMR with IBM?
>
>> -------- Original Message --------
>> Subject: Re: [WDSCI-L] Problems opening files with different CCSID's
>> From: ChrisBougher@xxxxxxxxxxx
>> Date: Tue, November 15, 2005 8:12 am
>> To: Websphere Development Studio Client for iSeries
>> <wdsci-l@xxxxxxxxxxxx>
>> 
>> 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
>> --