[Info-vax] hostunavailable

[Michael Moroney]

"Jilly" <jilly at hp.com> writes:


>"Bob Koehler" <koehler at eisner.nospam.encompasserve.org> wrote in message 
>news:7bHkzFuGeJsg at eisner.encompasserve.org...
>> In article <jq88s2$84c$1 at usenet01.boi.hp.com>, "Jilly" <jilly at hp.com> 
>> writes:
>>>
>>> No because SYSMAN will not modify the existing UCBs from MPI1$DK to $1$DK
>>> and the device locks are all based on the device name.
>>
>>   What should be happening is that new UCBs should be being created,
>>   connecting to the new device name.  Since the disks were dismounted
>>   before the change it is perfectly OK to mount the volumns under
>>   the new device name.  File system locks are then based on the volume
>>   name.
>>
>>   The problem is the new UCBs not showing up.
>>

>Logically one would think that the configure code would be able to 
>update/modify the existing UCB or mark the existing UCB offline and create a 
>new UCB but the code 'sees' that it 'knows' about a DKnn from MPI1 and thus 
>won't do anything at all. 

I don't think so.

I've lost a lot of brain cells since I was messing with the MSCP Server
and DUDRIVER, but what I recall is that DUDRIVER on the client node will
see the $1$DKxxx device as a completely new drive, with the old name
unreachable, as the o.p. expected.