Ah, got it. After looking at the implementation guide as Joel suggested
(duh, why didn't I think of that) and getting the correct syntax (why isn't
it in the Admin Ref), I found out what I was doing wrong.
I had it nearly right to start with when I did
> > DEF CLIENTO FRED INCLEXCL "ex /foo/*"
b
Joel means "Getting Started with Tivoli Storage Manager: Implementation
Guide", SG24-5416-01from www.redbooks.ibm.com.
In your example,
def cliento inclexcl exclude /kernel/genunix
the name of the client option set which is to have this particular client
option associated with is missing. So add
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 cl
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
I think the inclexcl one is right but you need to include a number to
specify which order to process the options...
-Original Message-
From: Walker, Lesley R [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 09, 2000 1:16 AM
To: [EMAIL PROTECTED]
Subject: Re: Option file and optionset
AIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:(bcc: Michel Engels/BE/Devoteam)
Subject: Re: Option file and optionset
Ron Pavan wrote:
> example in my env:
> all server side option sets for "excludes" are set with override = no
> all server side option sets for "inclu
Ron Pavan wrote:
> example in my env:
> all server side option sets for "excludes" are set with override = no
> all server side option sets for "includes" are set with override = yes
>
[etc]
While we're on this topic, can someone give an example of the syntax (3.7.3
on Solaris) to specify an inclu
your includes will always override your exludes.
-Original Message-
From: James Thompson [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 06, 2000 10:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Option file and optionset
I can't help you exactly with your problem, but you can
use the comm
I can't help you exactly with your problem, but you can
use the command 'SHOW INCLEXCL' from your client's backup
command line to see what order the client is going to process
the list. One thing to note with that command is the list is
in reverse order from what it is in the dsm.opt file.
This w
