In all cases, if null exists in the input
field, then null is written to the related output field without generating an
error.
The following errors may occur for each
data type:
-
STRING. Does not
generate any errors.
-
BOOLEAN. When
there is a non-null value in the input that cannot be parsed, an
UNPARSABLE_FIELD error is generated.
-
INTEGER. When
there is a non-null value in the input that cannot be parsed, an
UNPARSABLE_FIELD error is generated.
-
FLOAT. When
there is a non-null value in the input that cannot be parsed, an
UNPARSABLE_FIELD error is generated.
-
LONG. When there
is a non-null value in the input that cannot be parsed, an UNPARSABLE_FIELD
error is generated.
-
DAY. If the data
parsing ends with an error, an INVALID_DATE error is generated. If the
READ_POSSIBLE option is set, the step parses the data again, this time with
added leniency towards nonsensical numeric parts of the date. For example, the
string 32-13-2000 represents a valid date value that is parsed as 1.2.2001. If
even lenient parsing fails, an UNPARSABLE_FIELD error is generated.
-
DATETIME.
Processing is the same as for the DAY data type.
Each step that handles I/O parsing of iWay
DQC data types must implement a specific strategy that manages error handling.