SNAP-IX Diagnostics Guide

• BeforeYou Begin
  • Prerequisite Knowledge
  • About This Book
    • Organization of This Book
    • Typographic Conventions
  • SNAP-IX Publications
    • Publications for Users
    • Publications for Administrators
    • Publications for Programmers
  • Related Publications
• 1 Overview of Problem Solving
  • 1.1 Types of Diagnostic Information
    • 1.1.1 Program Error Messages
    • 1.1.2 Log Messages
    • 1.1.3 Introducing Tracing
    • 1.1.4 Alerts
    • 1.1.5 Help Information
• 2 Resolving Common Problems
  • 2.1 Basic Checks
    • 2.1.1 What to Check First
    • 2.1.2 Check That the SNA Daemon Is Started
    • 2.1.3 Check That the Local SNA Node Is Active
    • 2.1.4 Check Communication with Other SNA Nodes
    • 2.1.5 Check that the Solaris Client Can See its Servers
    • 2.1.6 Check that a Windows Client Can See its Server
    • 2.1.7 Check System Configuration Information
    • 2.1.8 Check the Style Files
  • 2.2 Resolving Specific Problems
    • 2.2.1 Resolving Problems with Programs That Use Motif
    • 2.2.2 Resolving Problems with the 3270 Emulation Program
    • 2.2.3 Resolving Problems with RJE
    • 2.2.4 Resolving APPC or CPI-C Application Problems
    • 2.2.5 Resolving LUA orLU0 Problems
    • 2.2.6 Resolving HLLAPI Problems
    • 2.2.7 Resolving MS Application Problems
    • 2.2.8 Resolving NOF Application Problems
    • 2.2.9 Resolving 5250 Emulation Problems
    • 2.2.10 Resolving Problems with TN Server
    • 2.2.11 Resolving NDMA Problems
    • 2.2.12 Resolving Network Node Session Routing Problems
    • 2.2.13 Resolving PU Concentration Session Problems
    • 2.2.14 Resolving Server Administration Problems
  • 2.3 Reporting Problems to Support Personnel
    • 2.3.1 Types of Support Personnel
    • 2.3.2 Information to Provide to Support Personnel
• 3 Using Logging and Tracing
  • 3.1 Controlling Logging Using the Motif Administration Program
  • 3.2 Controlling Logging Using the Command-Line Administration Program
    • 3.2.1 Changing the Names and Locations of Log Files
    • 3.2.2 Enabling Central Logging and Local Logging
    • 3.2.3 Determining Which Messages Are Logged
    • 3.2.4 Controlling Log File Size
    • 3.2.5 Choosing the Format of Logs
  • 3.3 Usage Logging
    • 3.3.1 Usage Log File
    • 3.3.2 Using Administration Tools to Check Resource Usage
  • 3.4 Tracing
    • 3.4.1 Line Tracing
    • 3.4.2 API Tracing
    • 3.4.3 Client-Server Tracing
    • 3.4.4 TN Server Tracing
    • 3.4.5 3270 Emulation Program Tracing and RJE Workstation Tracing
    • 3.4.6 Internal Tracing
• Appendix A: Using snafilter and snatrcfmt
  • A.1 Filtering Binary Tracing
    • A.1.1 Running the snafilter Utility
    • A.1.2 Sample Command and Output
  • A.2 Formatting Internal Binary Trace Output into Text Files
    • A.2.1 Running the snatrcfmt Utility for Line Tracing
    • A.2.2 Running the snatrcfmt Utility for Internal Tracing
    • A.2.3 Output from the snatrcfmt Utility
• Appendix B: Using snagetpd
  • B.1 Operating snagetpd
  • B.2 Command Syntax and Program Output
  • B.3 Command Restrictions
• Appendix C: Windows Clients
  • C.1 Logging for Windows Clients
  • C.2 Controlling Tracing on Windows Clients
• Index