/[NO]CUMULATIVE

   Controls whether or not successive ALLOW commands are cumulative.

   /NOCUMULATIVE causes all prior ALLOW information to be erased, via
   an implicit DISALLOW, before the current ALLOW command is executed.

    Example:  $ PEEK/ALLOW/NOCUMULATIVE J_DOE

   The above command erases any and all existing ALLOW permissions
   before granting permission to J_DOE to watch you.

   The default value for this qualifier is taken from the logical
   USER$CUMULATIVE, usually defined by PEEK_DEFAULTS.COM.

   For /CUMULATIVE, the current qualifier value for /FIRST controls
   whether the current ALLOW defition is added at the beginning or
   at the end of any previously-defined ALLOW information.

   For /NOCUMULATIVE, the current value for the qualifer /KEYS_ERASE
   controls whether or not hot-key definitions previously defined via
   ALLOW commands are also erased as part of the implicit DISALLOW.

   Note that earlier versions of Peek/Spy did not have the /CUMULATIVE
   qualifier. The value for the ALLOW subcommand in these earlier
   versions was always /NOCUMULATIVE.