X-no-Archive:yes
Without more information, we can only multiplying guesses. Type issues are
one likely cause.

Another possibility is that the file is coming from an IBM box, and
sixty-seven bytes are being lost due to the default on the IBM ftp servers
(on MVS, OS/390, and OS/400) to suppress trailing blanks, where this is an
unusual condition in this file (only a few records end in one or more
trailing blanks). Although I'm not sure why this wouldn't be an issue,
sending to the 3000, unless record size was specified in the send, so
trailing blanks were not lost. Or, if the file has any kind of header or
trailer record, that could be a point of failure.

67 records does not work out; 125,874 does not divide evenly by 67, and
would require a record length of 1878 and a fraction bytes per record (for
you oxymoron fans). If the records were eighty bytes, plus one char to
separate the records, that works out to 1554 records of eighty-one bytes
each. There are at least forty values that will divide 125,874 evenly.

Greg Stigers
http://www.cgiusa.com
this ftp stuff was supposed to be easy
There is a house in New Orleans...