We put everything that is common to a group of clients in a cloptset on the TSM server, just because its easier to manage if you have only 1 copy and don't have to physically visit the clients.
Things that are unique to one particular machine, go with that machine. Just that simple. -----Original Message----- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 28, 2004 5:11 PM To: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 854-0975
