Diagnostic data

To diagnose problems with IP CICS® Sockets, some or all of the following data might be required:
  • Message logs
    • System log
    • Message log at the transient-data destination specified by the ERRORTD IP CICS Sockets TYPE=CICS configuration option
  • CICS external-trace data set (auxtrace)
    Tip: Using the CICS Trace Control Facility transaction, CETR, ensure the following CICS trace flags are set to obtain the CICS auxiliary trace:
    • Set the CICS Master User Trace Flag to the value of ON to generate IP CICS Sockets CICS trace records
    • Set the Master System Trace Flag to the value of ON to generate CICS trace records
    • Set the AP component trace level to the value of 1
    Rule: Ensure that CICS tracing is enabled for the IP CICS Socket Interface. If the IP CICS Sockets TYPE=CICS TRACE configuration option is NO then no IP CICS Sockets CICS tracing occurs. Either change the configuration option to enable IP CICS Sockets CICS tracing and then stop and restart the IP CICS Socket Interface or dynamically enable the CICS trace by using the EZAO,START,TRACE command or with the EZAO,SET,CICS transaction specifying TRACE=YES.
  • Component trace
    • Engine
    • Physical file system (PFS)
    • Socket
    • Socket (SOCKAPI)
    • Transmission control protocol (TCP)
  • Dumps
    • CICS address dump, if captured.
      Guideline: Ensure the following CICS environment before recreating a problem and taking a dump:
      • The CICS internal trace is started
      • The Master System trace flag and Master User trace flag is on
      • Standard trace level 1-2 set for the AP component
      • IP CICS Sockets CICS tracing is enabled
    • Supervisor Call (SVC) dump. SVC dumps are also known as console dumps or system dumps.
      Guideline: For hangs and loops, request an SVC dump of CICS and TCP/IP.
  • NETSTAT SOCKET output
  • NETSTAT CONN output
Parent topic: Diagnosing problems with IP CICS sockets