text: In ODWEK V8.5.0.0 and later, the trace file is written in binary. To convert the trace file from 
  its binary format, use the**arstfmt**command that is in the bin directory of your Content 
  Manager OnDemand server (version 8.5 and later). The following sample command shows 
  how to convert the ODWEK trace file: 
  
  /usr/lpp/ars/v9.5/bin/arstfmt -i arswww.trace -o arswww.trace.txt 
  
  Tracing can be set to different levels with the**trace**parameter. When you troubleshoot an 
  ODWEK issue, set the trace level to the highest level, unless you are instructed otherwise by 
  IBM Support. 
  
  Setting the trace at lower levels, such as Trace=1, creates a minimal impact while it alerts you 
  only about error conditions. Setting the lower trace levels are ideal for monitoring an ODWEK 
  application that is in a steady state. Higher levels are used for troubleshooting an ODWEK 
  issue. 
  
  **18.4.4 TCP/IP packet trace**
  
  If a problem exists with TCP/IP, a TCP/IP packet trace might be helpful in troubleshooting. 
  
  Example 18-5 show a procedure for tracing to an external writer. 