5 pts.
 CPYTOIMPF data corruption
CPYTOIMPF on V5R4 with latest PTF's adds invalid data to the created CSV file for some blank fields in the PF. Is this a Bug?

Software/Hardware used:
AS/400 V5R4
ASKED: September 21, 2009  3:04 PM
UPDATED: September 21, 2009  5:45 PM

Answer Wiki:
Enhancements to the CPYTOIMPF command and the CPYFRMIMPF command for V5R4: When the from-file character fields contain a string of blank characters, the CPYTOIMPF command and the CPYFRMIMPF command keep one single blank in the corresponding to-file field, unless you have specified *NONE for the RMVBLANK parameter. A string escape character (STRESCCHR) parameter has been added to indicate that a string delimiter should be treated as a normal character. This new parameter allows import utilities to parse the delimiter character correctly, when the string delimiter itself is a character in a string field. A special value *DBLQUOTE is provided as the default value for the string delimiter (STRDLM ) parameter, to indicate that the double quotation mark character is used as string delimiter. A from CCSID (FROMCCSID) parameter has been added for the CPYTOIMPF command. This parameter can be used to specify the CCSID to be used when the from-file field is 65535. A to CCSID (TOCCSID) parameter has been added for the CPYFRMIMPF command. This parameter can be used to specify the CCSID to be used when the CCSID of the to-file field is 65535. ________________________- Was the exact same procedure working before you put on the PTFs? Is it because of NULL values?
Last Wiki Answer Submitted:  September 21, 2009  4:37 pm  by  CharlieBrowne   32,785 pts.
All Answer Wiki Contributors:  CharlieBrowne   32,785 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _