>Hello  All, We  have  had a  problem  with people  trying  to shut  down
>  listserv
>quickly.  They would  issue the  stop command  and become  impatient and
>issue the stop command a second time. This caused the stop command to be
>queued  for the  next listserv  session. Well,  the listserv  starts and
>stops as expected.
 
The next release  will ignore such stacked STOP  commands. Meanwhile, you
can add code to  PROFILE EXEC to delete all lines  in WAKEPARM FILE which
start with the word STOP or SHUTDOWN (note that this won't prevent things
like QUIET STOP, but I doubt your ops are doing that).
 
  Eric