Troubleshooting data for errors or incorrect output of IBM Explorer for z/OS or CICS Explorer

CICS® MustGather for Explorer errors or incorrect output

If you receive incorrect output, an error in the log, or a pop-up error message from the CICS Explorer®, IBM® Explorer for z/OS®, or any of the CICS Tools plug-ins, gather the following diagnostic information before contacting the CICS support team.

Required data:

1. Use the Explorer-integrated capability to create a zip file that contains service data:
   1. Select Explorer > Trace > Collect Service Data from the Explorer menu.
   2. Select where to save the .zip file.

   For more instructions, see Preparing error data for IBM service in the CICS Explorer product documentation.

2. If you think the Explorer shows an incorrect output, create screen captures of the Explorer screen as image files (.bmp or .jpg). These images might provide useful information for IBM Support.
3. When you get an error, gather the following additional data based on the type of the connection you use:
   • For a CICSPlex® SM connection, the complete job log (including CICS TDQ output) of the WUI server and the CMAS to which the WUI server connects.

     If you receive a bad response from the CICS management client interface (CMCI) or the CICSPlex SM application programming interface (API), for example FAILED or EXCEPTION response, collect the unformatted auxiliary trace data sets from the WUI server and the CMAS to which the WUI server connects.

   • For a single server (SMSS) version in a stand-alone CICS region, the complete job log (including TDQ output).
   • For other types of connections, the required documentation varies. For example, for CICS Performance Analyzer, a copy of the input file that is used on the request is useful.