Re: CRLF in middle of CSV text strings

Actually the CPYFRMIMPF was *corrected* to prevent accidentally seeing embedded CRLF in character strings as indication of new text lines. This was done to both specifically _enable_ CRLF to be be embedded in the text and to prevent the side-effect that the line of text would be treated as two incomplete rows -- where the remaining columns for the corresponding row gets no data and the unexpected row typically fails to insert as a row [or worse, inserts as junk] due to data mismatches. Since it could and did export text in that manner, exporting embedded control characters [and since the primary rule for an import/export is the ability to parse its own output], required that correction.

If the CRLF should not be embedded in the text field, should that not be enforced by the database from which the data was exported? By what rule would embedded control characters be removed, and to be replaced by what? For example, what to do with the following string:
"Text is not HTML, so instead of <br> there is<CRLF>to break"
Perhaps one of:
"Text is not HTML, so instead of <br> there isto break"
"Text is not HTML, so instead of <br> there is to break"

If there is a difficulty w/ the 0x0D25 [or 0x0D0A] in the DB2 for i5/OS PF, then create a VIEW which uses a function like TRANSLATE() or REPLACE() on the field which can have that data embedded; then the VIEW defines how to /strip/ the CRLF rather than having the import guess [or adding more/complicated parameters on the import command]. Have the application refer to the VIEW instead of the PF.

Regards, Chuck