Charles,
I'm not up on the issues with the CPYxxxIMPF commands.
However, after reading one of Rob's suggestions, I changed the CCSID on both of our systems (production and backup) from 65335 to 37 in the middle of the day while processing was going on. Never burped. That was a couple of years ago, if my erratic memory serves me correctly. The few instances of the CPYTOIMPF command that I have (don't use the FRM versions) worked fine after that without any issues.
Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Monday, October 06, 2008 9:42 AM
To: Midrange Systems Technical Discussion
Subject: CCSID 65535 v5r2-->v5r4 upgrade
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!
Charles Wilt
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
