Re: Is ccsid 65535 cvt to 37 painless?

Hi Jim,

I wouldn't expect it to be painless - depends why they have 65535 in the
first place! I've worked with clients across Europe who were recommended to
have 65535 (no translation) either because they had an app with its own
translation tables, or because at earlier version of OS/400 the whole
CCSID/QCHRID thing did not 100% work. For example, the AS/400 part sort of
worked, but ODBC and FTP etc didn't even look at CCSIDs. This is not of
course a problem if you are using 37!
It seems that more of the NLS stuff is working now at V5.2.
If possible you would need to plan the change very carefully, and somehow
test each component. Maybe one of the vendors involved has a 37 system you
could test on.
But as you say, do you really need to? If it ain't broke...
What is there to translate in webcgi? If you are at 37 maybe not much?
Good luck,

----- Original Message -----
From: "Jim Franz" <franz400@triad.rr.com>
To: <MIDRANGE-L@midrange.com>
Cc: <WEB400@midrange.com>
Sent: Thursday, November 28, 2002 12:16 AM
Subject: Is ccsid 65535 cvt to 37 painless?


> This is a multi-part message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> I have a customer V4r5 with default ccsid 65535, using
> ftp, CA transfers, async credit card comm using qascii code page
> conversion. Now need to add web cgi. The cgidev2 docs
> strongly suggest changing system to a proper ccsid, and
> is "usually" is painless. I don't have a spare system to test
> that theory.
> Is it truly required? Is it safe?
> I searched the archives and found lots of discussion about ccsid, but
> not really desribing how the change went (if they did it at all).
> Sorry for the post to two lists, but question equally applies.
>
> jim franz (who will be shot if i bring the applications down)
>
> --
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>