I too have seen slow response using the search facility (magnifying glass
icon) under the V3 NT client.  When I reported it, I was told it must be
something on my machine.  I am running on an Intel platform (a Thinkpad), so
it isn't something particular to your Alpha, although mine wasn't that slow,
but then again, it probably doesn't have anywhere near as many files as your
machine does.   By the way, don't try to search a file space that isn't
mounted - it won't do it - it searches the mounted file with the same letter!

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: Problems with V3 Client code running on V2 server.
Author:  INTERNET.OWNERAD at SNADGATE
Date:    2/5/98 6:28 PM


     Hi all,,,We are starting to implement some V3 clients into our
     environment.  Mainly for the support of NT on a DEC ALpha platform.
      Our server is on an os/390 machine running 2.1 level 13.  We are
     seeing numerous problems with the V3 client, several Dr. Watson
     errors, very poor performance when bring up a directory tree on a
     restore.  Is anyone else seeing these kind of problems?  I have an
     issue open with IBM but I thought I would ask around.

     As an example we were doing a search for a file in a filespace on a
     NT (Dec Alpha client) and it took 4.5 hours and it only had
     processed 150 files????

     We hit the filter button and get Dr. Watson abends?

     When trying to display a directory tree it appears that ADSM is not
     doing anything when in fact it is?  It would be nice if the cursor
     showed it was busy or something.  Because if you hit another button
     you get a Dr. Watson again.

     I know this is new code but I am just wandering if anyone else is
     seeing these types of things?

     By the way we are running the IP21169 (intel) and IP21170
     (dec/alpha) client code.

     Thanks
     Don Ludwig