[Info-vax] secondary page and swap files, MINICOPY, SYSHUTDWN.COM

[Phillip Helbig---undress to reply]

I set up some secondary page and swap files on a shadowed non-system 
disk.  After a reboot, I had a merge on this shadow set (and on no other 
shadow set).  Do I need to put something into SYSHUTDWN.COM to avoid 
this?

Now that I have only ALPHA nodes in the cluster, using MINICOPY is
easier.  When I dismount a single shadow-set member with
/POLICY=MINICOPY, then I get a MINICOPY when it comes back into the 
shadow set.  What is the point of MOUNT/POLICY=MINICOPY during the 
initial creation of the shadow set?  Would this provide MINICOPY 
functionality when a single member leaves and returns, even if it is not 
dismounted with /POLICY=MINICOPY?  Is there any reason not to specify
/POLICY=MINICOPY at the initial creation of a shadow set?

Is the problem regarding the merge mentioned in the first paragraph in 
any way related to MINICOPY?  IIRC, the shadow set was not initially 
created with /POLICY=MINICOPY.

Would HBMM have helped with the problem regarding the merge?

Is it possible to turn on HBMM but not for the system disk (since I 
don't want DOSD)?