× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



From the V5R3 MTU

CPYFRMIMPF and CPYTOIMPF command changes . . . . . . . . . . . . . . .26

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. Record delimiter (RCDDLM) parameter change
RCDDLM(*ALL) will find the first occurrence of a single or double
character combination of carriage-return and line-feed and use that value
as the record delimiter. Character strings containing a null character
(X'00') allowed only in binary fields In previous releases, the CPYFRMIMPF
and CPYTOIMPF commands treated character strings containing a null
character (X'00') as acceptable values for any field. In V5R3, character
strings containing a null character (X'00') are allowed only for binary
type fields. Binary type fields are BINARY, VARBINARY, BLOB, CHAR FOR BIT
DATA, or CHAR CCSID(65535). A null character (X'00') encountered in a
non-binary field will produce a data mapping error.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.