>My understanding from documentation is that specifying force=yes on server
>side inclexcl options will process those includes/excludes *before* the
>ones in the client side dsm.opt file. And force=no will process them
>after. In effect, force=yes puts the server side rules at the "bottom" of
>the include/exclude list and force=no puts them at the "top".
Jennifer - The redbook Getting Started with Tivoli Storage Manager:
Implementation Guide, SG24-5416-01 does a good job of
describing Client Option Sets, in section 7.3. The server-supplied
include-exclude definitions ALWAYS precede the client options file
specifications, in the processing order. As the manual says:
"include-exclude options in a client option set will always be seen and
processed during backup first, before any options set in the client
options file."
And:
"Include-exclude options in the client option set are additive options and
will not override the include-exclude options in the client options file."
As the book says: "The sequence is not obvious." There is a lot of customer
confusion about this because the standard product reference, the Admin Guide,
treats the topic superficially and the Client manual ignores it.
Richard Sims, BU
