I was running the code for 2.5 on 2.5.1 for a few months and began having
major problems 2 weeks ago as I reported earlier here on the list.  I am
pleased to report that I found the problem.  Here are the details...

Server:  AIX 4.1.2, ADSM 2.1.0.10 and 2.1.0.12
Client:  Solaris 2.5.1, ADSM 2.1.0.5 and 2.1.0.6G (latest)

The problem was based on not being able to exclude/include items specified
in the inclexcl file.  It was simply ignored or it complained about syntax
errors in the inclexcl file (that were not actually errors).

I traced the problem to the dsm.sys config file.  I was looking it over
(like a million times before) and it hit me that I did add a new line to
the file about the time we started having problems.  I added the
POSTschedulecmd and had it perform something like getting a tail on a file
and send the output via email to me.  I commented out this line.
Suddenly, dsmc was responding properly and parsing the inclexcl file as
well.

Here is what I found out about this particular option.  It seems if the
command string inside the ""'s is 0-81 characters, everything works OK.
If the command string is 82-87 characters, dsmc complains (upon execution)
that there are strange syntax errors in the inclexcl file (which are
perfectly, syntactially correct) and dies.  If the string contains 88 or
more characters, I get no errors at all, but the inclexcl file is
completely ignored (it verifies it is there, but that's it).

I have reported this bug to support under PMR 27607 and they are
investigating the problem.  The problem does not seem to appear under
Solaris 2.4 and I have not tried under Solaris 2.5.  Hope this information
proves useful to others running this client software on Solaris 2.5.1.

_______________________________________________________________
Joe Morris  -  morris AT unc DOT edu  -  http://sunsite.unc.edu/morris
Academic Technology and Networks (formerly OIT), Development
University of North Carolina at Chapel Hill