/TOGGLE_INPUT = "hot-key-defintion"
   /NOTOGGLE_INPUT

   Defines a hot-key sequence for use while being watched which, when
   pressed, switches control of the user's keyboard between the
   watcher and the user.

   If a watcher has taken control of the user's keyboard with PEEK,
   then when this hot-key is pressed by the user, it returns
   control of his keyboard back to him/her.

   The default value for this hot-key is taken from the logical
   USER$TOGGLE_INPUT, usually defined by PEEK_DFAULTS.COM.

   If SIMULTANEOUS_INPUT is in effect, both the watcher and the user
   will be able to provide input for the user at the same time.
   Pressing the TOGGLE_INPUT hot-key has no effect in this case.

   If this hot-key is NOT defined (either on the command line or
   as a logical name) then the user will not be able to regain
   keyboard control once it has been taken over by a watcher.

     NOTE:  There is a licensing option which will prevent the watcher
     from ever providing input to the user's terminal. This is for use
     in banking and other high-security environments. If the
     TOGGLE_INPUT feature appears not to work at your site, you
     should check to see if your license specifies NOKB_CONTROL. Use
     the $ PEEK/SHOW LICENSE command to check your license options.

   The remainder of this section will assume that SIMULTANEOUS_INPUT
   is not in effect.

   When a watcher first begins watching someone, the watcher is not
   allowed to enter input for the user's process. If he types anything
   (other than one of his defined hot-key sequences) PEEK throws away
   the watcher's input and rings the bell on his terminal to remind
   him that he does not currently have keyboard control.

   The watcher may press his TOGGLE_INPUT hot-key to swap keyboard
   control, taking it away from the user being watched. At this point,
   the bell on the terminal of the user being watched will ring if he
   attempts to type anything other than his defined hot-key sequences.

   The user being watched may then press his own TOGGLE_INPUT hot-key
   sequence to get control of his keyboard back from the watcher.

   For example, J_DOE issues the command:

         $ PEEK/ALLOW/TOGGLE_INPUT="<F10>" USER1

   After this ALLOW command is issued, USER1 can watch J_DOE with PEEK.

   While watching J_DOE, USER1 can press his hot-key to take over
   keyboard control from J_DOE. If J_DOE then tries to type, his
   terminal bell will just ring to inform him that USER1 currently
   has keyboard control.

   J_DOE can then press his F10 key to regain control of his keyboard.

   For a complete description of the syntax used for specifying hot-key
   definitions, see the top-level PEEK Subtopic: Hot-Keys.

   The /TOGGLE_INPUT command qualifier may also be negated. This allows
   one to override a default TOGGLE_INPUT definition which has been
   placed in a logical name table.

   When specified as PEEK/ALLOW/NOTOGGLE_INPUT, this tells PEEK no
   hot-key should be defined to allow the user to toggle input control
   while being watched.

   /NOTOGGLE_INPUT is equivalent to specifying /TOGGLE_INPUT="" (null
   string).

   NOTE: The ALLOW/NOTOGGLE_INPUT qualifier prevents a user who issues
         the command containing it from toggling keyboard input. The
         ALLOW/NOKB_CONTROL qualifier refers to whether an ALLOWed
         watcher may take over control of the keyboard of the user
         being watched.