Collect troubleshooting data for an Event processing problem in CICS TS

Resolving The Problem

For the most up-to-date documentation, refer to Collecting CICS troubleshooting data (MustGather) for IBM Support in the CICS TS documentation. You will find the General information you should gather for every type of problem followed by the Component-specific information which includes Troubleshooting data for Event processing problems.

The following is the original MustGather information:

• Collecting general information for all problems
• Collecting data for CICS Event processing problems
• Troubleshooting hints and tips
• Exchanging data with IBM Support


• Collect troubleshooting data for CICS products - Read first

Collecting general information for all problems

If you have already contacted IBM Support, you can continue on to the component-specific MustGather information. Otherwise, go to Collect troubleshooting data for CICS products - Read first.

Back to top

• Version and release of any IBM product used to consume the events, such as IBM WebSphere Business Events or IBM Business Monitor.
  
  
• Any relevant messages from the CICS console log. These will typically include DFHEPnnnn messages and DFHECnnnn messages.

• CICS internal trace that is included in the MVS system dump when tracing is active. If possible turn on level 2 trace for the EC and EP components, and level 1 tracing for all CICS components. If this is not possible, turn on a minimum of level 1 trace for EC, EP, EI, SM, PG, and RL components. If the problem involves System Events also turn on level 1 trace for FC, XM, and RA. Set the internal trace table size to be at least 10240K.

• MVS system dump taken at the point that the problem occurs. The way you get the dump will depend on whether or not you are getting a message, transaction abend, or no output when the problem occurs. See the instructions under MVS system dump for details.
  
  If you are unable to get a system dump, a CICS auxiliary trace leading up to the error will be sufficient. As with CICS internal trace, turn on level 2 tracing for the EC and EP components, and level 1 tracing for all CICS components. If this is not possible, turn on a minimum of level 1 trace for EC, EP, EI, SM, PG, and RL components. If the problem involves System Events also turn on level 1 trace for FC, XM, and RA.

• If using EXEC CICS SIGNAL EVENT from within an application program, a copy of the source code for the program that you added this code to in order to emit an event.

Back to top

Troubleshooting hints and tips

• Review the logs and dumps generated at the point of failure.
• Search the CICS support site for known problems using symptoms like the message number and error codes.
• If you find a fixing PTF, see Ordering CICS products and maintenance for the options that are available to order CICS maintenance.
• Gather the documentation and work with the CICS support team to resolve your problem.
• The sample custom EP adapter can be useful in problem determination as a simple event consumer.
  
  

• WebSphere Business Events
• Event Manager trace points
• Event processing domain trace points
• ECSS Event Capture Control blocks *LUA (CICS TS V4.1)

1. See Exchanging information with IBM Technical Support for FTP and email instructions using the IBM Enhanced Customer Data Repository (ECuRep).
   
2. Go to the Service Request page to open or update a problem. If you have a SoftwareXcel enterprise edition for zSeries contract, you can also ask a non-defect installation and usage questions.
   
   Note: Always update your Service Request (problem record) to indicate that data has been sent.

Back to top