Troubleshooting data for event processing problems

CICS® MustGather for event processing problems

If you have event processing problems, see Event processing problem determination procedures to collect documentation that is listed for your problem before contacting IBM® Support.

To complement the documentation, use the following guidelines:

Required data:
  1. Details of the event bindings and EP adapters that are used to capture and emit the events. These can be exported from the Event Binding Editor within CICS Explorer® or Rational® Developer for z Systems® and sent to IBM as files.
  2. The version and release of any IBM product that is used to consume the events, such as IBM Operational Decision Manager, IBM Business Monitor, or Cognos® Real-Time Monitoring.
  3. Relevant messages from the CICS console log. These messages typically include DFHEPnnnn messages and DFHECnnnn messages. For more information, see CICS messages.
  4. The CICS internal trace that is included in the MVS™ system dump when tracing is active. Ensure that the internal trace table size is big enough to contain sufficient data for diagnosis; for example, you can use a table size of 20480K. When possible, turn on level 2 tracing for the EC and EP components and level 1 tracing for all other CICS components. If this is not possible, turn on a minimum of level 1 tracing for the EC, EP, EI, SM, PG, and RL components. For more information, see Using trace for CICS problem determination on z/OS®.
  5. The MVS system dump that is taken when the problem occurs. The way that you get the dump depends on whether or not you get a message, transaction abend, or no output when the problem occurs. For more information, see Using dumps for CICS problem determination on z/OS.
  6. If you are unable to get a system dump, get a CICS auxiliary trace that leads up to the error. If possible, turn on level 2 tracing for the EC and EP components, and level 1 tracing for all other CICS components. If this is not possible, turn on a minimum of level 1 tracing for the EC, EP, EI, SM, PG, and RL components. If the problem involves System Events, also turn on level 1 tracing for FC, XM, and RA.
  7. If you use the SIGNAL EVENT command from within an application program, take a copy of the source code for the program that you added this code to in order to emit an event.