[comp.os.vms] No terminate Systartup.com

DL01@TE.CC.CMU.EDU (David B. Love) (08/02/88)

  When our Systartup.Com hits an error (such as trying to execute an
  indirect file that someone accidentally deleted), it aborts the
  rest of the startup file.  Is there a way to make it continue
  executing ?  Can anyone think of anything particularly dangerous
  about doing this ?  


  David Love
  DL01@TE.CC.CMU.EDU
-------

jayz@cullsj.UUCP (Jay Zorzy) (08/06/88)

From article <12419017247.14.DL01@TE.CC.CMU.EDU>, by DL01@TE.CC.CMU.EDU (David B. Love):
> 
>   When our Systartup.Com hits an error (such as trying to execute an
>   indirect file that someone accidentally deleted), it aborts the
>   rest of the startup file.  Is there a way to make it continue
>   executing ?  Can anyone think of anything particularly dangerous
>   about doing this ?  

Just insert a "Set NoOn" at the beginning of your Systartup.Com file.  This
will inhibit error checking by the CLI during the processing of that command
procedure.  In fact, I think this is suggested in the System Manager's 
Reference Manual.  Just be careful that your conditions can't cause an 
infinite loop.

-Jay Z.

helen@uhccux.uhcc.hawaii.edu (Helen Rapozo) (08/07/88)

In article <12419017247.14.DL01@TE.CC.CMU.EDU> DL01@TE.CC.CMU.EDU (David B. Love) writes:
>
>  When our Systartup.Com hits an error (such as trying to execute an
>  indirect file that someone accidentally deleted), it aborts the
>  rest of the startup file.  Is there a way to make it continue
>  executing ?  Can anyone think of anything particularly dangerous
>  about doing this ?  
>
>
>  David Love
>  DL01@TE.CC.CMU.EDU
>-------

You can put SET NOON at the top of your SYSTARTUP.COM.  Of course 
there might be a danger of the system might be missing something
when it's up and running.  I remember someone changed a few lines
of code that prevented some DECnet device drivers to be loaded
properly thru SYSGEN (that person for some strange reason put a $
in front of those lines).  This cause the DECnet startup to fail
which in turn cause system to fail as a LAT load host and also
caused the system to forget it had remote ports on the LAT.  This
being the case other applications started to complain why it
couldn't find 3 or 4 ports on the LAT.

Luckly this happen doing a time when no one was around so it was
possible to change the SYSTARTUP.COM and restart the system.

-- 
BITNET address: helen@uhccux
UH Admin Network: HCCADA::CS_RAPOZO
US Mail Address: 874 Dillingham Blvd., Honolulu, HI 96817, Ph# (808) 845-9202
PLATO address: helen rapozo/honcc/hawaii