Troubleshooting data for IP interconnectivity (IPIC) problems

CICS® MustGather for IP interconnectivity (IPIC) problems

Gather the following diagnostic information before contacting the CICS support team to troubleshoot your IPIC problems.

Required data:
  1. The CICS message log that includes DFHISnnnn messages. If you have problems with connecting or have a failure when you run a transaction, the console and CISO transient data queue usually have messages. If the other region is also CICS, make sure that you have the message log from that region too. For more information, see CICS messages.
  2. The MVS™ system dump that is taken at the point of failure. If you can re-create the problem, take a dump or add the pertinent DFHISxxxx message to the dump table. If you cannot determine which side of the connection causes the problem, dump both regions. For more information, see Using dumps for CICS problem determination on z/OS®.
  3. The CICS internal trace, which runs within CICS regions that participate in the conversation. Ensure that the internal trace table size is big enough to contain sufficient data for diagnosis; for example, you can use a table size of 20480K. Also, turn on standard level 1 tracing for all components and level 1-2 for the IS, WB, and SO components. For more information, see Using CICS trace for problem determination.
Optional data:
  1. If you can re-create the problem, the CICS auxiliary trace might be useful. Ensure that you run the trace on all the CICS regions that are involved in the IPIC problem.
  2. If you want to see all of the trace entries in one file, you can use the GTF Trace. The GTF Trace is useful when the CICS regions are on different MVS regions. You can write the trace to a GTF trace data set on each MVS, and then merge the files to see the flow of trace in the connected regions. If the CICS regions are in a single MVS, you can write all the trace to a single GTF trace data set.
  3. The CICS transaction dump that is taken at the point of failure.