Collect troubleshooting data for CICS-MQ adapter or CICS-MQ bridge problems in CICS TS for z/OS

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 CICS-MQ adapter or bridge problems.

The following is the original MustGather information:

• Collecting general information for all problems
• Collecting data for CICS-MQ adapter or CICS-MQ bridge problems
• Troubleshooting hints and tips
• Exchanging data with IBM Support


• Collect troubleshooting data for CICS products - Read first

Back to top

• CICS message log and the MVS system log (SYSLOG) containing the messages leading up to the problem.
  
  
• MVS system dump taken at the point of failure. If you are receiving an abend and system dumping is permitted for the dump code, a system dump will be taken when the error is detected. Otherwise, you can request a dump by following the instructions in the first step under MVS system dump.
  
  
• CICS internal trace that is included in the MVS system dump when tracing is active. The trace should be at least 10240K and when possible level 1 tracing should be on for all CICS components.
  
  Non-exception trace entries for the MQ adapter are controlled by Resource Manager Interface (RI) and Resource Manager Adapter (RA) level 1 and level 2 tracing. Standard trace is usually sufficient but level 1-2 tracing for the RI and RA components could expedite problem resolution. Bridge facility (BR) standard trace is usually sufficient for a CICS MQ bridge problem but level 1-2 tracing for the BR component could expedite problem resolution.

• The WebSphere MQ for z/OS MSTR job log containing the messages leading up to the problem. The job log is named xxxxMSTR where xxxx is the WebSphere MQ subsystem identifier (ssid).
  
  
• Locrec report from SYS1.LOGREC data set (JCL to get software LOGREC report).
  
  
• If you need a larger trace consider using CICS auxiliary trace or GTF Trace in combination with the MVS system dump. Use the same level of tracing documented above for CICS internal trace.

Back to top

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

• Troubleshooting the CICS-WebSphere MQ adapter
• Troubleshooting the CICS-WebSphere MQ bridge
• DFHMQnnnn messages
• CICS WebSphere MQ trace points

Back to top

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