Trace event logs

ISAM provides configurable tracing capabilities that can aid in problem determination. Unlike message logs, trace logs (or tracing) are not enabled by default. Trace data is intended primarily for use by IBM Software Support. Trace data might be requested as part of diagnosing a reported problem. However, experienced product administrators can use trace data to diagnose and correct problems in a ISAM environment. Attention: Use trace with caution. It is intended as a tool to use under the direction of IBM Software Support. Messages from tracing are sometimes cryptic, are not translated, and can severely degrade system performance.

Trace logs are best suited to situations where a problem is easily reproduced, is short-lived in duration, and can be produced without significant trace generation from other system activity. Enabling tracing can adversely affect the performance ISAM and its associated products and applications.

Tracing can be activated when servers, daemons, and applications start by using routing files and Java™ properties files. In some cases, tracing can be activated dynamically by using the server task trace command with the set option. Tracing from the C-language portions ISAM is controlled through routing files. Similarly, tracing from the Java language portions ISAM is controlled through Java properties files. When relevant, the distinction between these two methods of trace handling is mentioned.

• Mechanisms for controlling trace logs
  
• Manage Trace
  
• Tracing configuration file examples
  
• Determining maximum size of a trace log
  
• Enable trace
  
• Use the trace commands
  
• Format of trace entry in logs
  
• Trace logging for WebSEAL
  
• Available trace components
  

Parent topic: Troubleshoot