File Management - IBM

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
118 File Management V4R5
v INCREL that specifies a UCS-2 graphic field name
For more information on copying DBCS or UCS-2 fields, see “Copying DBCS files”
on page 209.
Converting System/370 floating point and null fields
To copy floating point fields and null fields that are in a System/370 format to an
AS/400 format, use FMTOPT(*CVTFLOAT) and FMTOPT(*NULLFLAGS)
respectively. You can use these two values together in one command:
FMTOPT(*CVTFLOAT *NULLFLAGS).
The FMTOPT(*CVTFLOAT) parameter on the CPYF command converts each
floating point field from System/370 hexadecimal format to the IEEE format that is
used by the AS/400. The CPYF command converts those fields that are identified
by the external description of the physical to-file.
The FMTOPT(*NULLFLAGS) parameter on the CPYF command takes the byte (or
flag) following each null-capable field and uses it to indicate if the corresponding
input field is null. The CPYF command takes the fields that are identified as
null-capable by the external description of the physical to-file. If the byte (or flag)
is blank (X'40') or contains X'00', the data is considered not null. Any other value
for the flag causes the corresponding input field data to be ignored and the output
value set to null.
If you use *CVTFLOAT or *NULLFLAGS and the input file is externally described,
the input file’s external description is not used in mapping the copied data.
When you use *CVTFLOAT and *NULLFLAGS (together or independently), make
certain that the to-file is an existing database, externally-described, physical data
file.
You cannot specify the *CVTFLOAT and *NULLFLAGS values when any of the
following conditions are true:
v You have specified RCDFMT(*ALL) for a multiple-format logical from-file
v You have specified any value other than the default for CRTFILE, and the to-file
does not exist
v You have specified a value other than the default for the FROMKEY, TOKEY,
INCCHAR, INCREL, SRCOPT, or SRCSEQ parameters.
When you specify either *CVTFLOAT or *NULLFLAGS, all other values for the
FMTOPT parameter are ignored. If you use both *CVTFLOAT and *NULLFLAGS
on one CPYF command, both values are recognized.
When you specify the *CVTFLOAT value (and have not specified *NULLFLAGS),
the expected from-file record length is the to-file record length. When you have
specified the *NULLFLAGS value, the expected from-file record length is equal to
the sum of the to-file record length and the number of null-capable fields in the
to-file. The from-file’s record length may not be less than the expected length. If
the from-file’s record length is greater than the expected length, an inquiry
message is sent to the QSYSOPR message queue to determine if the user wants to
continue. If the user continues, the trailing data (fields) in the from-file is truncated
in the to-file.