Collecting data about IMS Connect problems

If a problem occurs during IMS Connect execution, you need to collect logs, data sets, and dumps to determine the source of the problem.

For almost all problems that might occur during IMS Connect execution, you can take the following action to collect the data that is needed to diagnose the problem:

Create a dump of the IMS Connect address space.
Save the IMS Connect joblog, which contains only IMS Connect messages. IMS Connect messages are also written to the MVS system log (SYSLOG), but the IMS Connect messages can be difficult to find in the SYSLOG, because of the other z/OS® subsystem messages that the SYSLOG contains.
Save the MVS SYSLOG. The SYSLOG is useful for seeing what messages other subsystems issued before and after the IMS Connect messages were issued, because the MVS SYSLOG contains messages from all z/OS subsystems, including TCP/IP, IMS, and IMS Connect.
Turn on the IMS Connect Recorder Trace facility and attempt to re-create the problem.

In addition to collecting data about IMS Connect, you might need to collect data about other components or products if they appear to be related to the problem in some way. For example:

If the problem appears to be network related, you might also need to initiate a TCP/IP packet trace to trace the IP packets flowing to and from a TCP/IP stack on the z/OS Communications Server. For more information about initiating packet traces, see z/OS Communications Server IP Diagnosis Guide.
If the problem is related to IMS Connect support for an IMS TM system, where the connections to IMS are through OTMA, you might also need to collect data about the IMS system.
If the problem is related to IMS Connect support for an IMS DB system, where the connections to IMS are through an instance of the Open Database Manager (ODBM), which runs in its own address space as a component of the IMS Common Service Layer (CSL), you might also need to collect data about both the IMS system and any ODBM instance that might be associated with the problem.
If the problem is related to two-phase-commit processing, you might also need to collect data related to z/OS Resource Recovery Services.