If a problem occurs on an ISC link that uses TCP/IP, you
might need to collect diagnostic information from IMS, the Structure Call Interface (SCI) component
of the IMS Common Service Layer
(CSL), IMS Connect, TCP/IP, and IBM® CICS® Transaction Server for z/OS®.
Prerequisite: Review error messages
that were issued by IMS, the
SCI, IMS Connect, and CICS around the time of the error
to determine at which point in the ISC link the error might have occurred.
If you can determine that any components are unrelated to the error,
you might not need to collect information about that component.
To collect the data that is needed to diagnose a problem
on an ISC link that uses TCP/IP:
- For IMS, the information
that you can collect includes:
- The IMS system console
sheet
- The IMS job log
- The z/OS system log
(SYSLOG)
- A dump of the IMS control
region
- A DC trace
- For SCI, the information that you can collect includes:
- An SCI region dump
- The z/OS SYSLOG from
the logical partition in which SCI is running.
- A z/OS SVC dump of
the CSL address spaces
- For IMS Connect, the
information that you can collect includes:
- A dump of the IMS Connect
address space
- The IMS Connect job log
- The z/OS SYSLOG
- Output from the IMS Connect
Recorder Trace facility
- 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.
- For CICS, refer
to the CICS documentation for
current information about collecting diagnostic information. Information
that might be helpful to collect includes:
- The CICS system console
sheet
- The CICS job log
- The CICS message log
including any DFHISnnnn messages
- A z/OS system dump
taken at the point of failure
- A CICS internal trace