  DECevent and SYS$SYSDEVICE:[SYSEXE]SYSBOOT? 
 The Question is:
 
After the instalation of DECevent the file
 
SYS$SYSDEVICE:[SYSEXE]SYSBOOT.EXE
 
set it'self into a state of (No such file)
 
This was for all nodes of the cluster.
 
Is this a known problem?
 
 
 The Answer is:
 
  SYS$SYSDEVICE:[SYSEXE]SYSBOOT.EXE is a file alias that was used for the
  MicroVAX I and related systems, systems using older versions of the
  primary VMB.EXE bootstrap on the console media, or in the boot ROM.
  (Systems with older versions of VMB on the console media should be
  updated.  There is no way to update the version of VMB.EXE present in
  the MicroVAX I boot ROM, however.)  This SYSBOOT file alias can safely
  be removed (via a SET FILE/REMOVE command, and not via DELETE), and the
  SYS$SYSDEVICE:[000000]SYSEXE.DIR directory can then be deleted, in system
  disk configurations that are not bootstrapping MicroVAX I systems.
 
  This particular SYS$SYSDEVICE:[SYSEXE] directory scheme and this SYSBOOT
  alias is a result of the pre-rooted system disk structure that was used
  on releases prior to V3.0.  This directory and this SYSBOOT alias are not
  used by any current OpenVMS VAX systems -- VMB now looks for SYSBOOT in
  the correct (current) location, and does not depend on the alias entry.
 
  This SYSBOOT alias has been known to occasionally become corrupted.
  There are several possible causes that have been seen to cause this
  corruption over the years -- one of the more common reasons involves
  an errant system disk restoration operation.
 
  The Wizard would not expect this file to be affected specifically by the
  installation of the DECevent kit.
 
  If you have questions on this, the Wizard would encourage you to contact
  the customer support center directly.
 
