The context is just an "dsmc incr"!
No restore. And: Drive d: is really not existing! Nowhere.
And there is nothing specified like "include d:..." just "include *:..."
I just don´t understand. It´s also not a security problem, as somebody else
supposed!
Kindly regards,
Oliver
___________________________________________
"France, Don (Pace)" <don.france-eds AT EDS DOT COM> on 16.05.2000 18:14:37
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Oliver Janzen/Germany/IBM)
Subject: Re: ANS1134E Drive d: is an invalid drive specification
Oliver,
What is the context for the error message? (ie, if you're trying to
restore
from the d: drive, and "domain c:" in dsm.opt, then only the c: drive is
valid). Does the same command work for your c drive? I've seen cases
where
the restore must have UNC form of file system name --- ie, \\node\d$ else I
cannot restore.
Regards,
Don France
Technical Architect, P.A.C.E.
San Jose, CA
mailto:dfrance AT pacbell DOT net
PACE - http://www.pacepros.com
Bus-Ph: (408) 257-3037
> -----Original Message-----
> From: Oliver Janzen [mailto:OJANZEN AT DE.IBM DOT COM]
> Sent: Tuesday, May 16, 2000 9:34 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: ANS1134E Drive d: is an invalid drive specification
>
>
> Client 3.1.0.7 on NT 4.0
> Server 3.1.2.50 on OS/390
>
>
> Dear *SMers,
>
> my NT Client gives me the message
>
> ANS1134E Drive d: is an invalid drive specification
>
>
> although the drive is non-existent. I made some statements like
>
> include "*:\windows\*.dll"
>
> in the dsm.opt. The domain is set to "domain c:".
> Therefore I don´t understand the error message.
> Anyone seen this before?
>
> Kindly regards,
> Oliver Janzen.
>
|