The following notes apply to using the event facility:

• If the event code sent from the source system is not a code specified in the import environment definition or is not -1 (connection-based termination event), the target Datareplicator recognizes that an event is being reported and outputs a message, but it continues the import processing that was underway before the event was notified (the event is ignored).
• If import processing is already underway, Datareplicator ignores a restart event (transaction-based import restart event or table-based import restart event), if detected.
• If you terminate Datareplicator before processing a received restart event (transaction-based import restart event or table-based import restart event), information about the received restart event is discarded.
• The import definition server process monitors events at an interval of one second and can manage up to 16 events concurrently. If more than 16 events are issued within one second, the additional event codes will not be displayed in messages. When you use event codes in messages output by the import definition server process, be sure that 16 events per second is not exceeded.