Troubleshooting the CICS-WebSphere MQ adapter

If you are having problems with the CICS-WebSphere® MQ adapter, CICS provides a range of information to help you diagnose the cause.

Depending on the information that you require and the environment in which you are currently working, you can use CEMT or EXEC CICS® INQUIRE commands, the CICS-WebSphere MQ adapter control panels, the CKQC DISPLAY command, or CICSPlex® SM to display information about the CICS-WebSphere MQ connection. For information about these different methods, see Displaying information about CICS-MQ connections.

The CKQC transaction (from the CICS-WebSphere MQ adapter control panels) can display details of individual tasks using the connection to WebSphere MQ, and the state that they are in, such as a GET WAIT. Displaying tasks that are using the CICS-MQ connection explains how to display this information.

The CICS execution diagnostic facility (CEDF) traps entry to and exit from the CICS-WebSphere MQ adapter for each MQI call, as well as trapping calls to all CICS API services.

The CICS-WebSphere MQ adapter uses AP domain trace points in the range A000 to A1FF, and the trace entries are written to standard CICS trace destinations. The contents of trace points issued by the CICS-WebSphere MQ adapter are documented in CICS WebSphere MQ trace points. Exception trace entries are unconditionally produced for error conditions. Non-exception trace entries are controlled by RI (Resource Manager Interface) and RA (Resource Manager Adapter) Level 1 and Level 2 tracing. For more information about CICS tracing, see CETR - trace control.