Step 2 - Use Trace Facilities

Step 1 requires no user or programmer intervention with failing code. Step 2 involves setting trace points and using trace data, and it does require intervention. The following functions are available in OS/2 Warp Version 4 to help you use trace effectively:

• A function to insert trace points in your code
  
• A command that describes the trace file to be used
  
• A command that turns trace on and off
  
• A utility called Trace Customization that lets you format entries in the trace file
  
• A utility called Trace Formatter that displays the contents of the trace file

Traces allow you to see and follow the course of events in code that lead to a failure. You can use trace data:

• To understand the order or determine the operating path of the code 
  To understand parameter data changes during processing
  
  To examine inputs to functions and outputs from functions
  
  To examine resulting return codes
  
  To save intermediate data values

  Analyzing Performance and Debugging Problems Using Trace, contains more information about the Trace facilities.

  ---

  [Back: Step 1 - Check the Error Log and Data Areas]
  [Next: Step 3 - System Dump]