Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!ucsd!rutgers!apple!voder!cullsj!jayz
From: jayz@cullsj.UUCP (Jay Zorzy)
Newsgroups: comp.os.vms
Subject: Re: No terminate Systartup.com
Message-ID: <384@cullsj.UUCP>
Date: 6 Aug 88 00:06:04 GMT
References: <12419017247.14.DL01@TE.CC.CMU.EDU>
Organization: Cullinet Software, San Jose, CA
Lines: 14

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.