>(Martha McConaghy) writes:
>OK, I may be pushing it, but here's my second question of the day.  I
>am trying to use the linemode client on OS/2 to display the backup records
>for another node.  I used the following:
>
>dsmc query backup -node=othernode -pass=blahblah c:\*
>
>No matter what I put for the file specification, ADSM comes back and says:
>
>ANS4087E No files have previously been backed up for '\*'
>
>I know there are files there, and I can view them using the GUI client.
>I have checked IBMLINK and found no mention of it there.  Has anyone else
>seen this, or can reproduce it?  My VM server is at v1 r1 l0.4 and
>my OS/2 client is at v1 r1 l0.18.  I suspect that this is a bug, but want
>to make sure I'm not missing something.
>
>Martha

responce:(from Bill Colwell)
>   The problem is that ADSM is looking for a filespace with the name ofyour
>C drive.  To find out the name of the filespaces for the other node do query
> filespace'.
>If the dirve is called 'BILLDRIVE', enter the query backup as 'q b
> {BILLDIRVE}\*'.  This is
>documented in the os2 ugr release 1 on page 74 under the discussion of
> 'fromnode'.
>You would have to use this syntax for your own node if you have two filspaces
> for
>the C drive or any other drive.  Why would you have two filespaces for he C
> dirve?
>One reason would be to simulate the long awaited and MUCH DESIRED pointin time
>capability.
>
>Bill Colwell


    Removable drives and remote drives are other reasons for multiple
labels stored on the ADSM server under the same drive letter.  For
example backing up diskettes (A:).

    When you issue "dsmc query backup C:\*" ADSM looks at the label
of the local C: drive and substitutes this into the query.  This
enables the most common use of the query command in a easy to use
format (most user like to type in C: and not the label).  Therefore
the shorthand notation of the dsmc query command "dsmc q backup c:\*"
will be equivalent to "dsmc query backup {CURRENT_LABEL}\*".
   As Bill has stated, if you want to query or restore a drive
with a different vol label than your current drive you must use
the long version of the command with the {}.

--David Derk--
=========================================================================