Hi:
The following is not a joke or a cry for help but an information that I would
like to pass on to the list. I have posted in the past requests for help to the
list concerning this issue which I finally could resolve.

I am running the ADSM Netware client version 2.0.5 for a NW 4.1 system and a
ADSM server ver 1 on VM. I could not explain why a series of

     ANS4228E Sending of object  ..... failed
     ANS4090E Access to the spec. file or directory .. denied

would show up. I received from several ADSMers suggestions to rewrite my
EXCLUDE statements in question. This did not solve the problem either.
But it became clear to me that the EXCLUDE statements were not processed
at all.

After 2 month of this happening I ( or rather we) have encircled/solved
the problem.

Whenever I make additions to the DSM.OPT file I make a revision entry at the
top of the DSM.OPT file. Each line is properly preceded with a '*' to
flag it as comment. Being the neat German I thought it would be visually
supportive of separating my revision notes with a line  of stars above and
below the rev comment. I made the line of stars as long as the commented
text line, around 80 chars or so.

Here is the bug now: a comment line starting with a '*' and having more than
                     80 (in my case) stars on the same line will cause that
                     none of the EXCLUDE statements in that DSM.OPT file will
                     be read.
I have not tested if it is more than 72 stars and I do not know if this
claim extends to INCLUDE statements as well though I was told that it will.

I mentioned before the 'we' which includes this very knowledgable gentleman
in the IBM-ADSM camp who figured this detail out and has issued the APAR
IC17154 concerning this particular occurrence.
He also tested that the above bug relates to a comment line with all
stars ONLY.

So, I made a line of 72 stars instead of 80 or so and voila I am back in
business.