We use domain and mgmtclasses by platform which seems to work for our
environment.   Aix, Linux,Wintel,,Db2,Domino,etc.

For example:

Aix_pd   Policy Domain for AIX clients
Aix_ps Policy Set for Aix clients
Aix_mc  Description= 'MC for AIX clients'






Nancy Backhaus
Enterprise Systems
HealthNow, NY
716-887-7979



Michael Bartl <michael.bartl AT SPACE DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/05/2008 02:51 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: Fw: Naming conventions of PDs/MCs






Yes, keep them short, simple and exchangeable.
Sometimes you decide to migrate a node from one policy domain into a
different one. Then it's very convenient to have the same names for
the Mgmt-Classes as before.

In general we don't name the standard/default MC, it just stays
"standard" in any PD.
For MCs we often use names that reflect the settings for the main 4
parameters, like 3-2-30-60 or 2-1-7-7. We use "0" for the nolimit
value, like in 0-0-14-14.
In addition to this we have some short-forms like RET14 (=0-0-14-14),
sometimes we add a special MC name to make a customer happy.
And of course, sometimes it gets cryptic, when you need to put
additional information into the name, like in 4-3-50-80-SHDY (shared
dynamic).

If you have more than one TSM server, try to keep all PDs and MCs in
sync - makes moving nodes between servers much saver. Just imagine
what happens if the new server doesn't have the new longtime-
protecting special MC and you find out just after the restore request
arrives.

Best regards,
Michael

Am 04.03.2008 um 23:46 schrieb Nicholas Cassimatis:

> One rule - Keep them short and simple.  They need to have enough
> info so
> you know what they are, not necessarily every feature of them but I
> try
> keep them short enough (8 characters or below) so they don't line-
> wrap when
> using the Administrative Command Line.
>
> Nick Cassimatis



CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole 
use of the intended recipient(s) and may contain proprietary, confidential, 
trade secret or privileged information.  Any unauthorized review, use, 
disclosure or distribution is prohibited and may be a violation of law.  If you 
are not the intended recipient or a person responsible for delivering this 
message to an intended recipient, please contact the sender by reply email and 
destroy all copies of the original
message.