I'm guessing that you defined the EXCLUDE something like this:
DEF CLIENTOPT cloptsetname INCLEXCL
"EXCLUDE *:\...\documents and settings\...\userclass.dat"
(I used two lines to hopefully avoid bad wrapping in this post, but it is
all one command.)
Because of the spaces in the file specification, TSM sees it like this:
EXCLUDE *:\...\documents
If you were to put this in a dsm.opt file, you would need to use quotes
like this:
EXCLUDE "*:\...\documents and settings\...\userclass.dat"
It is no different for client option sets. The double quotes are necessary
in order for TSM to parse the entire file specification correctly.
To fix this problem:
1) Delete the incorrect EXCLUDE in your client options set.
2) Define the EXCLUDE like this:
DEF CLIENTOPT cloptsetname INCLEXCL 'EXCLUDE "*:\...\documents and
settings\...\userclass.dat"'
Note the use of single and double quotes.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Zoltan Forray/AC/VCU <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10/18/2002 05:43
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Whats wrong with this EXCLUDE
Can someone point out the obvious error(s) of my way........
I have the following statement in my CLOPTSET:
EXCLUDE *:\...\documents and settings\...\usrclass.dat
10/17/2002 20:42:49 ANE4987E (Session: 1853, Node: UCC-PC84) Error
processing '\\ucc-pc84\c$\Documents and Settings\kperdue.ADM.VCU.EDU\Local
Settings\Application Data\Microsoft\Windows\UsrClass.dat': the object is
in use by another process
Yes, I checked and the CLOPTSET is active for this node and this statement
is FORCE=YES !
