|
Hi Francis, For now I'm doing something similar with a homegrown FTPFILE command, but I'd like to use Scott's FTPAPI, especially because I can check for errors after each FTP command. I've downloaded it and put it on an iSeries, and briefly looked at it but haven't had time to use it. Soon I hope. Peter Dow Dow Software Services, Inc. 909 793-9050 voice 909 793-4480 fax Lapeyre, Francis wrote:
I just switched to using Scott Klement's FTPAPI. What you an do there is get a directory listing, loop through it and choose the files to GET. In your case, you could, in RPG, %XLATE the name you get back from the M$ server toupper case to compare to an upper-case name.Francis Lapeyre IS Dept. Programmer/Analyst Stewart Enterprises, Inc.E-mail: flapeyre@xxxxxxxx-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Peter Dow (ML) Sent: Tuesday, February 28, 2006 11:46 AM To: Midrange Systems Technical Discussion Subject: FTP Case-sensitivity Hi Everyone, Just learned something yesterday about Microsoft FTP Server 5.0. I had an iSeries FTP script that was using the GET command to get a file from MS FTP Server 5.0 and had to change it to use MGET. The file name for the GET was ShippedOrders.csv; for the MGET I changed it to ShippedOrders*. The GET worked fine whether the remote file was named shippedorders.csv or Shippedorders.csv or ShippedOrders.csv. The MGET failed unless the remote file was named ShippedOrders.csv or ShippedOrders.xyz.csv etc. The DIR command worked like the MGET. Just thought I'd pass that tidbit on. I knew Unix/Linux was case-sensitive; I didn't know MS was 1/3 case-insensitive, 2/3 case-sensitive, at least with their FTP server. Peter Dow Dow Software Services, Inc. 909 793-9050 voice 909 793-4480 fax
As an Amazon Associate we earn from qualifying purchases.
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.