Re: FTPAPI failing to rename a file

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Hi Jonathan,

All FTPAPI does is send the from/to filenames to the server.  So if you 
say FTP_rename(x: 'x': 'y'), FTPAPI will send RNFR x, RNTO y.  All it 
does is send them to the server, it's the server that does the actual 
work of renaming the file.

If the send() API is returning -1, it typically means that the network 
connection was dropped for some reason.

Maybe there's a bug in the server somewhere that when it tries to rename 
the file under some circumstances, it crashes (and this ends the network 
connection)?

But it's hard to see how this could be a problem in FTPAPI... after all, 
it does so little, just sends the filenames...


On 2/28/2014 3:57 AM, Jonathan Mason wrote:
> The process we have in place will retrieve a file and then use the
> FTP_Rename procedure to append a '.done' to the name before it calls
> a validation routine.  If any errors are detected in the file then
> the file is renamed a second time and the '.done' replaced with
> '.error'.  This process has worked since it was introduced, however,
> while testing a new interface a colleague is having the problem where
> the first rename is successful, however the second fails.
>
> I have debugged the FTP_Rename procedure and at the point the
> SendLine procedure is called for the RNFR command a -1 is returned.
> The joblog, however, doesn't record any information other than
> showing the RNFR command that was sent and the usual "350 Pending
> further information" is not displayed.  Stepping through the SendLine
> and subsequent tsend procedures shows a return code of -1 being
> returned by the send() procedure.