Re: ccsid problem

i used both methods (create and import) so that would explain my different 
properties on the files.

my testing shows that my wdsc i5 connection job has a different ccsid (273) 
than my terminal session job (65535). seems that there is some configuration 
work to do. thanx again.

spelling: no prob.

-----Ursprüngliche Nachricht-----
Von: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im 
Auftrag von Violaine Batthish
Gesendet: Donnerstag, 24. August 2006 16:19
An: Websphere Development Studio Client for iSeries
Betreff: Re: [WDSCI-L] ccsid problem

Hey  Mihael (sorry for misspelling your name earlier)

There are 2 answers for your question  :-)
When you create a file in an iSeries project, the CCSID of the file is
supposed to default to *JOB (unless you pressed the Next button after the
first screen of the wizard and changed it).  I'm guessing if the file
already existed on the iSeries then the CCSIDs could potentially become
out-of-sync.

If the file was automatically created using the Make available offline or
Add to iSeries project action, then the file CCSID should have been
retrieved correctly from the host file.  This would also apply to files
added when remote objects appear in your project, and you've added a file
that way.

Hope this helps!

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 08/24/2006 09:59:35 AM:

if i edit the files in wdsc an then compile (transfer the source to
the i5) then the umlaute are screwed up.

the ccsid in the file properties doesn't have the same value as on
the i5. changed it and now it's working. thanx a lot.

but why does it have a wrong ccsid in the first place? is there a
property somewhere where i define what ccsid new resources have?


-----Ursprüngliche Nachricht-----
Von: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@midrange.
com] Im Auftrag von Violaine Batthish
Gesendet: Donnerstag, 24. August 2006 15:44
An: Websphere Development Studio Client for iSeries
Betreff: Re: [WDSCI-L] ccsid problem

Hi Michael,

I believe compilers use the CCSID defined for the file, unless the CCSID

is

65535, in which case the job ccsid is used (I am guessing that this is

your

scenario).
Does the file CCSID appear correctly in the file properties for the
project?
When you look at the member on the iSeries, does the umlaute appear
correctly?
I am assuming that when you compile the member from an emulator session,
the member compiles, even after its been pushed from the project.  Is

that

so?

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab


wdsci-l-bounces@xxxxxxxxxxxx wrote on 08/24/2006 08:01:30 AM:

hi,

i got a little problem with the ccsid. i'm relative new to wdsc and i
hope the solution will be a quick and easy one.

problem: if i try to compile a program from the iseries project
perspective then the german umlaute and some other characters get
screwed up. i think it is related to the ccsid. if i logon to the i5 in
a 5250 session i get

CCSID        65535
DFTCCSID     273

if i do a user defined action in wdsc with a DSPJOB OUTPUT(*PRINT) i

get

CCSID        273
DFTCCSID     273

how do i change the ccsid in websphere for the connection? (or is it
something else?)

thanx in advance

mihael