Just opened a case with IBM. Retrieving a simple text file from an FTP site... <filename>.tab
The file already has hex '0d' '0a' at the end of each row/record/line (whatever)... FTP is actually inserting another '0d' before the existing '0d0a'.
Of course, if I use the BIN command this goes away... however, why on earth would FTP do that?? Anyone seen this before?
The file already has hex '0d' '0a' at the end of each row/record/line (whatever)... FTP is actually inserting another '0d' before the existing '0d0a'.
Of course, if I use the BIN command this goes away... however, why on earth would FTP do that?? Anyone seen this before?
Comment