Re: CCSID 65535 v5r2-->v5r4 upgrade

Charles,

You do not tell us what problems you have had with this issue so far.

Mine was:
When using files, created by SQL or CPYF on a previous release, and try
to use CPYxxxIMPF, we got the same CCSID problems.

After changing the system value for CCSID to 37, at V5R3, I deleted those
files first, recreated them with the next query run and had no problems
with the CCSID conversion, no garbage after a CPYTOIMPF.

For me changing the system value for CCSID and recreating the PFs solved
it.

I hope I made myself clear.

With regards,
Carel Teijgeler

*********** REPLY SEPARATOR ***********

On 7-10-2008 at 8:10 Charles Wilt wrote:

So has anybody else got any input?


On Mon, Oct 6, 2008 at 10:42 AM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

All,

I'm aware of issues regarding CPYxxxIMPF and CCSID 65535 when moving to

v5r4 from v5r2 or earlier due to the changes at v5r3.

I'm looking for additional issues others may have been bit by.

Particularity in scenarios were there are multiple systems involved,

some at v5r2, some at v5r4, some with CCSID 65335 and some with CCSID 37.

I'm trying to make a case that we should change everything to 37. Since

all our boxes are in the US with US users only.

I'm also pushing for looking at any existing file on the boxes that has

CCSID 65535 to see if it should be changed.

Thank for the ammo!