We have had a sutdown batch job for I can't remember how long.  It closes
down everthing gracefully, and saves everthing that should be saved.  I
didn't realise that nobody else thought of this.
Terry

At 03:19 PM 11/19/98 -0500, Doug Werth wrote:
>Hi all.
>
>I have recently designed a command file to be executed just before the
>=SHUTDOWN is issued. If anyone would like a copy you can get it from our web
>site at http://www.beechglen.com Click on the downloads button and look for
>PRESHUT.TXT
>
>The focus of this command file is primarily to make sure there are no hidden
>"gotchas" when you bring the system back up as well as to remind the you of
>a few things. Here are the steps it goes through:
>
>o  Shuts down our software if it is installed and running.
>o  Checks to make sure that the creator of SYSSTART is MANAGER.SYS
>o  Checks to see if there are any non-validated sections of NMCONFIG and
>validates them if accordingly.
>o  Shuts down the network.
>o  Makes a copy of the current booted configuration group in case CONFIG.SYS
>is screwed up and you need to recover. It is much faster to reboot from a
>different group than to find an SLT and perform an UPDATE CONFIG
>o  Reminds the user that they may want an SLT and backup and/or
>configuration listing if they are shutting down for the purpose of hardware
>maintenance. Optionally will provide the SLT and configuration list.
>
>Currently it does not abort sessions or jobs. Those will be taken care of by
>the implicit =LOGOFF that occurs when you =SHUTDOWN.
>
>(CYA)
>I have tested this script fairly extensively but provide no warranty of any
>kind.
>(/CYA)
>
>Often I have wondered why you there is a script that automatically executes
>when you boot up a system (SYSSTART) but no corresponding system shutdown
>script. Maybe we can get that on an enhancement ballot?
>
>Any comments or suggestions are appreciated.
>
>Doug.
>
>Doug Werth                                     Beechglen Development Inc.
>[log in to unmask]                                       Cincinnati, Ohio
>
>
>The opinions expressed do not necessarily represent the views or opinions
>of Beechglen Development. They might, but not necessarily. They represent
>solely the opinions of the author.
>
>