Captured events missing

Events have been captured, but not emitted, and they have not been received at the point where they were expected.

  • Obtain the event processing statistics and look to see if any events have been lost by the dispatcher or adapters. When the events lost reason is config, examine the CICS message log for explanations. Possible reasons include incorrect adapter transaction ID and incorrect or revoked password. Correct these problems appropriately. When the events lost reason is other, examine the CICS message log for explanations. Possible reasons include CICS short on storage. Take the appropriate action. When no explanatory message is found, check the CICS exception trace entries for an explanation.
  • Check the statistics for transactional events that have been discarded because of transactions being backed out. Check if the number matches the number of missing events.
  • Check the number of times the adapter has been started using the CEMT INQUIRE PROGRAM command.
    • When the adapter has not been started for all the events, the event has been lost by the EP dispatcher.
    • When the adapter has been started the required number of times the event might have been lost by the adapter, by the transport to the event consumer, or by the event consumer.
  • When event processing is stopped, or a CICS immediate shutdown is performed, event capture is stopped and in some cases captured events are not emitted.
  • DFHECnnnn messages and AECx abend codes can help you diagnose problems with your EP adapters.
  • If your adapter transaction is subject to scheduling constraints, then an AKCC abend for the adapter transaction could indicate the cause of your missing event.