CLOPTSETS's are good for things like inc/exc operations. For instance, we
have a whole ton of options now that exclude *.ldf, *.mdf, *.mp3, etc. No
matter what the user does to their .opt file, we'll still not get what we
don't want to get.

As for management, it's easy: define them once and pretty much forget about
'em. Once we added a bunch of exclusions, we reduced our errors (from
skipped files that should have been skipped) by around 66%.

Mike Bantz
Research Systems, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Gill, Geoffrey L.
Sent: Wednesday, April 28, 2004 11:11 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: DSM.opt vs CLOPT

Hi All,



I was wondering if anyone has any ideas about how much to centrally manage
through a CLOPT set vs. the dsm.opt. I will compare one of our typical
dsm.opt files with what is definable through the CLOPT, but maybe if someone
has experience with this they could tell if there are some things you would
"NOT" want to centrally locate on the TSM server and why. I do already have
a couple of CLOPT sets on the server with excludes for specific directories,
txnbytelimit, compression and compressalways.



As always, thanks for the help.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   gillg AT saic DOT com
Phone:  (858) 826-4062
Pager:   (877) 854-0975