Re: ftp to the ifs from a database file

Joel,

First of all, is this a SAVF?  If so use *YES on compression.  Try doing a
DSPOBJD on the save file with a compressed and an uncompressed save - big
difference.

Second, I assume that your 400 is on the same lan as your PC, so we are
comparing apples to apples here, right?

Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.



                    Joel Fritz
                    <JFritz@sharperimag       To:     "MIDRANGE-L@midrange. com 
(E-mail)" <MIDRANGE-L@midrange.com>
                    e.com>                    cc:
                    Sent by:                  Fax to:
                    midrange-l-admin@mi       Subject:     ftp to the ifs from 
a database file
                    drange.com


                    09/20/2001 10:31 AM
                    Please respond to
                    midrange-l






This week I was filling in for a co-worker who's on vacation.  I had to
send
a reasonably large file (1.3 gig) by FTP.  Our procedure has been to move
the file down to a PC hard drive, zip it, and send the zip file from the pc
because direct FTP from the 400 was very slow.

Because I didn't have enough room on my hard drive, I tried FTPing the file
to an IFS directory, in hopes of sending it from there.  If I hadn't killed
the job, it would have taken nearly three hours to FTP the file to to the
IFS.  I deleted a bunch of files from my PC hard drive and was able to FTP
the file to my PC in 30 minutes.

I hope this isn't normal.  If not, what sorts of things should we look for
in the TCP/IP configuration on the 400?
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.