As documented recently here (yesterday, I believe), large directories are a
problem.  The only real solution (one your users will not want to hear, most
likely) is to make your hierarchy higher, and reduce the number of files in a
given level to something more manageable.

As you found out, adding the directory to the exclude list will not work -
this has also been well discussed here, although it has been a while.  We
have asked for a "don't even look here" type of exclude, but no comments have
been made from IBM (that I recall).

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: ADSM CLIENT HANGS on NT with Large Directories
Author:  INTERNET.OWNERAD at SNADGATE
Date:    10/2/97 6:29 AM


I am running V2 ADSM Server on MVS (Mainframe) and have ADSM 2.1.6 NT
Clients
running on Compaq Servers.

The problem that I have is that when there are a large number of files in
one directory
(e.g. >100,000) the ADSM client fails with a TCP/IP session rejected error
message.

The problem still occurs when the directory is excluded in the dsm.opt
file.

Anyone got any ideas?????

regards,

Alasdair Urquhart.