Home About Courses Schedule Services Webinars Contact Search

TCP/IP Diagnostics and Debugging on z/OS

SEE SCHEDULE

Duration: 4 days

Method: Instructor led, Hands-on workshops

Price: $2250.00

Course Code: MF5095


Audience

This class is intended for experienced systems programmers with a good understanding of TCP/IP functions.

Description

This class is a lecture-workshop for experienced systems programmers with a focus on using the tools available to narrow down the scope of network problems, identify failed components and debug TCP/IP problems. Emphasis will be on problem diagnosis and “hands-on” exercises using the available tools. This class is specifically customized to accommodate the fact that the majority of students will have had experience in dealing with SNA problem determination and so emphasis will be placed on the different approaches necessary for dealing with the TCP/IP architecture.

Topics

  • I.Tools and Service Aids
    • Collecting trace information and diagnostic data
      • Data collection and trace activation
      • Overhead considerations
    • Activating and analyzing traces using z/OS system tools
      • Component trace options
      • Tracing specific protocol elements
    • When to take a Dump?
      • What needs to be captured?
    • Online Commands and options for Dump
      • DUMP options
      • SLIP traps and other diagnostic procedures for TCP/IP stack related problems
    • Dump verification
    • Overview of commands for network diagnostic data
      • Commands to confirm configuration
      • Commands to determine operational status
    • Diagnostic data collection/commands in z/OS and Unix System Services
    • Diagnosing TCP/IP DVIPA and sysplex distributor problems ( using syslogd for problem determination)
    • Review operation of the parallel sysplex, Unix System Services (USS), and the use of multiple TCP/IP stacks in z/OS.
    • Review configuration options and considerations in using multiple stacks.
  • II.TCP/IP Service Traces and IPCS
    • Tracing will focus on the various data types that can be traced, when they would be appropriate to use, and the expectations that can be placed on such data. This will involve understanding the tools to capture trace data and return results as well as reviewing guidelines for appropriate value ranges to examine to determine various problem states that may occur and how to pursue follow-up problems.
    • Traces:
      • Event tracing
      • Packet tracing
      • Data traces
      • Intrusion detection tracing
      • OMPROUTE traces
      • RESOLVER traces
      • Configuration profile trace
      • OSPF Routing and routing table diagnosis
      • FTP Traces
      • Configuring for recoverability – Dynamic VIPA recovery / takeover
      • Telnet
    •  TN3270 traces ( with debugging)
    •  Server information and diagnostics
    •  Client information and diagnostics
  • III.General diagnostics for component failure
    • Diagnosing abends, loops, and hangs
      • Data collection options
      • TCP/IP options for using IPCS
      • Debugging tools
    • Performance issues / Response time diagnostics
      • TCP/IP performance considerations (service class requirements)
      • Network performance considerations (basic analysis/queuing concepts)
      • Capacity problems versus diagnostic causes of performance issues