- 论坛徽章:
- 0
|
不太确认是否是这个message
Message ID . . . . . . . . . : CPF5029
Message file . . . . . . . . : QCPFMSG
Library . . . . . . . . . : QSYS
Message . . . . : Data mapping error on member &4.
Cause . . . . . : A data mapping error occurred on member &4 file &2 in
library &3, because the data fields in record number &6, record format &7,
member number &8 are in error.
Recovery . . . : If the record number is zero, the error occurred on an
attempt to put or update a record through a logical file, or the error
occurred on a group by operation, or the error was caused by a default
value, or the error was caused by a null value in the record. See
previously listed message CPF5035 or CPD5036 to determine which fields are
in error. Change the fields that are in error and try the operation again.
If the record number is not zero, the error occurred on an attempt to read
an existing record from a file. See previously listed message CPF5035 or
CPD5036 to determine which physical file fields are in error. Then either
delete the record from the file or change the data in the fields that are in
error. Then try your request again.
Possible choices for replying to message . . . . . . . . . . . . . . . :
C -- The request is canceled.
I -- The request is ignored.
检查你的job log看看是否有CPF5035或CPF5036, 检查error code是几, 再查具体原因.
See previously listed message CPF5035 or
CPD5036 to determine which physical file fields are in error.
Message ID . . . . . . . . . : CPF5035
Message file . . . . . . . . : QCPFMSG
Library . . . . . . . . . : QSYS
Message . . . . : Data mapping error on member &1.
Cause . . . . . : A data mapping error occurred on field &9 in record number
&5, record format &7, member number &8, in member &1 file &2 in library &3,
because of error code &6. The error code meanings follow:
1 -- There is data in a decimal field that is not valid.
2 -- A significant digit was truncated.
3 -- A floating point value exceeded the maximum representable value.
4 -- A floating point value was less than the minimum representable value.
5 -- A binary floating point value could not be used for the attempted
operation because it is not a number, or is not valid.
6 -- A floating point value could not be mapped to packed decimal, zoned
decimal, or binary.
8 -- A binary floating point value that is not a number is not allowed as
a key value.
9 -- Division by zero.
10 -- A partial binary key field could not be mapped. The length of the
key did not include the entire binary field.
11 -- A partial key field could not be mapped. The length of the key did
not include the entire binary, floating point, date, or timestamp field.
12 -- There is data in a DBCS field that is not valid.
13 -- Group by results could not be determined because no records were
selected.
14 -- The length of a variable length field is not valid or the data in a
substring variable is not valid.
15 -- A date value is greater than the maximum allowed value.
16 -- A date value is less than the minimum allowed value.
17 -- The format of the data in a date, time, or timestamp field is not
valid.
18 -- There is data in a date, time, or timestamp field that is not valid.
19 -- An unexpected null field was found.
20 -- A field that is not null capable could not be set to null.
21 -- The data has been converted from one CCSID to another. However,
substitution characters were used for characters which could not be
converted.
22 -- A shift-out character was found while converting to a single or
mixed byte CCSID or a substitution character was found. The data could not
be converted.
23 -- The data could not be converted from one CCSID to another.
24 -- The data could not be converted from an ASCII CCSID to an EBCDIC
CCSID, or could not be converted from or to a UCS-2 (Universal Coded
Character Set) CCSID. The addition of shift-out and shift-in characters or
the expansion of single-byte data to a double-byte value caused the
converted length to be larger than the maximum length the result could hold.
25 -- Hash value cannot be computed for the requested query.
If the error occurred on an attempt to read an existing record, file &2 in
library &3 identifies the name of the physical file containing the field
contributing to the mapping error. Otherwise, the error occurred on an
attempt to put or update a record in a file and the file name identifies the
open file that contains the field contributing to the mapping error. If the
field name is *N, the field name is not known or is a default value.
Message ID . . . . . . . . . : CPD5036
Message file . . . . . . . . : QCPFMSG
Library . . . . . . . . . : QSYS
Message . . . . : Data mapping error on member &1.
Cause . . . . . : A data mapping error occurred on field &10 in record
number &5, record format &7, member number &8, in member &1 file &2 in
library &3, because of error code &6. The error codes and their meanings
follow:
26 -- For the CAST operation, a source character was found that is not
valid.
27 -- For the CAST operation, the character destination field is too short
to hold all the significant digits of the source.
28 -- User-defined function &9 returned a mapping error.
29 -- Java user-defined function with external name &9 returned a mapping
error.
30 -- For an identity column, the range of values has been exhausted.
31 -- For a rowid column, the value is not valid.
32 -- The total length of the fields of the file is greater than
3,758,096,383.
33 -- The resulting length of a concatenation operation involving a
varying-length field exceeded the maximum allowed length for the result
type.
34 -- The data could not be converted from or to a UTF-8 or UTF-16 CCSID.
The expansion of single-byte data to a double-byte value caused the
converted length to be larger than the maximum length the result could hold.
35 -- The data was not valid in a decimal floating point field.
36 -- The SQL subscript &11 is not valid.
37 -- The XMLCOMMENT parameter starting with &12 is not valid.
38 -- The XMLPI parameter starting with &12 is not valid.
39 -- The XML string starting with &12 contains the invalid character &13
(0xhex(&13)).
If the error occurred on an attempt to read an existing record, file &2 in
library &3 identifies the name of the physical file containing the field
contributing to the mapping error. Otherwise, the error occurred on an
attempt to put or update a record in a file and the file name identifies the
open file that contains the field contributing to the mapping error. If the
field name is *N, the field name is not known or is a default value. |
|