If AIX used \n as a line terminator (in keeping with standard UNIX practice,) binary vs ascii mode would not be an issue, but according to the ever-accurate wikipedia, it uses EBCDIC 0x15: http://en.wikipedia.org/wiki/Newline
Learn something new every day. The ftp client should be changing the data to network byte order before transmission. The ftp server should be converting from network byte order to host byte order after transmission. Again, this should be a non-issue for any decently cobbled-together network program. -- Mike Doyle Unix Developer / Administrator AMO Recoveries ________________________________ From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED] Sent: Thu 1/12/2006 10:57 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] System Migration issues [EMAIL PROTECTED] wrote: > I am migrating an old AIX server running U2 to RH Linux. Because of the > server's limitations, I need to transfer files between the two devices via > FTP and then converting the files for Linux use. After doing so, my > distributed files are getting corrupted. It looks like the IBM provided > fixtool utility repairs the files, but it's taking way too long for my > larger distributed files. Making a HUGE assumption that it's the file > transfer responsible for the file corruption, is there a preferred method > for copying data files? > Two possible problems. You ARE transferring them in ftp in binary mode? And you have run the clean-up tool that corrects the byte order? (I think that's what Karl is talking about) You might also find it easier to do a UVBACKUP and then restore that, because that (I think) gets round all the endian issues and that sort of stuff. Cheers, Wol ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ [demime 1.01d removed an attachment of type application/ms-tnef which had a name of winmail.dat] ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
