[Info-vax] SYS$COMMON:[SYSERR]CLUE$NODE*

Phillip Helbig undress to reply helbig at asclothestro.multivax.de
Sat Mar 14 12:32:56 EDT 2015


In my effort to enable easy cloning of system disks (i.e. upgrade or
otherwise modify one disk, make a copy of it by breaking a shadow set
then use it to boot another node---it contains all SYS$SPECIFIC roots
for all nodes and these (relatively static) are kept in sync, the idea
being that [VMS$COMMON...] should be the same on all), I've come across
SYS$COMMON:[SYSERR]CLUE$<nodename>* files.  I think it is OK to lose
these during a cloning process.  Still, why put a file in SYS$COMMON and
put the node name in the file?  Why not put it in the corresponding
directory in SYS$SPECIFIC without the node name?  I guess only
CLUE$HISTORY.DAT should go in SYS$COMMON. 

(Of course, with the node names in the file names, I can just copy the
CLUE$<nodename>* files to a non-system disk for safe keeping; for
CLUE$HISTORY I need to add the node name to the file name (OK in my case
since there is only one boot server per system disk, although there
might be one or more satellites).) 




More information about the Info-vax mailing list