ADSM-L

Re: Directory names with embedded spaces on NT (ATT: Andrew

2015-10-04 18:04:42
Subject: Re: Directory names with embedded spaces on NT (ATT: Andrew
From: Andrew Raibeck [SMTP:storman AT US.IBM DOT COM]
To: ADSM-L AT VM.MARIST DOT EDU
This may actually be a problem compounded by APAR IC13818. IC13818 addresses
the following scenario:

1) You back up an NT volume whose name is "MyVol" (or any other name with
lower-case letters in it).

2) You try to query backup versions of this volume using the filespace name,
i.e.:

   QUERY BACKUP {MyVol}\* -SUBDIR=YES

3) You get a message indicating no match found.

The fix is in version 2.1.0.6. To access MyVol's data, you need to specify the
filespace name thus:

   QUERY BACKUP {"MyVol"}\* -SUBDIR=YES

This will show you MyVol's backup versions.

However, if the file space name has a space in it, i.e. "My Vol", then this
won't work. For file spaces that have all upper-case letters *and* have a space
in the name, i.e. "MY VOL", you can do this:

   QUERY BACKUP "{MY VOL}\*" -SUBDIR=YES

But this won't work if the file space name has lower-case letters *and* a space
in the name, due to IC13818. Using quotes both within and without the curly
braces doesn't work, either. The only work-around that comes to mind is to:

a) From an ADSM Admin client, rename the filespace so that it has either all
upper-case letters and/or has no spaces in the name. Then the query should
work. For example, depending on what you do, you can do one of these:

   QUERY BACKUP "{MY VOL}\*" -SUBDIR=YES
   QUERY BACKUP {"MyVol"}\* -SUBDIR=YES
   QUERY BACKUP {MYVOL}\* -SUBDIR=YES

This is the first time I've looked at this scenario (mixed-case *and* spaces),
so I might not have covered all the bases yet. But I will forward this
information to ADSM development.

Andy Raibeck
ADSM Level 2 Support

        ADSM-L AT VM.MARIST DOT EDU
        10-20-97 05:12 PM
Please respond to dthorneycroft AT lacsd DOT org @ internet

To: ADSM-L AT VM.MARIST DOT EDU @ internet
cc:
Subject: Re: Directory names with embedded spaces on NT (ATT: Andrew

I have a similar problem which Sid Wong from IBM techsupt has been
helping me with. I am also running on WindowsNT.
When attempting to do a dsmc Q backup command from our ADSM server for a
client that has a space in the volume label, using the following
command, I get a message that no files have been backed up. The same
command works for drives that have no spaces in their label, and from
the client, where I can specify the drive, and don't need to include the
filespace name.

Command used:
 dsmc> q backup -fromnode=cs02 "{Platinum Data}\adsm\baclient\*.log"
 ANS4087E No files have previously been backed up for
'\ADSM\BACLIENT\*.LOG'


Andrew Raibeck wrote:
>
> Try putting the entire file spec in quotes, i.e.:
>
>    dsmc> restore "c:\the lazy dog\*"
>
> Andy Raibeck
> ADSM Level 2 Support
>
>         ADSM-L @ VM.MARIST.EDU
>         10-19-97 09:50 PM
> Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet
>
> To: ADSM-L @ VM.MARIST.EDU @ internet
> cc:
> Subject: Directory names with embedded spaces on NT
>
> Hi,
>
> I am having trouble, on WindowsNT, restoring directories that have embedded
> spaces in their names, using the command line client. I can get it to work
> using the GUI OK.
>
> I have tried the following without success:
>
> dsmc> restore c:\the lazy dog\*.*
> dsmc> restore c:\"the lazy dog"\*.*
> dsmc> restore c:\thelaz~1\*.*
>
> The only reference that I have been able to find regarding embedded space
> is problems installing the ADSM client into a directory where the path
> contains an embedded space.
>
> I am running NT 4.0 SP3 and 2.1.0.6 of the 32-bit Windows client.
>
> Any suggestions?
>
> regards,
>
> Trevor
<Prev in Thread] Current Thread [Next in Thread>