Using the IMS Connect Extensions trace
Tracing events are additional event records produced by IMS Connect Extensions when tracing is activated. Use the IMS Connect Extensions ISPF dialog to start and stop tracing for an active IMS Connect system.
- Use the Status Monitor in IMS Connect Extensions Operations Console for z/OS Explorer. For more information, see Using conditional trace.
- Use the QUERY commands and the TRACE command in the IMS Connect Extensions host command environment for REXX to query, start, and stop tracing. See members CEXRXC11 and CEXRXC45 in the SCEXSAMP library for details.
In addition to logging IMS Connect events, IMS Connect Extensions can optionally write trace event records that expose the raw messages entering and exiting IMS Connect. These messages include the IMS request message (or IRM) from the client, the response to the client, and the OTMA messages that IMS Connect exchanges with IMS. These trace event records are useful for diagnosing problems such as malformed messages. Optionally, IMS Connect Extensions can include application data in these trace event records, such as the application data that typically follows an IMS request message.
For a list of the IMS Connect trace records, see IMS Connect Extensions trace records. The current tracing status and tracing level are included in the X'00' event record.Starting the trace:
Stopping the trace: