ftp to the ifs from a database file--a postscript

[Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>]

I finally extracted the truth about what I really did with the file transfer
by using sophisticated interrogation techniques on myself.  The extremely
slow results came using the NT command line FTP client, signing on to the
400 and transferring the file to a directory in a drive mapped to the root
of the IFS.  Something like:    put source.file f:\target\target.txt.

That doesn't work very well.  I just tried using the IP address of the 400
from the 400 command line and got a slightly faster transfer  than using the
loopback address.  I don't think the time difference was significant.  Now
if I can try sending something from the IFS to an address outside our
firewall...

-----Original Message-----
From: Joel Fritz
Sent: Thursday, September 20, 2001 11:55 AM
To: 'midrange-l@midrange.com'
Subject: RE: ftp to the ifs from a database file


Thanks.  That's the answer.  Transfer to the IFS in about six minutes using
the loopback address. I'm truly amazed at the difference.

I like to think of the other way as "abusing" my comm resources. <g>

> -----Original Message-----
> From: rob@dekko.com [mailto:rob@dekko.com]
> Sent: Thursday, September 20, 2001 11:23 AM
> To: midrange-l@midrange.com
> Subject: RE: ftp to the ifs from a database file
>
>
>
> Did you ftp to the loopback address of 127.0.0.1 or were you
> beating the
> #$%^ out of your comm resources?
>
> 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'" <midrange-l@midrange.com>
>                     e.com>                    cc:
>                     Sent by:                  Fax to:
>                     midrange-l-admin@mi       Subject:
> RE: ftp to the ifs from a database file
>                     drange.com
>
>
>                     09/20/2001 12:50 PM
>                     Please respond to
>                     midrange-l
>
>
>
>
>
>
> The problem I noticed was that it took nearly six times as
> long to FTP a
> database file from the 400 to a text file in the IFS on the
> same machine
> than it did to FTP the same database file to a text file on
> my PC.  The
> zipping comes after the conversion to a text file.
>
> > -----Original Message-----
> > From: Peter Dow [mailto:pcdow@yahoo.com]
> > Sent: Thursday, September 20, 2001 10:35 AM
> > To: midrange-l@midrange.com
> > Subject: Re: ftp to the ifs from a database file
> >
> >
> > Hi Joel,
> >
> > Is it faster from the PC because you've zipped it up first?
> > How much does
> > zipping compress the file? 50% or more? So it takes twice as
> > long from the
> > 400 as from the PC? If that's the case, try using the jar
> > program on the 400
> > to compress it into the IFS, for example:
> >
> >     qsh
> >     jar cvf /home/pdow/test.jar
> > /qsys.lib/pdows.lib/source.file/addvlle.mbr
> >     adding: qsys.lib/pdows.lib/source.file/addvlle.mbr
> > (in=1900) (out=336)
> > (deflated 82%)
> >
> > Then FTP it from the IFS.
> >
> > hth,
> > Peter Dow
> > Dow Software Services, Inc.
> > 909 425-0194 voice
> > 909 425-0196 fax
> >
> _______________________________________________
> 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.
>
>
>
>
>
> _______________________________________________
> 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.
>