[Info-vax] Reconfiguring VMS 6.2 - Shadow set question
Jan-Erik Soderholm
jan-erik.soderholm at telia.com
Mon Oct 22 17:43:45 EDT 2012
supervinx wrote 2012-10-22 21:56:
> Il Mon, 22 Oct 2012 19:42:28 +0000, Phillip Helbig---undress to reply ha
> scritto:
>
>> In article <k62ou3$alf$1 at tdi.cu.mi.it>, supervinx <nessuno at libero.it>
>> writes:
>>
>>>> $ mount dsa0: /shadow=($1$dka100:,$1$dka200 /system V47701_sys
>>
>> If it really is the system disk, you shouldn't have this command as part
>> of the startup. Use such a command ONCE to create a shadow set, then
>> put both physical devices into the boot-device console variable. When
>> you specify a device at boot, specify just one. (Having the list
>> enables an automatic boot if one member doesn't work, resulting in a
>> one-member shadow set (assuming you have 2 altogether).) The shadow set
>> will be formed very early in the boot sequence. Think about it:
>> normally you don't MOUNT the system disk, since it is already known from
>> the boot; same with a shadow set as the system disk.
>
> You mean I can remove safely this line from the customized startup file ?
> What else should I change ?
> I removed all references to DKA200: and DKA400: disks (the missing ones)
> and everything works well.
>
>
>
It's standard not to MOUNT the system/boot shadow set in any
command file. That is done, just as Phillip described, early
and automaticly in the boot process, before the SYSTARTUP_VMS
command file is called.
From the beginning you manualy set the system parameter(s)
SYSSHAD-something to the right value and reboot, that mounts
automaticly the first DSA device as a single disk shadow set.
Then you manualy add the other disk and that is recorded on both
system disks and used at the next reboot to automaticly mount
both (or the single available) system disk(s).
In no case do you need a MOUNT of the system disk in any
command file.
Jan-Erik.
More information about the Info-vax
mailing list