We see a lot of people writing in to ADSM-L concerning client session
problems where the client messages or dsmerror log entries don't give
much sense of what the problem is.  You have to remember that ADSM is
a CLIENT-SERVER arrangement, and so looking at just your client messages
tells you only half the story.  Look also at your server Activity Log
for the time period in question.  Almost always, it will tell you more
about what the real problem is.

Additional advice:  A lot of the client-server problems result from not
evolving your client-server parameters as your use of ADSM increases.
Be particularly aware that the ADSM default values that you start out
with are usually insufficient as your utilization increases.  The most
egregious parameter of this kind is the COMMTimeout value, which MUST
be given a value which allows time for your clients to traverse the
largest file system out there, during a backup operation.  In general,
don't blindly take default values, and adjust your values over time.
Always specify values (don't take implied values), so you won't get a
surprise when a PTF or a new release changes the ground rules.  And
always review the new parameters which are introduced with PTFs and
new releases to facilitate your processing.
       Richard Sims, BU