When you enable your database to save key events, an additional database process is created to handle the responsibility. This background database process periodically scans your database log file, creating records of the key events in the _KeyEvt table. When successfully started, the key event process writes messages to your log file similar to the following:

[2006/04/06@10:52:58.578-0400] P-6450       T-1     I KEVTRDR 5: (13658) 
Starting the Save Key Events daemon.
[2006/04/06@10:52:58.578-0400] P-6450       T-1     I KEVTRDR 5: (2518)  
Started.

The key event process is also visible in PROMON. The following example shows User Control output from a database enabled to save key events:

User Control:
Usr Name     Type Wait      Area   Dbkey     Trans    PID  Sem Srv   Login  Time
  0 docdemo  BROK  --         0        0         0  11117   0   0 04/07/06 13:50
  5 docdemo  MON   --         0        0         0  11220   2   0 04/07/06 13:50
  6          KERD  --         0        0         0  11235   3   0 04/07/06 13:50
RETURN - repeat, U - continue uninterrupted, Q - quit:

The new process type, KERD, represents the key event process.