CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

3.5 Problem determination
3.5.1 Tips and utilities
In this section, we document information we learned while configuring this
scenario, as well as further information on problem determination and tracing.
In this section, you will find useful commands and utilities for debugging any
problems with your configuration. You will also find some additional information
about topics discussed in this chapter.
Logs
For problem determination at the client side, it is best to check the CICSCLI.LOG
under the /bin directory for error messages. If this does not give enough
information, you should start the CICS TG connection with trace as shown in
3.5.2, “Tracing” on page 61.
For problem determination with APPC connections into CICS TS, refer to the
following logs:
► z/OS system log (SDSF.LOG) for VTAM information messages
► CICS console and CSMT logs for CICS messages
Windows TCP/IP status
To check the status of TCP/IP as used by AnyNet on the workstation, you can
issue the netstat /a /n command to view socket usage as shown in
Example 3-7.
Example 3-7 Client side netstat information
C:\>netstat /a /n
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:397 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1039 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1073 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1161 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1186 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1187 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9495 0.0.0.0:0 LISTENING
TCP 9.1.38.39:139 0.0.0.0:0 LISTENING
TCP 9.1.38.39:397 9.12.6.6:1263 ESTABLISHED
TCP 9.1.38.39:1033 0.0.0.0:0 LISTENING
TCP 9.1.38.39:1072 0.0.0.0:0 LISTENING
Chapter 3. TCP62 connections to CICS 55