× 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.



Great - check out the examples he has (I have adapted
LIBFTP/QRPGLESRC(EX4MGET) for our needs). It works fine for us. 

The reason I needed to use it is that we are dealing with a bank whose file
names are 36 bytes long, but the decryption software they supply to decrypt
the files only processes QDLS.LIB style file names. So I wrote a program,
based on the example, to rename the files as they are downloaded to a
10-character name that I can process with the decryption program. All of
this is much simpler with FTPAPI than using a clunky hodgepodge of CLPs with
DSPFD to an outfile, etc. (of course, it would be nice if the decryption
program worked with IFS file naming conventions, but, alas, it does not).

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: Wednesday, March 1, 2006 5:06 PM
To: Midrange Systems Technical Discussion
Subject: Re: FTP Case-sensitivity

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 to upper 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



--
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 ...


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.