Stops the Rdb/VMS monitor.

 Digital Equipment Corporation recommends you use the DCL-level
 RMU/MONITOR STOP command instead of the RDO STOP MONITOR statement.
 While they share the same function and require the same privilege,
 the RDO STOP MONITOR statement requires you to be attached to an
 Rdb/VMS database on your VAX node.  (Attached means you have issued
 an INVOKE statement and have not yet issued a FINISH statement.) With
 the RDO statement, being attached to an Rdb/VMS database means that
 STOP MONITOR WITH DELETION will delete your own process.  The
 equivalent RMU/MONITOR STOP /ABORT=DELPRC command does not pose this
 problem.

 Example:

   RDO>  STOP MONITOR WITH EXIT

Additional information available:

MoreExampleFormat

 Digital Equipment Corporation recommends you use the DCL level
 RMU/MONITOR STOP command instead of the RDO STOP MONITOR statement.
 While they share the same function, and require the same privilege,
 the RDO STOP MONITOR statement requires you to be attached to any
 Rdb/VMS database on your VAX node.  (Attached means you have issued
 an INVOKE statement and not yet issued a FINISH statement.) With the
 RDO statement, being attached to an Rdb/VMS database means that STOP
 MONITOR WITH DELETION will delete your own process.  The equivalent
 RMU/MONITOR STOP /ABORT=DELPRC command does not pose this problem.

 If you do not enter any argument, the default is to let active users
 complete their database activity up to the FINISH statement.  An
 active user is defined as any user who is attached to the database
 and has not yet entered a FINISH or (in RDO) EXIT statement.

 The STOP MONITOR statement requires VMS WORLD privilege only.  No
 additional Rdb/VMS privilege is needed.  Your database administrator
 or system manager should continue to carefully monitor the use of VMS
 privileges on your system.

 Once a STOP MONITOR statement is issued, another STOP MONITOR
 statement for the same Rdb/VMS monitor cannot be issued.  That is, if
 you issue a simple STOP MONITOR statement, you cannot enter a
 subsequent STOP MONITOR WITH EXIT statement to expedite the monitor
 shutdown.

 You must be attached to an Rdb/VMS database before executing a STOP
 MONITOR statement.  This means that STOP MONITOR WITH DELETION will
 delete your own process.

 In the following example, the database administrator needs to shut
 down the Rdb/VMS monitor so that a new version of Rdb/VMS can be
 installed.  The statement that is entered will immediately force all
 active database users off any Rdb/VMS databases on this node (by
 forcing their image to exit).

 RDO> $ REPLY/ALL "As previously announced, beginning Rdb/VMS"
 RDO> $ REPLY/ALL "installation in 1 hour. Please complete work"
 RDO> $ REPLY/ALL "with PERS before then. All databases should be"
 RDO> $ REPLY/ALL "backed up (as discussed)."
 RDO> !
 RDO> ! After waiting one hour:
 RDO> !
 RDO> STOP MONITOR WITH EXIT
 RDO>

 STOP MONITOR ────┬───────────────────>───────────┬──────────────>
                  │                               │
                  └───> 
W
I
T
H ────┬───> 
E
X
I
T ──────┤
                                 │                │
                                 └───> 
D
E
L
E
T
I
O
N ──┘

Additional information available:

WITH_EXITWITH_DELETION

 Immediately forces all active database users off any Rdb/VMS
 databases by forcing their images to exit.

 Deletes all processes that were actively using Rdb/VMS databases on
 the node.