try issuing a ftp command ASCII before your GET command, this should
handle the record seperator

-----Original Message-----
From: Gates, Scott [mailto:[log in to unmask]]
Sent: Thursday, June 29, 2000 11:14 AM
To: [log in to unmask]
Subject: [HP3000-L] FTP CRLF vs LF question


                I am trying to automate a process for FTP'ing a file from a
server to HP.
                The file is a 380B wide file and as much as 50Krecs long.

                I do a GET a10tpl766 A1TPL766;REC=-380,,F,ASCII

                Problem: *Sometimes* the file only has a LF instead of the
CRLF at end of line.
                When this happens the HP(or FTP program on the HP) dutifully
puts a CRLF at the end of 380 and puts the existing LF on the next line,
making the file go off by 1 character each line.

                It evidently happens about a third of the time and is
detected only by looking at the file every time.  When it does, we transfer
the file manually using Reflections and Record Separator to LF instead of
the default CRLF

                I don't want to have to eyeball the file every time to see
if it's happened.

                Is there a way(before, during, or after the FTP) to detect
and patch the LF to a CRLF if the file is screwed up?

                *************************************************
                * Scott Gates-ext 7994  | There is no problem   *
                * UPMC Health Plan      | in the world that     *
                * [log in to unmask] <mailto:[log in to unmask]>   |
cannot be made worse  *
                * 412-454-7994          | by overreacting to it.*
                *************************************************