[Info-vax] Correct way to dismount shadowed volume set as late as possible?

[Matthew Wilson]

Thank you for the pointers, Stephen.

On 03.25.2021 20:32, Stephen Hoffman wrote:
>For this case, you're running a VAX version of OpenVMS VAX, and AFAIK 
>all versions that predates availability of SYSHUTDWN_0010.COM, so you 
>won't have access to that procedure here.  The furthest back that the 
>MANAGE patch got was V7.3-2, IIRC. Which means you'll be dismounting 
>in SYSHUTDWN.COM.

Ah. Yes, SYSHUTDWN.COM seems to be the only place to add to the shutdown
process but it seems to run pretty early in the shutdown process, so I
hadn't considered it at first since I assume things like the audit
server and other processes that would have open files on my shared
cluster volume would still have them open. Sounds like the idea is I
need to take care of stopping all of those things earlier in my
SYSHUTDWN myself.

>You will also want to use an edited version of 
>SYS$EXAMPLES:MSCPMOUNT.COM to mount and maintain volumes mounted—this 
>procedure can be configured and run and operates as a detached 
>process—and probably not what you're doing now with your MOUNT 
>commands in SYSECURITY.COM, as MSCPMOUNT contends with cluster member 
>hosts coming and going as can happen. I prefer to avoid using MOUNT 
>/CLUSTER here.

Ah, I pulled in some logic from SYS$EXAMPLES:CLU_MOUNT_DISK.COM based on
a note I saw in the _OpenVMS Cluster Systems_ manual, so I am ensuring
the disks across the servers is available before I mount the shadow set,
but I see MSCPMOUNT.COM appears to be a more comprehensive solution.
I'll take a look at that.

Thanks,
Matthew