Selecting a trace

Base your choice of traces on the criteria given in Table 1.
Table 1. Selecting a trace
If the problem is... Then use this type of trace or command Trace output location
Load balancing using the z/OS® Load Balancing Advisor

See Diagnosing problems with the z/OS Load Balancing Advisor for more information.

Log file

syslogd
Network connectivity

See Diagnosing network connectivity problems for detailed information.

Ping, Netstat ARP/-R

For information about Ping, see Using the Ping command. For information about Netstat ARP/-R, see Netstat ARP/-R.

Not applicable
Packet trace

See TCP/IP services traces and IPCS support for detailed information about packet trace.

CTRACE managed data set
Dynamic VIPA or Sysplex Distributor

See Diagnosing dynamic VIPA and sysplex problems for detailed information.

Component Trace (SYSTCPIP) XCF option TCP/IP address space or external writer
TCP/IP socket application

See Socket API traces for detailed information.

Component Trace (SYSTCPIP) SOCKAPI option TCP/IP address space or external writer
LPR client

See LPR client traces for detailed information.

LPR command with the TRACE option sysout
LPD server

See LPD server traces for detailed information.

See LPD server traces for ways to activate traces. SYSPRINT
z/OS UNIX FTP server

See Diagnosing File Transfer Protocol (FTP) problems for detailed information.

z/OS UNIX FTP server trace Server traces appear on the console if syslogd is not started. If it is started, traces appear in the file designated in the syslog.conf file. See z/OS Communications Server: IP Configuration Guide for detailed information about syslogd.
z/OS UNIX Telnet

See Diagnosing z/OS UNIX Telnet daemon (otelnetd) problems, for detailed information.

z/OS UNIX Telnet traces syslogd
TN3270E Telnet server

See Diagnosing Telnet problems for detailed information.

Telnet traces Telnet address space or external writer
SMTP

See SMTP RESOLVER trace for detailed information.

Resolver Trace Job log output
Popper

See Diagnosing z/OS UNIX sendmail and popper problems for detailed information.

Popper Messages syslogd
SNALINK LU0

See Diagnosing SNALINK LU0 problems for detailed information.

IP Packet Trace CTRACE managed data set
Debug Trace SNALINK LU0 address space
SNALINK LU6.2

See Diagnosing SNALINK LU6.2 problems for detailed information.

TRACE DETAIL ALL SYSPRINT
IP Packet Trace CTRACE managed data set
TCP/IP Internal Trace CTRACE managed data set CTRACE managed data set
VTAM® Buffer Trace GTF managed data set, see z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for detailed information.
Dynamic domain name system (DDNS) Error messages syslogd
Resolver Trace Job log output
TCP/IP component trace CTRACE managed data set
z/OS UNIX REXEC

See Diagnosing z/OS UNIX REXEC, RSH, REXECD, and RSHD problems.

z/OS UNIX REXEC debug trace syslogd
z/OS UNIX REXECD

See Diagnosing z/OS UNIX REXEC, RSH, REXECD, and RSHD problems.

z/OS UNIX REXECD debug trace syslogd
z/OS UNIX RSHD

See Diagnosing z/OS UNIX REXEC, RSH, REXECD, and RSHD problems.

z/OS UNIX RSHD debug trace syslogd
X Window and Motif

See Diagnosing X Window System and Motif problems for detailed information.

XWTRACE and XWTRACEC

(environment variables)

stderr
SNMP

See Diagnosing Simple Network Management Protocol (SNMP) problems for detailed information.

Manager Traces Console (snmp) or SYSPRINT (NetView® SNMP)
  • SNMP Agent Traces
  • TCP/IP Subagent Traces
  • OMPROUTE Subagent Traces
  • Network SLAPM2 Subagent Traces
  • TN3270E Telnet Subagent Traces
  • TRAPFWD Traces
syslogd
Policy Agent

See Diagnosing Policy Agent problems for detailed information.

Log file See z/OS Communications Server: IP Configuration Guide for detailed information.
RSVP Agent

See Diagnosing RSVP agent problems for detailed information.

Log file See z/OS Communications Server: IP Configuration Guide for detailed information.
Traffic Regulator Management Daemon (TRMD)

See Diagnosing intrusion detection problems for detailed information.

Log file syslogd
IKE daemon

See Diagnosing IKE daemon problems.

Component trace

For detailed information about IKE daemon component trace, see TCP/IP services component trace for the IKE daemon.

CTRACE managed data set

Log file

For detailed information about obtaining IKE daemon debug log information, see Obtaining syslog debug information for the IKE daemon.

syslogd
Network security services (NSS) server

See Diagnosing network security services (NSS) server problems.

Component trace

For detailed information about network security services (NSS) server component trace, see TCP/IP services component trace for the network security services (NSS) server.

CTRACE managed data set

Log file

For detailed information about obtaining network security services (NSS) server debug log information, see Obtaining syslog debug information for the network security service server.

syslogd
OMPROUTE

See Diagnosing OMPROUTE problems.

Component trace

For detailed information about OMPROUTE Component Trace, see TCP/IP services component trace for OMPROUTE.

CTRACE managed data set

OMPROUTE Trace

For detailed information, see OMPROUTE traces and debug information.

stdout
NCPROUTE

See Diagnosing NCPROUTE problems for detailed information.

NCPROUTE Traces SYSPRINT
X.25 NPSI

See Diagnosing X.25 NPSI problems for detailed information.

Server activity log SYSPRINT
IMS™

See Diagnosing IMS problems for detailed information.

IP Packet Trace CTRACE managed data set
TCP/IP Internal Trace CTRACE managed data set
IMS Trace For more information, see the IMS knowledge center at http://www-01.ibm.com/support/knowledgecenter/SSEPH2/welcome.
CICS®

See Diagnosing problems with IP CICS sockets for detailed information.

CICS external trace data set (auxtrace) For more information, see the CICS knowledge center at http://www-01.ibm.com/software/htp/cics/library/.
TCP/IP Internal trace CTRACE managed data set
Express® Logon

See Diagnosing problems with Express Logon for detailed information.

Log file syslogd
Resolver

See Diagnosing resolver problems for detailed information.

Trace Resolver SYSPRINT or stdout
Resolver Internal trace CTRACE managed data set

You can now perform the steps for the decision you have made.