Hi Zoltan,

The file name in the ANE4987E message is not written as a single string,
so it isn't as if TSM is inserting the extra blank into the fully-formed
path. Rather, it is written as three components that are concatenated
together:

- the file space name (\\acadnt3\d$)
- the high-level name (\MSSQL7\Data)
- the low-level name (\BIS_Data.MDF)

It looks to me like there is a minor bug in the message skeleton that
causes the blank space to appear between the high-level and low-level
names. While it may be annoying, it is not otherwise impact the operation.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (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 <zforray AT VCU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/09/2002 05:57
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Include/Exclude question



I am trying to build CLOPTSETs for various, similar boxes. For instance,
NT/W2K boxes that have MS-SQL on them. Unfortunately, I have found at
least 4-different permutation on the directory names used.

I have noticed that in the error messages when attempting to backup the
SQL files as regular files, not using the TDP/TDS, I see these errors:


ANE4987E Error processing '\\acadnt3\d$\MSSQL7\Data \BIS_Data.MDF': the
object is in use by another process


My question, what gives with the extra blank/space after the "\Data" part
of the directory name ?