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

[Kenneth Fairfield]

On Aug 10, 12:00 pm, hel... at astro.multiCLOTHESvax.de (Phillip Helbig---
undress to reply) wrote:
> In article
> <7ce77c2e-0418-4b40-b89e-6226cc1ea... at a2g2000prf.googlegroups.com>,
>
> Kenneth Fairfield <ken.fairfi... at gmail.com> writes:
> > > 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?
>
> > I believe this is normal/expected.  Any process still running when the
> > system halts could have pages mapped to a pagefile on that shadow
> > set, and therefore, a merge is required on reboot.  The only solution
> > is to be sure all processes (other than, like, the one running the
> > shutdown), are stopped so that pagefile disk can be dismounted
> > cleanly.
>
> I have many files such as SYSUAF.DAT etc on a non-system-disk shadowset.
> I had similar problems there, but took steps to make sure nothing still
> had those files open.  I'm pretty sure there is no application which has
> the files open, but rather the "system itself".

You could try doing a MC SYSGEN DEINSTALL <pagefile>/PAGEFILE
in SYSHUTDWN.COM.  Or search SYS$SYSTEM:SHUTDOWN.COM
and see whether it deinstalls the pagefiles.  Shutdown seems to be
able to cleanly dismount the system disk, but it may not have logic
to find pagefiles on non-system disks.

[...]

> My setup is locally connected SCSI disks, all with a direct connection
> to only one node.  Every disk is a shadowset.  System and page/swap
> disks have both members on the same node.  Other disks have members on
> different nodes.
>
> For PLANNED reboots etc, everything works OK.  If one member goes down
> with a node, at worst I get a quick minicopy.
>
> For unplanned reboots, I expect merges.  Since I haven't added 4096 to
> SHADOW_SYS_DISK, I can't expect minimerge on system disks.  OK.  What
> about other disks.  Do I need to "turn it on" somehow, or is it there
> automatically?  Still at 7.3-2.

Mini-merge needs to be enabled on a volume-by-volume basis.  I don't
have access to the systems I used to do this on, and its been a few
years, so my memory is foggy.  One or more things need to be done
before mounting the volumes.

I think setting a MINIMERGE POLICY (see the docs or Help) is one of
them.  For sure, if you are going to set merge priorities, that needs
to be
done before the mount.  Otherwise, I think it's just a
MOUNT/POLICY=MINIMERGE.

    -Ken