You can do the same kind of thing with cloptsets, you know - kind of a
virtual dsm.opt file that lives in the server database rather than on the
client's disk - and cloptsets have the advantage that you can change them,
and the changes take effect WITHOUT you having to restart the scheduler
service.

And...then you can leave the client's dsm.opt file under user control, for
example, to exclude certain files that they don't want backed up.

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Joe Cascanette
> Sent: Wednesday, August 08, 2001 11:22 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: shared dsm.opt file
>
>
> Has there been any changes in TSM4.2 client to use a shared
> DSM.opt file?. I
> would like to place a grand dsm.opt file on the network and have all the
> clients to use this when their backup schedules start.
>
> Thanks
>
> Joe Cascanette
>