× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Jeff,

Three key points with FTP API..
1) You always know when a error has occured.
2) You know after every step rather or not an error occured.
3) You can have any kind of logic around the transfer process you need.
(ex. reading a list of files to process without knowing the names in
advance)

whereas with trying to script the built in client,
1) It's difficult if not impossible to always know an error has occured
2) You can't try to check for errors till the script has completed.
3) No logic around the process..

Here's a nice article
http://iprodeveloper.com/rpg-programming/ftpapi-scotts-utility-assist-batch-ftp-programming


Charles




On Tue, Jul 15, 2014 at 12:35 PM, Jeff Young <jyoung0950@xxxxxxxxx> wrote:

Thanks Charles,
I will talk with them and try to get approval to use the FTPAPI program.

Jeff Young
Sr. Programmer Analyst


On Tue, Jul 15, 2014 at 12:16 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

No there isn't...

And that's why Scott's FTP API is such a better choice.

​The customer is not always right...


http://www.huffingtonpost.com/alexander-kjerulf/top-5-reasons-customer-service_b_5145636.html

Especially in IT...​have you explained to the customer that you could
spend
20hrs trying to bullet proof the error detection in the built in client
or
spend 1hr doing it with FTP API?

Charles


On Tue, Jul 15, 2014 at 11:59 AM, Jeff Young <jyoung0950@xxxxxxxxx>
wrote:

Is there any consistent method to test for exceptions?

I know that I could use Scott Klement's FTPAPI, but the customer
insists
that we use the normal system FTP function (and the customer is
*always*
right).


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.