[Info-vax] MOUNT/SYSTEM before SHADOWING license loaded: /SYSTEM vs. /NOSYSTEM

[Phillip Helbig---undress to reply]

For a long time now, I have been mounting /CLUSTER a shadowed disk which 
itself contains the license database.  At least when this is done at 
startup (and I have to do it at startup, since SYSUAF and most other 
files which one can move off the system disk are on it), it works, even 
though the shadowing license is not loaded until after this shadow set 
is mounted.

Would such a mount work at startup but /NOSYSTEM?

The reason I need to do this is that I have to issue SET VOLUME/LIMIT on 
this shadow set, which requires a /NOSYSTEM mount.  The idea is the 
following:

$  if f$trnlnm("volume_limit_start") .nes. "TRUE"
$  then
$    define/table=lnm$syscluster volume_limit_start TRUE
$    mount/nosystem/noassist/norebuild -
      DSA510:/SHADOW=($33$DKB0:,$33$DKB500:) USER
$    set volume/limit dsa510:
$    dismount dsa510:
$    define/table=lnm$syscluster volume_limit_end TRUE
$  else
$wait_for_volume_limit:
$    if f$trnlnm("volume_limit_end") .eqs. "TRUE" then goto volume_limit_done
$    wait 0:0:5
$    goto wait_for_volume_limit
$  endif
$volume_limit_done:
$!
$!==============================================================
$!      DSA510:/SHADOW=($22$DKA0:,$22$DKA500:,$44$DKA400:) USER
$    MOUNT/CLUSTER/NOASSIST/NOREBUILD -
      DSA510:/SHADOW=($33$DKB0:,$33$DKB500:) USER

The logical names are to coordinate near simultaneous mounting after a 
cluster reboot.

Note that the original list of members is commented out, replaced with 
two members on the same node.  The old shadow set has two members on one 
VAX and another on another VAX (up until recently: 2 VAXes and 1 ALPHA 
in the cluster).  Since DDS works only for ALPHA, I have to take the 
VAXes out of the cluster, so the idea is:

   o  add 2 more ALPHAs to the cluster (already done)

   o  shut down the entire cluster

   o  physically move the cable connecting the two $22$ members from a
      VAX to what was formerly the only ALPHA in the cluster (slow 
      machine)

   o  reboot the cluster, now consisting of the original (slow) ALPHA 
      and two new (fast) ALPHAs

   o  during reboot, the code above will be executing, allowing me to
      use DDS and DVE on the shadow set

   o  use DDS and DVE to move the DISK$USER shadow set from the old 
      disks to newer disks

   o  replace slow ALPHA with fast ALPHA

The reason for moving the shadow set is that the old disks are 5 MB/s 
and the new ones are 40 MB/s (though at the moment limited to 20 MB/s by 
the BA356 shelf) and are also easy-to-replace SBB disks.  Since the new 
disks are slightly larger (17773524 as opposed to 17755614 blocks), I 
have to use DDS and DVE to move the shadow set to the new disks.

Have I missed anything?