[Info-vax] minicopy confusion explained

[Robert A. Brooks]

On 12/31/2012 8:20 AM, Phillip Helbig---undress to reply wrote:

>> At first glance, it seems that MULTIUSE is not on 7.3-2; another reason
>> to upgrade.  I can't test it yet, so I'll ask a question: Does MULTIUSE
>> allow a minicopy when a member is removed with DISMOUNT without
>> specifying POLICY=MINICOPY?  If so, is POLICY=MINICOPY needed anymore at
>> all for shadow sets which have HBMM?
>
> Of course, some things are in 7.3-2 but not documented, like VOLSIZE and
> EXPSIZE for F$GETDVI, but this is not one of them:
>
> $ SET SHADOW/POLICY=HBMM=(MASTER_LIST=*,MULTIUSE) DSA370:
> %SYSTEM-F-HBMMBADPOLSPEC, HBMM policy specification syntax error -- please check documentation

MULTIUSE was an HBMM add-on after the initial implementation.  Whereas 
the first release for HBMM was an UPDATE kit to V7.3-2, I *guess* that 
MULTIUSE came out for V8.4 (perhaps V8.3) and was not backported.

With respect to $GETDVI and V7.3-2 -- whenever I worked on $GETDVI, I 
always backported the work to V7.3-2.  It was not a complete backport, 
in that the LIB$ variant would not necessarily work, and it was 
typically not documented.

I'm pretty sure that my last major addition to $GETDVI -- the addition 
of the pathname parameter (which is only relevant for a few item codes), 
the addition of the long-awaited dvi$_mountcnt_cluster item code, and 
dvi$_adapter_ident were backported to V7.3-2.  I *think*
that dvi$_mountcnt_cluster may have been documented in a V7.3-2 SYS kit.

                           -- Rob