Thanx everyone for the replies.
It's all clear to me now.............but I still find it strange;-)
I defined a client option set and updated all my client nodes except the one that
needs the LOG_POLICY-MC managementclass to make use of this option set.
Kind regards,
Jerry
>>> [EMAIL PROTECTED] 10/26/01 04:13PM >>>
Yes, this is perfectly normal. I am guessing that the LOG_POLICY-MC
management class has a RETONLY value equal to or greater than that of your
STANDARD management class. The TSM client binds directories to the
management class with the largest RETONLY setting. If two or more
management classes have the largest RETONLY setting, then it is
undocumented as to which class will be selected.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Jerry Caupain <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10/26/2001 02:12
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Strange behaviour????
Hello everyone,
I have noticed something strange. In my policy domain I have two
management classes. One is called STANDARD and the other is called
LOG_POLICY-MC. I want to use the last one only for my log server so I
included the following line in my include/exclude file:
INclude /logs/.../* log_policy-mc
Managementclass STANDARD is the default managementclass.
Why is it that all my other systems also use the LOG_POLICY-MC
managementclass? It seems that the directories on my other systems are
all bound to this managementclass. This can't be normal............can
it???
Jerry Caupain
