Hello, Srinivas. Normally the root user administers the dsm.sys file, setting things like connection and logging options in various stanzas available to everyone.
Each user can have its own dsm.opt, or even multiple dsm.opt's, defining more or less how its client behaves and which stanza of options it wishes to use. For example, on a DB2 server, there may be multiple DBA users with different responsibilities and multiple instance users of DB2. Each instance could back up to a different TSM server and each of the DBAs might have multiple dsm.opt files for doing different things. ________________________________ Alex Paschal Storage Solutions Engineer MSI Systems Integrators ________________________________ Your Business. Better. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of srinivas ryiad Sent: Wednesday, November 26, 2008 5:19 AM To: [email protected] Subject: [ADSM-L] HI! WHY dsm.sys & dsm.opt why not a single file on client side HI! WHY dsm.sys & dsm.opt why not a single file on client side any specifc reason? thanks This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
