The only way I could get this to run and it ran great was to have
node_name - UPPER CASE
FILESPACE_NAME - lower case
HL_NAME - UPPER CASE
ll_name - UPPER CASE
I tried most combinations and this was the only one that would come back
with results.
This will definitely make it easier than connecting to the machines and
querying for the file.  It took about 2 minutes to run which was not bad
at all.  It's not something we use regularly but at times do need.

Thanks for all the help,
Eric

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Gerhard Ginzler
Sent: Tuesday, March 01, 2005 2:28 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: How to display all versions of a file


Andrew Raibeck wrote:

 > Hi Eric,
 >
 > For your example, \\MOLSON\C$\DATA\status.txt, the correct criteria
would
 > be:
 >
 >    filespace_name='\\MOLSON\C$' and
 >    hl_name='\DATA\' and
 >    ll_name='STATUS.TXT'
 >
 > For Windows, note that:
 >
 > - All components are stored in upper case, regardless of how they
appear
 > on the client machine.

Hmm, my filespace_names are in lower case:
Node Name           Filespace       FSID     Platform     Filespace
                     Name                                  Type
---------------     -----------     ----     --------     ---------
CC.AMSEL            \\amsel\c$         1     WinNT        NTFS

 >
 > - The hl_name begins and ends with a backslash (unless it is the
drive
 > root, in which case there is only one backslash).
 >
 > - When you concatenate filespace_name, hl_name, and ll_name, they
should
 > form a proper path.
 >
 > Regards,
 >
 > Andy
 >
 > P.S. Suggestion: Selecting from the BACKUPS table can take a very
long
 > time. If you plan to do a lot of data mining from it, consider
selecting
 > all output from the table and redirecting to a file (make sure you
have
 > tons of free disk space), then use an external tool to mine the data.
 >
 > 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.ibm DOT com
 >
 > The only dumb question is the one that goes unasked.
 > The command line is your friend.
 > "Good enough" is the enemy of excellence.
 >
 > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-02-27
 > 17:54:07:
 >
 >
 >>This is something I was also looking for.
 >>Normally I go to the client machine and query the backups to see the
 >>history of a file.
 >>From what I can tell and I'm not very good at the "select" SQL
 >>statements is the following a correct interpretation of the statement
if
 >>I was looking for a single files backups.
 >>----------------------------------------------
 >>Select * from backups where node_name='MOLSON" and
 >>FILESPACE_NAME='\\MOLSON\C$' and HL_NAME='C:\DATA\' and ll_name like
 >>'status.txt'
 >>--------------------------------------
 >>MOLSON - client node
 >>FILESPACE_NAME - FILESPACE where file is located
 >>HL_NAME - Directory where file is located
 >>ll_name - actual file you are looking for
 >>
 >>Thanks
 >>Eric

--
_____________________________________
eMail: gerhard.ginzler AT meduniwien.ac DOT at
tel: +43 1 40160-21209
IT Systems & Communications (ITSC)
Medizinische Universitaet Wien
Spitalgasse 23, A-1090 WIEN