It's a nuisance message.  When I closed open-registration, I moved most of
those nodes that got into the STANDARD domain before I noticed their
presence into more suitable domains.  So expiration leaves me hundreds of
these messages every morning in the AC.





At 10:56 AM 2/15/99 -0800, you wrote:
>I don't want anything pointing to the old management class. After I created
>the new domain, mgmt class, etc., I moved all the nodes to it. I then
>inserted an include line into the client options to get it rebind to the new
>setup. Was this the wrong thing to do?  I can't see where there is an
>association back to the old management class.
>
>-----Original Message-----
>From: Rick Bailey <fbailey AT US.IBM DOT COM>
>To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
>Date: Monday, February 15, 1999 10:53 AM
>Subject: Re: What does this message mean?
>
>
>>Management class - "class name" in domain "domain Name" used by node "node
>>name" in file space "filespace name" is no longer active, or no longer has
>>a backup copy group:  Default management class attributes will be used for
>>expriation.
>>
>>Explanation:  During policy roll-off processing, the server has found a
>>client file copy whose managemnet class or backup copy group no longer
>>exists.
>>
>>System action:  The server obtains the default management class for the
>>specified domain and uses its backup copy group version and retension
>>parameters to determin if file copies need to be expired.
>>
>>What you need to do:  "With Authority over the specified domain"  Use the
>>Define Copygroup
>>Define Mgmtclass, and Activate Policy commands to define and activate a
>>policy set that contains definitions for the missing class or copy group.
>>
>
Fred Johanson
System Administrator, ADSM
S.E.A.
University of Chicago
773-702-8464