Go get the redbook whose title is something like "getting started with
ADSM". It will save you a lot of false starts.
I use something like this:
/* Base Option Set */
define cloptset base description='Base Set'
define clientopt base dirmc dir
define clientopt base schedmode prompted
define clientopt base TxnByteLimit 25600
/* Windows Option Set */
copy cloptset base win
update cloptset win description='Windows Clients'
/* Exclude files that cannot be recovered without corrupting the */
/* Operating System or ADSM itself. */
define clientopt win inclexcl 'exclude "?:\microsoft uam volume\...\*"'
seq=3
define clientopt win inclexcl "exclude ?:\...\*.swp" seq=6
define clientopt win inclexcl 'exclude "?:\...\EA DATA. SF"' seq=9
define clientopt win inclexcl "exclude ?:\...\pagefile.sys" seq=12
... etc ...
On Tue, 10 Oct 2000, Walker, Lesley R wrote:
> Michel Engels wrote:
> > You have to combine both syntaxes. an example would look like:
> >
> > DEF CLIENTO FRED INCLEXCL EXCLUDE "/foo/*"
> >
> Well I thought this looked hopeful, but no such luck. It still complains
> about EXCLUDE as an invalid keyword. The full output is as follows:
>
> tsm: TESTSERVER>def cliento inclexcl exclude /kernel/genunix
> ANR2056E DEFINE CLIENTOPT: Invalid option name - EXCLUDE. Retry using
> the full optionname.
> ANS8001I Return code 3.
>
> > "Walker, Lesley R" <[EMAIL PROTECTED]> on 10/09/2000 06:16:26 AM
> >
> > While we're on this topic, can someone give an example of the syntax
> > (3.7.3
> > on Solaris) to specify an include/exclude statement in the client option
> > set? I've read the Admin Ref, and tried a couple of ways but it comes
> > back
> > with errors:
> >
> > DEF CLIENTO FRED EXCLUDE /foo/*
> > results in: Invalid option name - EXCLUDE"
> >
> > DEF CLIENTO FRED INCLEXCL "/path/filename"
> > DEF CLIENTO FRED INCLEXCL "ex /foo/*"
> > both result in: DEFINE CLIENTOPT: Invalid option value
> > (and yes, the file exists in the first one)
> >
> > What am I doing wrong?
> > Why doesn't the manual have an example, dammit?
>
