Just my own personal preference, but I find it easier to manage multiple
management class and/or copygroup needs by creating a whole separate domain.
That way I don't have to worry about what's in the options file - I register
the client to the appropriate domain.  Since the person who administers,
maintains and supports ADSM (me) isn't the same person who administers the
ADSM clients, it makes it easier for me to keep track of who's using what
managementclass and what we're doing with their data storage.






ADSM-L AT VM.MARIST DOT EDU on 10/28/99 11:42:30 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: Re: Management Classes

David,

I have experienced the server crashes also when adding a new client option.
I reported it to IBM and it is apar PQ28538.  They are planning to fix it
in the 3.1.2.50 level.  I don't know if it is fixed in the tsm 3.7 server.

I think you are on the right approach to the problem.  Once the server is
fixed,
make many different client option sets, perhaps one for each client.  I don't
think there is a lot of overhead to this and will give you maximun
flexability.


--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
In <72C659D7A121D311A15E0010E37C4A6A047EA9@LDNTES02>, on 10/28/99
In <72C659D7A121D311A15E0010E37C4A6A047EA9@LDNTES02>, on 10/28/99
   at 02:59 PM, "Irvine, David (ANFIS)" <dirvi1 AT ANFIS.CO DOT UK> said:

>Hi All,

>Don't want to steal anyones thunder but does anyone have any good ideas on
>configuring some decent Management Classes ?

>We have a large distributed environment - mostly NT (what else!). This is
>made up of the usual mixture of mail servers, internet servers, exchange
>servers, database servers etc etc.
>At the moment I have 7 management classes defined and try to keep user data
>versions rich whilst other classes have lower retention periods etc.
>However I am not particularly happy with this and its quite hard to manage.

>In order to break down a server into several different management classes
>I have been using INCLUDE statements in the client option file. This works
>fine but is a bit messy....

>I am currently looking at the centralised option sets but the server
>hangs(!)
>every time I try to change this...(call in progress with IBM)
>We are using NT 3.1 clients and a 3.1.2.2 MVS Server.

>Would be grateful to know or receive ideas on how other ADSM shops handle
>management classes..............

>Thanks!

>David Irvine