[Info-vax] Reconfiguring VMS 6.2 - Shadow set question

[JF Mezei]

On 12-10-22 03:18, supervinx wrote:

> Can I use some logical symbol instead of go hunting all DSAXXX: reference ?

You can specify a logical name as last argument of a mount command. Just
about everywhere (but not everywhere), you can use that logical name in
command procedures etc.

mount dka300: myvolume mydisk


dir mydisk:[0000000]  will do the same as dir dka300:[000000]

theoretically, you could use DSA001 as logical name that is created when
dka300: is mounted and this woudl resolve almost all existing references
to DSA001 .

However, there are instances where command procedures absolutely require
the physical device name. For instance, when creating rooted logical names:

$define/system/trans=(terminal,conceal) MYUSERS  dsa001:[users.]

so reference to myusers:[jdoe] actually maps to dsa001:[users.jdoe]

But in this case, the device name cannot be a logical name. So you have
to update those references to the actual device name instead of relying
on the creation of a DSA001 logical name to "fake" the old device.



SEARCH will be your friend here.

SEARCH SYS$MANAGER:*.com DSA001
SEARCH SYS$STARTUP:*.com DSA001

you can also check inside your application directories to see if there
are references to it.

You can also do
SEARCH dka100:[000000...]*com DSA001  to search the whole disk for any
command procedures that reference the DSA001 device name.

Note that some applications may store their configuration in data files
as opposed to defining symbols and logical names in command procedures.


The best bet is to keep the shadow set with just one disk while you
research your complete system to see how many "hard" references there
are to the DSA001  device name.  Then you can plan your strategy to
switch to using the physical disk device (DKA100: ) without volume
shadowing.