I would imagine if there is no source file to transfer, then it will not replace or update anything on the remote FTP site for that file.

That would be expected behavior in my eyes.

If you don't want to send a file at a time, you should consider doing a delete from the remote site before you transfer any data.

Or get the remote vendor to remove the files after they process them.

Then you would not have any leftover data.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx

------------------------------

message: 2
date: Sun, 29 Nov 2020 18:07:06 +0000
from: "Steinmetz, Paul via MIDRANGE-L" <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: RE: SFTP Script halting

Different but related issue.
If the file being SFTP is empty, and replace option is used, the transmission is stated successful, but the empty file does not replace the existing file on remote server.
Thus, I receive a call from remote vendor stating they did not receive today's file, file is equal to yesterday's file.

Anyone from the group experiencing this issue?

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Sam_L
Sent: Sunday, November 29, 2020 12:26 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: SFTP Script halting

How about putting one file at a time? I suppose there is a slight overhead on the connection, but maybe not noticeable?

Sam


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.