• Abstract for IP Diagnosis
    • Summary of changes
      • Changes made in z/OS Version 2 Release 1, as updated September 2014
      • Changes made in z/OS Version 2 Release 1, as updated December 2013
      • Summary of changes for z/OS Version 2 Release 1
  • General diagnosis information
    • Overview of diagnosis procedure
      • Steps for diagnosing problems
    • Selecting tools and service aids
      • How do I know which tool or service aid to select?
        • Selecting a dump
        • Selecting a trace
        • Selecting a service aid
      • Overview of available tools and service aids
        • Dumps
        • Traces
        • First Failure Support Technology (FFST)
          • FFST dumps
          • SDUMP
          • Formatting an SDUMP
          • FFST minidump
          • Formatting an FFST minidump
          • Generic alert
          • The symptom string
          • FFST console
        • Display commands
          • DISPLAY TCPIP,,STOR
        • System service aids
      • Methods for submitting documentation
        • Using AMATERSE
          • Starting AMATERSE
      • Using electronic transfer through email attachments
      • Necessary documentation
    • Diagnosing abends, loops, and hangs
      • Analyzing abends
      • Analyzing loops
        • Steps for collecting documentation
      • Steps for analyzing hangs
    • Diagnosing network connectivity problems
      • Overview
      • Communicating through the correct stack
      • Steps for diagnosing problems connecting to a server
      • Steps for verifying server operation
      • Steps for verifying IP routing to a destination when not using policy-based routing
        • Steps for diagnosing problems with IP routing to a destination when using policy-based routing
        • Steps for verifying network interface operation
      • Steps for verifying network access
      • Tools for diagnosing network connectivity problems
        • Using the Ping command
          • Correcting timeout problems
        • Using the Netstat command
          • Netstat HOME/-h
          • Netstat DEVLINKS/-d
          • Netstat ROUTE/-r
          • Netstat ARP/-R
          • Netstat ND/-n
        • Using the DISPLAY TCPIP,,OSAINFO command
        • Using the Traceroute command
        • Using SNMP remote Ping command
      • Documentation for the IBM Support Center
  • Traces and control blocks
    • TCP/IP services traces and IPCS support
      • Component trace
        • Modifying options with the TRACE CT command
          • Modifying with the PARMLIB member
          • Modifying without the PARMLIB member
          • Displaying component trace status
            • Modifying the trace buffer size
          • Stopping a component trace
          • Obtaining component trace data with a dump
            • TCP/IP stack
            • OMPROUTE
            • RESOLVER
            • TELNET
          • Steps for obtaining component trace data with an external writer
          • Tips for using component trace external writer
            • Using a VSAM linear data set
          • Formatting component traces
            • Steps for formatting component traces using IPCS panels
            • Steps for using the CTRACE command
            • Syntax
            • Parameters
            • Keywords
            • Examples of formatting component traces
            • Formatting component traces using a batch job
      • IKE daemon trace (SYSTCPIK)
      • Event trace (SYSTCPIP) for TCP/IP stacks and Telnet
        • Specifying trace options
          • Specifying trace options at initialization
          • Specifying trace options after initialization
        • Additional filters for SYSTCPIP
        • Formatting event trace records for TCP/IP stacks and Telnet
          • Additional fields in CTRACE output
          • SESSION report example
        • Socket API traces
          • Recommended options for the application trace
          • Collecting the SOCKAPI trace option
            • CTRACE PARMLIB member CTIEZBxx
            • TCP/IP start procedure
            • TRACE command
            • External writer
            • Filtering options when recording the trace
            • Monitoring the trace
            • Capturing the trace
          • Formatting the SOCKAPI trace option
          • Reading and interpreting the SOCKAPI trace option
            • A SOCKAPI trace record
            • Examples of SOCKAPI trace records
              • Successful API Call
              • API call fails synchronously
              • API call fails synchronously with parameter not addressable
              • API call fails synchronously with diagnostic reason code
              • Resolver API calls
              • External IOCTL commands
              • API call with an IOV parameter
              • Default INITAPI
              • Default TERMAPI
              • SELECT
              • SELECTEX
              • Token Error
              • Unsolicited event exit
          • Correlating the data trace and packet trace with the SOCKAPI trace
      • Packet trace (SYSTCPDA) for TCP/IP stacks
        • The trace process
        • Supported devices
        • Starting packet trace
        • Modifying options with VARY
        • Formatting packet traces using IPCS
          • OPTIONS syntax
          • OPTIONS keywords
          • Report Examples
            • OPTION
            • SUMMARY
            • EXPORT
            • FORMAT
            • DUMP
            • HPR
            • REASSEMBLY
            • SESSION TCP
            • SESSION UDP
            • SNIFFER
            • STATISTICS
            • STREAM
          • Formatting packet trace using a batch job
      • Data trace (SYSTCPDA) for TCP/IP stacks
        • Starting data trace
        • Displaying data traces
        • Formatting data traces using IPCS
      • Intrusion Detection Services trace (SYSTCPIS)
        • Restrictions
        • CTRACE keywords on SYSTCPIS
        • SYSTCPIS OPTIONS
        • OPTIONS keywords
        • IDS reports
          • OPTION
          • SUMMARY
          • FORMAT
          • DUMP
          • SNIFFER
          • STATISTICS
          • STREAM
      • OSAENTA trace (SYSTCPOT)
        • The OSAENTA trace process
        • Starting OSAENTA trace
          • Modifying options with VARY commands
          • Formatting OSA traces using IPCS
      • Network security services (NSS) server trace (SYSTCPNS)
      • Defense Manager daemon (DMD) trace (SYSTCPDM)
      • OMPROUTE trace (SYSTCPRT)
      • RESOLVER trace (SYSTCPRE)
      • Configuration profile trace
    • IPCS subcommands
      • Types of subcommands
      • TCPIPCS
        • Syntax
        • Parameters
        • Symbols defined
      • TCPIPCS subcommands
        • TCPIPCS API
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS API subcommand
        • TCPIPCS CONFIG
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS CONFIG subcommand
        • TCPIPCS CONNECTION
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS CONNECTION subcommand
        • TCPIPCS COUNTERS
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS COUNTERS subcommand for IP UDP
        • TCPIPCS DUAF
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS DUAF subcommand
        • TCPIPCS DUCB
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS DUCB subcommand
        • TCPIPCS FRCA
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS FRCA subcommand
        • TCPIPCS HASH
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS HASH subcommand
        • TCPIPCS HEADER
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS HEADER subcommand
        • TCPIPCS HELP
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS HELP subcommand
        • TCPIPCS IPSEC
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS IPSEC subcommand
        • TCPIPCS LOCK
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS LOCK subcommand
        • TCPIPCS MAP
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS MAP subcommand
        • TCPIPCS MTABLE
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS MTABLE subcommand
        • TCPIPCS POLICY
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS POLICY subcommand
        • TCPIPCS PROFILE
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS PROFILE subcommand
        • TCPIPCS PROTOCOL
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS PROTOCOL subcommand
        • TCPIPCS RAW
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS RAW subcommand
        • TCPIPCS ROUTE
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS ROUTE subcommand
        • TCPIPCS SOCKET
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS SOCKET subcommand
        • TCPIPCS STATE
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS STATE subcommand
        • TCPIPCS STORAGE
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS STORAGE subcommand
        • TCPIPCS STREAM
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS STREAM subcommand
        • TCPIPCS TCB
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS TCB subcommand
        • TCPIPCS TELNET
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS TELNET subcommand
        • TCPIPCS TIMER
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS TIMER subcommand
        • TCPIPCS TRACE
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS TRACE subcommand
        • TCPIPCS TREE
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS TREE subcommand
        • TCPIPCS TSDB
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS TSDB subcommand
        • TCPIPCS TSDX
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS TSDX subcommand
        • TCPIPCS TSEB
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS TSEB subcommand
        • TCPIPCS TTLS
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS TTLS subcommand
        • TCPIPCS UDP
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS UDP subcommand
        • TCPIPCS VMCF
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS VMCF subcommand
        • TCPIPCS XCF
          • Syntax
          • Parameters
          • Sample output of the TCPIPCS XCF subcommand
      • ERRNO
        • Syntax
        • Parameters
        • Sample output of the ERRNO command
      • ICMPHDR command
        • Syntax
        • Parameters
        • Sample output of the ICMPHDR command
      • IPHDR command
        • Syntax
        • Parameters
        • Sample output of the IPHDR command
      • RESOLVER command
        • Syntax
        • Parameters
        • Sample output of the RESOLVER command
      • SETPRINT command
        • Syntax
        • Parameters
        • Sample output of the SETPRINT command
      • SKMSG command
        • Syntax
        • Parameters
        • Sample output of the SKMSG command
      • TCPHDR command
        • Syntax
        • Parameters
        • Sample output of the TCPHDR command
      • TOD command
        • Syntax
        • Parameters
        • Sample output of the TOD command
      • UDPHDR command
        • Syntax
        • Parameters
        • Sample output of the UDPHDR command
      • Installing TCP/IP IPCS subcommands by using the panel interface
      • Entering TCP/IP IPCS subcommands
        • Steps for entering a TCP/IP IPCS subcommand
        • Step for using the batch option
  • Diagnosing z/OS Communications Server components
    • Diagnosing problems with the z/OS Load Balancing Advisor
      • Diagnostic data
      • Diagnosing Advisor and Agent problems
        • Abends
        • Workload not distributed to a particular application
        • Workload not distributed as expected
        • Advisor or Agent appears to be hung
        • Group names in displays are indecipherable
        • Load balancer connection terminates unexpectedly
        • Agent-Advisor connection terminates unexpectedly
        • Automatic restart manager (ARM) registration failure
      • Debug settings and corresponding syslogd priority levels
    • Diagnosing problems with the automated domain name registration application (ADNR)
      • Diagnostic data
      • Diagnosing ADNR problems
        • Abends
        • ADNR fails to initialize
        • ADNR not communicating with the Global Workload Manager
        • Automatic restart manager (ARM) registration failure
        • ADNR not updating zones in a DNS server
        • DNS name servers managed by ADNR contain incorrect or outdated data
        • Diagnosing unresponsive zones
        • ADNR appears to be hung
        • ADNR connection to the GWM terminates unexpectedly
      • Debug settings
    • Diagnosing IKE daemon problems
      • Overview of diagnosing IKE daemon problems
      • Diagnosing IKE daemon problems
        • Initialization problems
        • Problems establishing security associations
          • Common problems
            • Network security services client problems
          • NAT traversal considerations
          • Abends
      • IKE daemon debug information
        • Obtaining syslog debug information for the IKE daemon
        • Obtaining debug information using PagentSyslogLevel
      • TCP/IP services component trace for the IKE daemon
        • Using CTRACE
          • Enabling CTRACE at IKE daemon startup
          • Steps for enabling the CTRACE at IKE daemon startup
          • Steps for disabling the CTRACE at IKE daemon startup
          • Step for enabling the CTRACE after the IKE daemon is started
          • Step for disabling the CTRACE after the IKE daemon is started
          • Step for displaying the CTRACE status
          • Enabling CTRACE after IKE daemon initialization
        • Formatting IKE daemon trace records
    • Diagnosing network security services (NSS) server problems
      • Overview of diagnosing NSS server problems
        • Common NSS server initialization problems
        • NSS client connection problems
        • NSS XMLAppliance client API return codes and reason codes
      • Network security services server debug information
        • Obtaining syslog debug information for the network security service server
          • Abends
          • Error codes
      • TCP/IP services component trace for the network security services (NSS) server
        • Using CTRACE
      • Steps for enabling the CTRACE at network security service (NSS) server startup
        • Steps for enabling the CTRACE at network security services server startup
        • Steps for disabling the CTRACE at network security services server startup
        • Step for enabling the CTRACE after the network security services server is started
        • Step for disabling the CTRACE after the network security services server is started
        • Step for displaying the CTRACE status
        • Enabling CTRACE after network security services server initialization
        • Formatting network security services server trace records
    • Diagnosing dynamic VIPA and sysplex problems
      • Overview of diagnosing sysplex distributor problems
      • Steps for diagnosing sysplex problems
      • Steps for diagnosing problems using DVIPAs in source IP address selection for TCPconnections problems
      • Steps for diagnosing problems with the SYSPLEX-wide ephemeral port assignment for distributed DVIPAs
      • Diagnosing problems with the SYSPLEX-wide ephemeral port assignment for EXPLICITBINDPORTRANGE processing
        • Steps for determining an optimal range for the EXPLICITBINDPORTRANGE parameter
        • Steps for diagnosing problems with EXPLICITBINDPORTRANGE processing
      • Diagnosing sysplex-wide security association (SWSA) problems
        • Steps for diagnosing sysplex-wide security association (SWSA) problems
      • Steps for diagnosing sysplex routing problems
      • Steps for diagnosing Tier 1 z/OS sysplex distribution problems
      • Steps for diagnosing Tier 1 non-z/OS sysplex distribution problems
    • Diagnosing access control problems
      • Overview of access control support
      • Diagnosing multilevel security consistency check messages (EZD1215-EZD1234)
        • Steps for verifying the configuration
    • Diagnosing line print requester and daemon (LPR and LPD) problems
      • Diagnosing LPR client and LPD server problems
        • Abends
        • Steps for diagnosing timeouts, hangs, and waits
        • Incorrect output
          • Steps for diagnosing garbled data
          • Steps for diagnosing truncated or missing print data
          • Steps for diagnosing LPR working with some options only
      • LPR client traces
        • Step for activating LPR client traces
        • Step for creating client trace output
      • LPD server traces
        • Step for activating server traces
        • Step for creating server trace output
    • Diagnosing File Transfer Protocol (FTP) problems
      • FTP server
        • Structural overview
        • Definitions and setup
          • Start procedure
          • FTP.DATA data set
          • TCPIP.DATA data set
        • Error exit codes
        • Name considerations for z/OS UNIX FTP
          • MVS naming conventions
          • z/OS UNIX file system naming conventions
        • Translation and data conversion support
          • Double-byte character set (DBCS) support
          • Single-byte character (SBCS) support
          • Multibyte character set (MBCS) support
        • DB2 query support
          • Steps for using FTP server SQL support
          • Symptoms of SQL problems
        • JES support
          • JES output not found (zero spool files)
          • Remote job submission functions fail
          • FTP connection stops during FILETYPE=JES processing
        • Logging FTP server activity
        • Common z/OS UNIX FTP problems
          • FTP daemon initialization problems
            • No "Initialization Complete" message
            • Incorrect configuration values
            • FTP daemon not listening on expected port
            • AUTOLOG does not start the FTP daemon
          • User exit routine is not invoked
          • FTP Messages and FTP trace entries
          • FTP server abends
          • FTP session problems
            • Connection terminated by the server after user enters user ID
            • Connection terminated by the server after user enters password
            • Connection terminated by the server after user enters any subcommand
            • Password validation fails; session continues
            • Anonymous login fails
            • Wrong initial working directory
            • Unable to open data connection message from server
            • AT-TLS problems
          • Data transfer problems
            • PASV and EPSV commands fail because no PASSIVEDATAPORTS are available
            • Load module transfer failures
            • Data set allocation fails
            • Data set allocation not picking up correct characteristics
            • MVS data set not found
            • RETR, STOR, RNFR, RNTO, APPE, or DELE of data set fails
            • REST fails
            • Data transfer terminated
            • Client abends during RETR command data transfer
            • Data set disposition incorrect when transfer fails
            • Checkpoint markers do not appear to be sent
            • LOADLIB directory information is not sent with module transfer
            • Server PDS member statistics not created or updated
          • File transfers to the BatchPipe subsystem fail
        • Diagnosing FTP server problems with traces
          • Where to find traces
          • Start tracing
            • Start tracing during FTP initialization
            • Start tracing after FTP initialization
          • Stop tracing
          • Tracing activity for one user
          • Controlling the FTP server traces with MODIFY operator command
            • Controlling general tracing
            • Controlling extended tracing
        • Documenting server problems
      • FTP client
        • Execution environments
        • Setup
        • Naming considerations
        • Directing the client to exit when an error occurs
        • Translation and data conversion support
          • Double-byte character set (DBCS) support
          • Single-byte character (SBCS) support
          • Multibyte character set (MBCS) support
        • File tagging support
          • ASCII file transfers
          • Binary file transfers
        • DB2 query support
          • Steps for using FTP client SQL support
          • Symptoms of SQL problems
        • Restarting file transfers
          • Client rejects the RESTART subcommand
          • Client rejects SRESTART subcommand
          • Client accepts SRESTART subcommand, but server rejects RESTART
        • Diagnosing FTP connection and transfer failures with EZA2589E
          • Values and explanations for operation in EZA2589E
        • Diagnosing FTP client user exit problems
        • Problems starting the client
          • Enabling or suppressing message EZYFT47I during startup
          • Abends
          • Incorrect configuration values
        • Problems logging in to the server
          • Client ignores SOCKS configuration file
          • Client connects to wrong SOCKS server
          • Connection through SOCKS server to FTP server fails
          • Message EZA2589E appears while trying to log in
          • Server rejects password or password phrase
          • Unknown host error message
        • Problems transferring data
          • Cannot establish conversion between <codeset> and UCS-2
          • Secure IPv4 FTP session cannot transfer data through an NAT firewall
          • Firewall does not permit FTP client to establish a data connection
          • Server rejects PORT or EPRT command with 504 replies
          • Message EZA2589E appears when trying to transfer data
          • Message EZA1771I is displayed
          • Message EZA1776I is displayed
          • Message EZA1777I is displayed
          • Message EZA1778I is displayed
          • The target data set does not match the source data set using the MVSGet or MVPut subcommand
          • The MVSGet or MVSPut subcommand fails when transferring a physical sequential extended format data set
          • REStart the failed PDS and library data sets transfer for the MVSGet or MVSPut subcommand
        • Other problems
          • Client PDS member statistics not created or updated
        • Diagnosing FTP client problems with tracing
        • Where to find the FTP client trace
        • Documenting FTP client problems
    • Diagnosing z/OS UNIX Telnet daemon (otelnetd) problems
      • Common problems
      • Debug traces
        • Debug trace flows (netdata and ptydata)
        • Debug trace examples (-t -D all)
        • Cleaning up the utmp entries left from dead processes
    • Diagnosing Telnet problems
      • General TN3270E Telnet server information
      • TN3270E Telnet server definitions
      • Diagnosing TN3270E Telnet server problems
        • Abends (server)
          • Documentation
          • Analysis
        • Logon problems (server)
          • Documentation
          • Steps for analyzing logon problems (server)
        • Session hangs (server)
          • Documentation
          • Steps for analyzing session hangs (server)
        • Incorrect output (server)
          • Documentation
          • Steps for analyzing incorrect output (server)
        • Session outages (server)
          • Documentation
          • Steps for analyzing session outages (server)
        • Special considerations when using SSL encryption support
        • Telnet Component Trace data
      • General Telnet client information
      • Telnet client definitions
      • Diagnosing Telnet client problems
        • Abends (client)
          • Documentation
          • Analysis
        • Session hangs (client)
          • Documentation
          • Steps for analyzing session hangs (client)
        • Incorrect output (client)
          • Documentation
          • Steps for analyzing incorrect output (client)
      • Telnet client traces
        • Step for starting Telnet client traces
        • Trace example (client)
      • Telnet commands and options
    • Diagnosing Simple Mail Transfer Protocol (SMTP) problems
      • Sender SMTP
      • Receiver SMTP
      • SMTP environment
      • SMTP definitions
      • Diagnosing SMTP problems
        • Abends
          • Documentation
          • Analysis
        • Spooling problems
        • SMTP does not deliver mail
          • Steps for undeliverable mail items
          • Documentation
          • Steps for analyzing mail delivery problems
        • SMTP loop
          • Documentation
        • Mail item has incorrect output
          • Documentation
          • Steps for analyzing incorrect mail output
        • Forcing resolution of queued mail
      • ADDRBLOK data set
      • SMTP RESOLVER trace
    • Diagnosing z/OS UNIX sendmail and popper problems
      • Diagnostic aids for sendmail
      • Debugging switches
      • Additional diagnostic aids
      • Diagnostic aids for IPv6 support
      • Diagnostic aids for AT-TLS support
      • Diagnostic aids for mail filter support
      • Hints and troubleshooting sendmail message submission program (MSP) file submit.cf
      • Diagnostic aids for popper
    • Diagnosing SNALINK LU0 problems
      • Definitions
      • Problem diagnosis
        • Abends
          • Documentation
          • Analysis
        • Session hangs
          • Documentation
          • Steps for analyzing session hangs
        • Session outages
          • Documentation
          • Analysis
      • Traces
        • Using IP packet trace
        • SNALINK LU0 DEBUG trace
          • Starting SNALINK LU0 DEBUG trace
          • DEBUG trace example
    • Diagnosing SNALINK LU6.2 problems
      • Steps for setting up a SNALINK LU6.2 network
      • Common configuration mistakes
      • Diagnosing problems
        • Quick checklist for common problems
        • Problems starting the SNALINK LU6.2 address space
          • Documentation
          • Analysis
        • DLC connection problems
          • Steps for checking DLC connection status
          • Analysis
        • Network connection establishment problems
          • Steps for checking network connection problems
          • Analysis
        • Network connection loss problems
          • Documentation
          • Analysis
        • Data loss problems
          • Steps for documenting data loss problems
          • Analysis
        • Data corruption problems
          • Documentation
          • Analysis
      • Documentation references for problem diagnosis
        • Using NETSTAT
        • Using the SNALINK LU6.2 subcommand
        • Useful VTAM operations
          • Activating an LU
          • Changing an LU definition
          • Displaying the status of an LU
      • Traces
        • Using SNALINK LU6.2 internal traces
        • Using IP packet trace
        • TCP/IP internal traces
        • VTAM buffer traces
      • Finding abend and sense code documentation
      • Finding error message documentation
    • Diagnosing REXEC, REXECD, and RSH problems
      • General information about REXEC and RSH
        • Documentation for REXEC problem diagnosis
        • TSO console log
        • Activating the REXEC debug trace
        • REXEC trace example and explanation
        • RSH trace example and explanation
      • General information about REXECD
        • Documentation for REXECD problem diagnosis
        • MVS system console log
        • Starting REXECD server traces
        • Example of an REXECD trace of a client using the SEND command
        • Example trace of an RSH client using the SEND command
        • Example trace to the JES spool file of the server
    • Diagnosing z/OS UNIX REXEC, RSH, REXECD, and RSHD problems
      • Setting up the inetd configuration file
      • Diagnosing z/OS UNIX REXEC
        • Activating the z/OS UNIX REXEC debug trace
        • z/OS UNIX REXEC trace example and explanation
      • Diagnosing z/OS UNIX RSH
        • Step for activating the z/OS UNIX RSH debug trace
        • Step for invoking z/OS UNIX RSH trace
      • Diagnosing z/OS UNIX REXECD
        • Activating the z/OS UNIX REXECD debug trace
        • z/OS UNIX REXECD trace example and explanation
      • Diagnosing z/OS UNIX RSHD
        • Step for activating the z/OS UNIX RSHD debug trace
        • z/OS UNIX RSHD trace example and explanation
          • Resolving garbage errors
    • Diagnosing X Window System and Motif problems
      • Trace output when XWTRACE=2
      • Trace output when XWTRACELC=2
    • Diagnosing Simple Network Management Protocol (SNMP) problems
      • Overview
        • Management information base (MIB)
        • PDUs
        • Functional components
          • Managers
          • Agents
          • Subagents
          • Trap forwarder daemon
      • Definitions
        • z/OS UNIX snmp command
        • SNMP agent
        • TCP/IP subagent
        • OMPROUTE subagent
        • Network SLAPM2 subagent
        • TN3270E Telnet subagent
        • SNMP socket call settings
        • Trap forwarder daemon
      • Diagnosing SNMP problems
        • Abends
          • Documentation
          • Analysis
        • SNMP connection problems
          • Problems connecting the SNMP agent to the TCP/IP address space
            • Documentation
            • Analysis
          • Problems connecting SNMP agents to multiple TCP/IP stacks
            • Analysis
          • Problems connecting subagents to the SNMP agent
            • Documentation
            • Analysis
          • Problems connecting to the SNMPIUCV subtask
            • Documentation
            • Analysis
          • Problems connecting the SNMP query stack to the TCP/IP address space
            • Documentation
            • Analysis
        • Incorrect output
          • Unknown variable
            • Documentation
            • Analysis
          • Variable format incorrect
            • Documentation
            • Analysis
          • Variable value incorrect
            • Documentation
            • Analysis
        • No response from the SNMP agent
          • Documentation
          • Analysis
        • SNMPv3 AES encryption or decryption failures
          • Documentation
          • Analysis
        • Report received from SNMP agent
        • 0.0.0.0 address in traps from the SNMP agent
        • I/O error for SNMP PING
          • Documentation
          • Analysis
        • Traps not forwarded by trap forwarder daemon
          • Documentation
          • Analysis
        • Incorrect address in forwarded trap
          • Documentation
          • Analysis
      • SNMP traces
        • Starting manager traces
        • Starting SNMP agent traces
          • If agent is not running
          • If agent is already running
        • Starting TCP/IP subagent traces
        • Starting OMPROUTE subagent traces
        • Starting Network SLAPM2 subagent traces
        • Starting TN3270E Telnet subagent traces
        • Starting TRAPFWD traces
          • If TRAPFWD is not running
          • If TRAPFWD is already running
        • Trace examples and explanations
          • SNMP agent traces
          • TCP/IP subagent trace
          • NetView SNMP query engine trace
          • NetView SNMP query engine IUCV communication trace
          • TRAPFWD Trace
    • Diagnosing Policy Agent problems
      • Overview
      • QoS policy
      • QoS policy scope
      • Import services
      • Gathering diagnostic information
      • Diagnosing Policy Agent problems
        • Initialization problems
        • Policy definition problems
        • Policy client connection problems
        • Policy client retrieval problems
        • Import requestor connection problems
        • Import requestor retrieval problems
        • LDAP object retrieval problems
        • LDAP object storage problems
        • Policy Agent and Sysplex distribution problems
          • Steps for diagnosing Policy Agent/Sysplex distribution problems
        • Memory allocation/leakage problems
    • Diagnosing RSVP agent problems
      • Overview
      • Reservation types, styles, and objects
      • Policies and RSVP processing
      • Gathering diagnostic information
      • Diagnosing RSVP agent problems
        • Initialization problems
        • Application problems
        • Policy problems
        • Example log file
    • Diagnosing intrusion detection problems
      • Overview
      • Diagnosing IDS policy problems
        • Step for determining which IDS policies are active in Policy Agent
        • Step for determining how your IDS policies have been mapped by the stack
      • Diagnosing IDS output problems
        • Steps for determining why IDS syslogd output is missing
        • IDS console output
        • IDS packet trace output
        • Unusual conditions
          • Buffer overflow transferring message data between the stack and TRMD
          • Repeated attacks of the same type at a high rate
          • Scan storage constrained
          • Excessive processing time for scans
          • Interface flood detection disabled
          • Interface flood storage constrained
      • Diagnosing TRMD problems
      • Documentation for the IBM Software Support Center
    • Diagnosing Application Transparent Transport Layer Security (AT-TLS)
      • Common AT-TLS startup errors
      • Steps for diagnosing AT-TLS problems
      • AT-TLS traces
        • Sample AT-TLS trace
      • AT-TLS return codes
      • SIOCTTLSCTL ioctl return codes
    • Diagnosing Defense Manager daemon problems
      • Overview of diagnosing Defense Manager daemon problems
      • Defense Manager daemon debug information
        • Abends during DMD processing
        • DMD error codes
      • TCP/IP services component trace for the Defense Manager daemon
        • CTRACE options
      • Enabling CTRACE at Defense Manager daemon startup
        • Steps for enabling the CTRACE at Defense Manager daemon startup
        • Steps for disabling the CTRACE at Defense Manager daemon startup
        • Step for enabling the CTRACE after the Defense Manager daemon has started
        • Step for disabling the CTRACE after the Defense Manager daemon is started
        • Displaying the CTRACE status
        • Enabling CTRACE after Defense Manager daemon initialization
        • Formatting Defense Manager daemon trace records
    • Diagnosing IP security and defensive filter problems
      • Overview of diagnosing IP security and defensive filter problems
      • Steps for diagnosing IP security problems
      • Steps for diagnosing defensive filter problems
      • Steps for diagnosing the cause for missing IP security or defensive filter syslogd output
      • Steps for verifying IP security and defensive filter operation
        • Steps for verifying manual IPSec protection
        • Steps for verifying dynamic IPSec protection
        • Steps for verifying IP security policy or defensive filter enforcement
        • Steps for verifying IPSec processing on zIIP
        • Determining the Workload Manager service class associated with IPSec workload being processed on zIIP
      • Tools for diagnosing IP security and defensive filter problems
        • Using the ipsec command
          • ipsec -f display
          • ipsec -F display
          • ipsec -m display
          • ipsec -k display
          • ipsec -y display
          • ipsec -i
          • ipsec -t
          • ipsec -o
          • ipsec -w
          • ipsec -x
        • Using the pasearch command
        • Using syslog messages
    • Diagnosing OMPROUTE problems
      • Overview
      • Definitions
      • Diagnosing OMPROUTE problems
        • Abends
        • OMPROUTE connection problems
        • Routing failures
          • Analyzing routing failures
          • Documenting routing failures
        • Adjacency failures
          • Analyzing adjacency failures
          • Documenting adjacency failures
        • Malformed and unexpected packets
          • Analyzing malformed and unexpected packets
          • Documenting malformed and unexpected packets
      • OMPROUTE traces and debug information
        • Starting OMPROUTE tracing and debugging from the z/OS UNIX System Services shell
        • Starting OMPROUTE tracing and debugging from an MVS cataloged procedure or AUTOLOG
        • Starting OMPROUTE tracing and debugging using the MODIFY command
        • Destination of OMPROUTE trace and debug output
      • Sample OMPROUTE trace output
      • TCP/IP services component trace for OMPROUTE
        • Specifying trace options
          • Specifying options at initialization
            • Specifying options after initialization
        • Formatting OMPROUTE trace records
      • Commands to enable, disable, and display the status of the OMPROUTE CTRACE
        • Steps for enabling the CTRACE at OMPROUTE startup
        • Steps for disabling the CTRACE at OMPROUTE startup
        • Steps for enabling the CTRACE after OMPROUTE is started
        • Steps for disabling the CTRACE after OMPROUTE is started
        • Step for displaying the CTRACE status
    • Diagnosing NCPROUTE problems
      • Definitions
      • Diagnosing NCPROUTE problems
        • Abends
          • Documentation
          • Analysis
        • Connection problems
          • Documentation
          • Analysis
            • Steps for NCPROUTE connection problems
        • Analyzing routing failures
          • Documentation
          • Analysis
            • Steps for analyzing routing failures
        • Incorrect output
          • Documentation
          • Analysis
            • Steps for diagnosing incorrect output
        • Session outages
          • Documentation
          • Analysis
      • NCPROUTE traces
        • Activating NCPROUTE global traces
        • Activating NCPROUTE selective traces
        • NCPROUTE trace example and explanation
    • Diagnosing X.25 NPSI problems
      • Operation
      • Configuration requirements
        • RACF/Security Manager requirement
        • VTAM considerations
        • NPSI considerations
      • Sources of diagnostic information
      • X.25 trace examples
        • Normal incoming call, TRACE OFF
        • Normal incoming call, TRACE DATA
        • Normal outgoing call, TRACE CONTROL
        • Results of LIST command
        • Termination by TCPIP STOP device
      • Steps for diagnosing logon problems
      • Session hangs
        • Helpful hints
        • Documentation requirements
    • Diagnosing IMS problems
      • Steps for setting up the IMS TCP/IP services socket interface system
      • Common configuration mistakes
      • Quick checklist for common problems
        • Component problems
        • Connection problems
        • Error message and return code problems
        • Socket data protocol problems
        • IMS transaction build problems
        • IMS database problems
      • Documentation references for problem diagnosis
        • Traces
          • Using IP packet trace
          • TCP/IP internal traces
          • IMS traces
        • Using NETSTAT
        • Where to find return code documentation
        • Where to find error message documentation
    • Diagnosing VMCF/TNF/IUCV problems
      • Diagnosing restartable VMCF/TNF problems
        • VMCF or TNF fail to initialize
        • Abends 0D5 and 0D6
        • Steps for diagnosing no response to commands
        • VMCF or TNF does not stop
      • Diagnosing VMCF/IUCV problems with the TSO MVPXDISP command
    • Diagnosing problems with IP CICS sockets
      • Diagnostic data
      • Initialization problems
        • Steps for diagnosing CICS socket interface not initialized
        • Steps for diagnosing CICS listener not initialized
        • No CICS sockets messages issued
        • Steps for diagnosing TCP/IP clients unable to connect
        • Steps for diagnosing child-server transactions not starting
      • CICS sockets application problems
        • Steps for diagnosing hung CICS tasks
        • Hung CICS region
        • Errors on socket calls
        • CICS shutdown hangs
      • CICS sockets control blocks
        • Task interface element
        • Global work area
      • CICS trace
        • Steps for displaying the internal trace
    • Diagnosing problems with SMC-R
      • Switch configuration issues
      • Physical network ID configuration issues
      • No associated subnet mask
      • PFID status remains STARTING
      • Problem with SMC-R interaction with security function
    • Diagnosing problems with Express Logon
      • Analyzing start problems with the DCAS
      • Analyzing client interface problems
    • Diagnosing resolver problems
      • Steps for resolving the hostname
        • Steps for resolving caching problems
        • Steps for responding to message EZZ9308E
        • Steps for responding to message EZZ9311E
      • TRACE RESOLVER
        • Specifying the Trace Resolver output location
          • TSO environment
          • z/OS UNIX shell environment
          • MVS batch job environment
          • z/OS UNIX batch environment
        • Interpreting the Trace Resolver output
      • CTRACE — RESOLVER
    • Diagnosing Simple Network Time Protocol (SNTP) problems
      • Activating the SNTPD debug trace
      • Abends
      • Steps for stopping SNTPD
      • Sample SNTPD debug output
    • Diagnosing Communications Server SMTP application problems
      • Gathering diagnostic information
        • Steps for gathering log information
      • Resolving initialization or logging problems
      • Resolving SMTPNOTE CLIST problems
      • Diagnosing and resolving Resolver problems
      • Resolving problems from the JES spool data set
      • Resolving mail problems
        • Target server problems
        • Mail problems
          • Using the undeliverable mail notification for problem determination
      • Resolving MODIFY command problems
      • Diagnosing checkpoint problems
      • Monitoring resources used
      • Monitoring target servers
        • ExtendedRetry Mail Directory
    • Diagnosing storage abends and storage growth
      • Storage definitions
      • Monitoring storage utilization
      • Limiting TCP/IP common and private storage utilization
      • Limiting CSM storage utilization
      • Storage messages
        • Sysplex Problem Detection and Recovery (SPDR) storage messages
      • Abends
      • Diagnosing a storage problem
        • Steps for reviewing a storage problem
        • Steps for reviewing data on the TCP queues
        • Steps for reviewing data on the queue if you are using IDS
        • Steps for reviewing data on the queue if you are not using IDS
        • Collecting documentation to submit to the IBM Support Center
  • First Failure Support Technology (FFST)
    • FFST probe index
    • FFST probe information
    • FFST probe naming conventions
    • FFST probe descriptions
  • Overview of internetworking
    • Maximum transmission unit (MTU)
    • Fiber Distributed Data Interface (FDDI)
    • Token-Ring IEEE 802.5
    • IEEE 802.3
    • Ethernet — DIX V2
    • Subnetwork Access Protocol (SNAP)
    • IP routing
    • Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6)
      • Internet Protocol Version 4 (IPv4)
      • Internet Protocol Version 6 (IPv6)
    • Direct routing
    • Indirect routing
    • Simplified IP datagram routing algorithm
    • IPv4 subnetting
    • IPv6 prefixes
    • Simplified IP datagram routing algorithm with subnets
    • Static routing
    • Dynamic routing
      • IPv4
      • IPv6
  • IKE protocol details
    • IKE version 1 protocol
      • Overview of negotiating IKEv1 security associations
      • Phase 1
        • Main mode
        • Aggressive mode
        • Interpreting IKEv1 daemon phase 1 SA states
      • Phase 2
        • Quick mode
        • Quick mode with commit bit
        • Interpreting IKEv1 daemon phase 2 SA states
          • Quick mode (phase 2) SA states without commit-bit support
          • Quick mode (phase 2) SA states with commit-bit support
      • ISAKMP Main mode limitations
        • Main mode scenario 1
        • Main mode scenario 2
        • Main mode scenario 3
    • IKE version 2 protocol
      • Overview of negotiating IKEv2 security associations
      • Initial exchanges
        • Interpreting IKEv2 IKE SA states
      • Child SA activation
        • First Child SA
        • Additional Child SAs
        • Interpreting IKEv2 Child SA states
      • Key exchange limitations
        • Responder
        • Initiator
    • Traversing a NAT
  • IBM Health Checker for z/OS
  • Related protocol specifications
  • Accessibility
    • Bibliography
      • Index for IP Diagnosis