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



When you say "accessing the IFS through shared folders", what do you
mean specifically?

Are you talking about the old PC-support-style shared folders function
that only accesses the QDLS filesystem?  If so, yes, it's always been
slow.  QDLS itself is slow.

Are you instead accessing the IFS through a newer driver?

Are you using the AS/400 NetServer, so you can use normal MS Windows
file sharing?

You are accessing this via a VPN?  Is that quick for non-IFS traffic?
What about FTP from the same files in the IFS?


On Mon, 17 Dec 2001, Reeve Fritchman wrote:
>
> I’m experiencing extremely long response times when accessing the IFS
> through shared folders.  I’m experimenting with a couple of HTML editors
> (CoffeeCup, HomeSite) and I’m looking at >60 seconds to download a 2K HTML
> file.  My IFS isn’t huge nor is it busy.
>
> >From a V5R1 820, I have a firewall, VPN, Internet/WAN connection, cable
> modem, and 1.1 gHz desktop.  There is very little running on the 820; we
> have enough memory (> 200 mb.) in *BASE and other stuff split out into a
> couple of other subsystems, etc. with 128 mb. or 256 mb.
>
> Serving HTML works fine; response is good.  I use CODE/400 (mostly) and SEU
> extensively; CODE/400 up/downloads aren’t fast but they’re better than IFS
> work.
>
> Is there some terrible TCP/IP default I’ve forgotten to change in
> OS/400-land, or am I expecting too much?
>
> Thanks,
> rf



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.