Bill, have you tried the fixtest 3.1.0.7f? I believe that a fix was put
in there specifically for the problem you are talking about. It is not
mentioned in the fixtest because at the time I did not have an APAR
number for it, and I forgot to mention it in the accompanying README file.

Best regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."

This fix was for the problem where the DSMCUTIL would remove the nodes'
password from the registry if the CLUSTERNODE=YES parameter was coded. I
just heard back from IBM and this APAR where the client doesn't recognize
the disks as cluster resources is still open with no fix/fixtest available.
They will get back to me after talking with the developer to see if there is
a workaround, atleast.

Thanks,
Bill

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Matthew Muldoon
> Sent: Thursday, September 30, 1999 3:52 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Antwort: Backing up Microsoft Cluster Servers
>
>
> You need to look at the readme1 for the fixtest 3.1.0.7c  Client
> The 3.1.0.7 Client had a problem with the cluster wich was fixed later in
> the fixtest.
> It is available on the ftp server under fixtests.
>