HP3000-L Archives

May 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Wirt Atmar <[log in to unmask]>
Reply To:
Date:
Thu, 13 May 1999 10:07:10 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Rick writes:

> I received the following error when we ftp'd certain files to a HP9000
>  and cannot find any clues as to what this means. I did a search on the
>  ESC and found two documents. One was blank, and the other was no help.
>  Has anyone seen this error before? Here is a sample of the JCL with the
>  error. It only happens on a few of the files that are FTP'd and the
>  record sizes vary.


>   200 PORT command successful.
>   150 Opening ASCII mode data connection for ACT999.
>   226-WARNING! 1918 bare linefeeds received in ASCII mode
>      File may not have transferred correctly.
>   226 Transfer complete.
>   40140100 bytes sent in 74.17 seconds (528.48 Kbytes/sec)

The problem is that the file is not formatted in a standard ASCII format with
CRLF at the end of each line. This kind of thing especially occurs when the
file transferred is not an ASCII file but rather is binary (e.g., an image or
a sound file). If that's the case, the LF's that FTP is seeing aren't meant
to be control characters but are instead just random bit patterns in the data
stream.

Add the statement "binary" before your "put" or "get" and the problem will go
away.

Wirt Atmar

ATOM RSS1 RSS2