V5R2 --> V5R3 CPYFRMIMPF and CPYTOIMPF

We have quite a few programs that use these 2 commands. Does anybody
know what I need to do to make sure those programs will still work
correctly after upgrade from V5R2 to V5R3?





CPYFRMIMPF and CPYTOIMPF command changes No conversion performed if
TOFILE field has no CCSID or a 65535 CCSID In prior releases, the
CPYFRMIMPF and CPYTOIMPF commands would create a temporary database file
when copying a stream file to a database file. The temporary file was
created with CCSID(*JOB). The temporary file was used as an intermediate
file that the stream file was copied to before the import file text was
processed and copied to the target database file. Any input stream file
text was converted to the job's CCSID when the stream file was copied to
the temporary database file. If the target database file (TOFILE
parameter) field did not have an explicit CCSID or had a CCSID of 65535,
the copied import file text would remain in the job's CCSID because it
was already converted when the import file was copied to the
intermediate, temporary database file. In V5R3, when the CPYFRMIMPF and
CPYTOIMPF commands copy an import file from a stream file to a target
database file, an intermediate database file is not used. If the TOFILE
field does not have an explicit CCSID or has a CCSID of 65535, no text
conversion will occur and the database file will contain the same
hexadecimal code points that existed in the original stream file. If you
need the text in the import file to be converted from the original
CCSID, make sure that the TOFILE field CCSIDs are specified and are not
65535. For additional information on ways to handle CPYFRMIMPF and
CPYTOIMPF command changes in V5R3, please refer to Informational APAR
II13784.