Troubleshooting
Problem
You want to know how to collect relevant troubleshooting data to help the IBM Support team fix an error in IBM CICS Explorer. You are receiving incorrect output, an error in a log, or an error in a pop-up window from CICS Explorer on Microsoft Windows or Linux. The problem might be with one of the CICS Tools plug-ins for CICS Explorer. You would like to know what documentation you must collect (MustGather) so that the IBM Support team can diagnose your problem. If you gather this documentation before contacting Support, then it will expedite the troubleshooting process and might save you time.
Symptom
CICS Explorer or one of the CICS Tools plug-ins for CICS Explorer is experiencing one of the following types of problem:
- Incorrect output
- Error in pop-up window
- Errors in the log
- Unable to connect to CICS system
Resolving The Problem
For the most up-to-date documentation, refer to Collecting CICS troubleshooting data (CICS 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 the z/OS or CICS Explorer when errors or incorrect output.
The following is the original MustGather information:
Collect this MustGather data before contacting IBM Support:
- Collecting general information for all problems
- Collecting data for an Explorer error or incorrect output
- Troubleshooting hints and tips
- Exchanging data with IBM Support
- Collect troubleshooting data (MustGather) 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 (MustGather) for CICS products - Read first.
Collecting data for an Explorer error or incorrect output
Before calling IBM support, gather the following documentation if you are receiving incorrect output, an error in the log, or an error in a pop-up window from the CICS Explorer or any of the CICS Tools plug-ins for CICS Explorer.
Required (MustGather) data:
- Use the CICS Explorer integrated capability to create a zip file containing service data (if possible directly after recreating the issue):
- In the CICS SM perspective, select File > Trace > Flush.
- Select File > Trace > Collect Service Data.
- Select where to save the .zip file.
- This procedure is explained in detail in the Help that accompanies CICS Explorer, under "Preparing error data for IBM service".
- If you think CICS Explorer is showing an incorrect output, images of the CICS Explorer screen are useful. These images might provide useful information for IBM Support. Do the following to create the screen shots as image files (bmp or jpg):
On Microsoft Windows:- Use the print screen or alt-print screen keys to create an image on the system clipboard.
- Open a graphics application (for example, Microsoft Paint) and select Edit > Paste to copy the clipboard into the application.
- Select File > Save as to create the file as a bmp or jpg.
- Use the print screen or alt-print screen keys to create an image on the system clipboard.
- When getting an error, you should gather the following additional data which is dependent on the type of 'connection' you are using:
- For a CICSPlex SM connection, the complete joblog (including CICS TDQ output) of the Web User Interface (WUI) Server and CMAS that the WUI Server connects.
- In the case of a bad response from the CICS management client interface (CMCI) or the CICSPlex SM application programming interface (API), for example FAILED or EXCEPTION response, the unformatted auxiliary trace data sets from the WUI Server and the CMAS that the WUI Server connects.
- For a single server (SMSS) version in a stand-alone CICS region, the complete joblog (including TDQ output).
- For the other types of connections, the needed documentation could vary. For example, for CICS Performance Analyzer for z/OS (CICS PA), a copy of the input file used on the request would be useful.
Troubleshooting hints and tips
Diagnostic tips:
- Search the IBM support site for known problems using symptoms like the message number and error codes.
- Search the CICS Explorer Help. This is where you will find CICS Explorer messages. They are not included in the CICS documentation. For further information see Finding the CICS Explorer messages that are prefixed with CNX.
- If you find a fix, see Ordering maintenance for IBM CICS Explorer and CICS Explorer plug-ins for the options that are available for ordering CICS Explorer maintenance.
- Gather the documentation and work with the CICS Support team to resolve your problem.
Learn more about CICS Explorer
Exchanging data with IBM Support
- See Exchanging diagnostic information with IBM Technical Support for problem determination for FTP and email instructions using the IBM Enhanced Customer Data Repository (ECuRep).
- Go to the IBM Support site to open or update a case for a problem. If you have a Preferred Care option for IBM Z that includes Support access for Q&A, 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.
If you need to speak to an IBM technical support representative call your country representative. If you need to speak to an IBM technical support representative in the US, call 1-800-IBM-SERV.
Product Synonym
CICS/TS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
15 June 2022
UID
swg21385861