Larry Boyd wrote after I wrote:
 
[.....SNIP.....]
>>just say    PURGE  or  ERASE  <database_name>.
>>And your data is toast.
 
>Actually, there is one more requirement.  The data base can not be
>opened by any users.  This doesn't solve Ken's problem, but does
>add one more stopping point.
 
Larry is of course correct;  that is one more check point.  But
the mental disconnect is most likely to occur late on swing shift
and/or on weekends, when there are no production users online.
Typical senario is wanting to make a new copy of the production
database, before which I need to purge the old version in the test
account.......
 
>This is a problem that I ran into, myself, about 10 years ago.  How
>do I know quickly what window am I in? (Back before windows, I used 2
>copies of Reflection for multiple access to the 3000).  I decided to
>use different color schemes for each environment.
 
Good idea.  But DBUTIL still ought to ask for confirm.....
 
[.....SNIP.....]
>I realize that MPEX is a third-party product, however it does at least
>require you to confirm, unless you use the YESPURGE command.
 
MPEX and various command scripts are certainly other options.
But I would again refer you to the answer I gave moments ago:
this should be a bundled solution.....     :-)
 
Ken Sletten