Collect troubleshooting data for a problem with SupportPac CB11: CICS Events for WBE

Resolving The Problem

Collect this MustGather data before contacting IBM Support:

• Collecting general information for all problems
• Collecting data for problems with SupportPac CB11
• 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 CICS Transaction Server for z/OS being used.
  
  
• Version and release of IBM WebSphere Business Events being used.
  
  
• Any relevant messages from the CICS console log.
  
  
• CICS internal trace that is included in the MVS system dump when tracing is active. The CB11 SupportPac program issues user trace entries to assist in diagnosing problems. Therefore, enable user trace by either setting the system initialization table (SIT) parameter USERTR=ON (the default) or using transaction CETR to turn the "Master User Trace Flag" ON.
  
  If possible turn on level 1 tracing for all CICS components. If this is not possible, turn on a minimum of level 1 trace for EI, SM, PG, and RI components. Also, set the internal trace table size to be at least 10240K.
  
  
• MVS system dump taken at the point that the error occurs. If you are receiving a transaction abend at the time of the error, you can enter CEMT SET TRD(xxxx) SYS MAX(1) ADD where xxxx is the transaction abend code to request a system dump. If you are receiving CICS message at the time of the error, you can enter CEMT SET SYD(xxxxx) SYS MAX(1) ADD where xxxxx is the CICS message without the DFH to request a system dump. Otherwise, you can request a dump after you see the error using CEMT PERFORM DUMP or CEMT PERFORM SNAP.
  
  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, user trace should be set on and level 1 tracing should be set on for at least EI, SM, PG, and RI components.

• If possible, a copy of the source code for the program that you added code to in order to invoke the SupportPac program.

Back to top

Troubleshooting hints and tips

• 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.
  
  

• WebSphere Business Events
• SupportPac CB11: CICS Events for WBE

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