A couple of questions I haven't seen yet 1. Was the original FTP done in binary or text mode? 2. Do the corrupted records make any sense as EBCDIC characters when you browse/view the "corrupted" file?
This smells like an issue we had once, someone FTPed a PC file with some option set that caused CR/LF (X'0D0A') _not_ to be stripped from the records (might have been the simple Binary/not text problem, but I don't remember). Therefore two extra characters were needed for each record and the two extra bytes caused the wrapping you are seeing. First thing would be 'send the file again correctly'. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
