Unexpected events captured
Work out why more events than expected have been received by an event consumer.
- One possibility to bear in mind during the investigation is that the events might have been captured correctly but routed to the wrong adapter, event consumer, or both.
- Obtain the Event Processing and CAPTURESPEC statistics. Check the number of events processed by each EP adapter to see which has received more than expected. When more than one custom adapter is in use, use the CEMT INQUIRE PROGRAM command to determine how many events were processed by each adapter and which one received too many events.
- Obtain a dump formatted for EC and EP. Check the =ECEVB: lines in the Event Binding Summary to discover which event bindings and capture specifications are sending events to the adapter. For more details about the adapter, for example, adapter type, transaction ID and so on, see the Event Processing Adapters summary in the EP section of the dump.
- Obtain a level 1 & 2 trace for EI and EC components. Search the trace for ECEC EVENT - CAPTURING_EVENT CAPTURESPEC(xxxx where xxxx is the required CAPTURESPEC name. Each occurrence in the trace represents an event captured because of that CAPTURESPEC. Examine the preceding trace entries with ECEC EVENT - PREDICATE_TRUE. These entries explain why the event filter was passed and the event captured.