$GETDVI and the clusterwide mount count
Rob Brooks
lexical function) is the inability to determine on how many nodes
a device is mounted. The DCL command SHOW DEVICE *does* return that
information, but the $GETDVI item code DVI$_MOUNTCNT returned the number
of times a device is mounted on the local node (the use of the /SHARE
qualifier on the MOUNT command can allow, in some cases, a device to be
mounted more than once.) For various reasons, the environment
in which $ SHOW DEVICE executes made solving the problem much easier than
what was needed for the system service interface. For those that are
curious, see the sources to [SYS]SYSGETDVI.MAR and [SYS]SYSGETDVI_SUBS.C
when the V8.3-1H1 source listings are available.
Given the above, the arrival of the new item code DVI$_MOUNTCNT_CLUSTER
may be of interest. This item code will "first" appear in OpenVMS I64
V8.3-1H1, expected to ship some time in the fall of 2007. As V8.3-1H1
is a limited hardware release targetted for I64 blade systems, there will
be no release for Alpha; the next general purpose release for OpenVMS Alpha
will be V8.4. No backport for OpenVMS VAX will be done.
This item code has been backported to V7.3-2, V8.2, V8.2-1, and V8.3, and
will require future SYS (for $GETDVI) and DCL (for F$GETDVI) kits. There will
be no backport for the RTL routine LIB$GETDVI. I expect that the kits for the
above versions will be available in the next month or so.
As an added bonus, another new item code (DVI$_ADAPTER_IDENT) that
will first appear in V8.3-1H1 has been backported. This item code
will return the identification string associated with an adapter
in the configuration files SYS$SYSTEM:SYS$CONFIG.DAT and
SYS$SYSTEM:SYS$USER_CONFIG.DAT. The item code pulls the string out of
in-memory structures created (typically) at boot time or in response
to the command SYSMAN IO REBUILD, not directly from the files themselves.
But wait, there's more! This backport makes $GETDVI functionally equivalent to
that which shipped in V8.3. That means that all item codes that exist
in V8.3 will be useable on a system with the relevant SYS/DCL kits.
The only caveat is that some of the LAN item codes added for V8.3 might
not work correctly -- some of the boolean ones require LAN driver changes
that may or may not be forthcoming.
The documentation in the SYS kit will explain how to add the needed new
item code definitions to $DVIDEF for your relevant language. No additional
changes are needed to use the new item codes with F$GETDVI, once the required
SYS and DCL kits are added.
This is likely my last enhancement to $GETDVI; while still employed by HP in
Nashua, I'm no longer a member of VMS Engineering.
I hope to see some of you at the bootcamp next month!
--
Rob Brooks MSL -- Nashua brooks!cuebid.zko.hp.com
JF Mezei
> Given the above, the arrival of the new item code DVI$_MOUNTCNT_CLUSTER
> may be of interest.
Yeah ! Horray ! Wooppy ! (says JF while jumping up and down in joy)
> No backport for OpenVMS VAX will be done.
Boo ! Sniff ! (says JF while crying on his desk).
I currently have cluster-wide disk mounting and dismounting procedures.
The lack of backport to VAX 7.3 means that I cannot take advantage of
this much needed feature.
> This is likely my last enhancement to $GETDVI; while still employed by HP in
Booo ! Sniff ! (says JF while listening to funeral march music).
Thanks for all your contributions to VMS over the years and especially
for your patience here on cov !