text: **Method 2: Setting up the trace by using the DB2 command line**
  Alternatively, you can use the DB2 command line to activate the trace by completing the 
  following steps: 
  
  1.  In the DB2 instance, run the DB2 commands that are shown in Example 18-3. 
  
  *Example 18-3 Turning on the trace through the DB2 command line*
  
  db2 UPDATE CLI CFG FOR SECTION COMMON USING Trace 1 
  db2 UPDATE CLI CFG FOR SECTION COMMON USING TraceRefreshInterval 5 
  db2 UPDATE CLI CFG FOR SECTION COMMON USING TraceFileName /tmp/db2trace.dmp 
  db2 UPDATE CLI CFG FOR SECTION COMMON USING TraceComm 1 
  db2 UPDATE CLI CFG FOR SECTION COMMON USING TraceFlush 1 
  
  2. Restart the application (in this case**arssockd**) for the changes to take effect. 
  
  3. Re-create the DB2 problem and capture the trace information. 
  
  4. Run the following command to turn off the traces: 
  
  db2 UPDATE CLI CFG FOR SECTION COMMON USING Trace 0 
  
  5. Restart**arssockd**. 
  
  **18.2.3 Tivoli Storage Manager**
  
  For Content Manager OnDemand problems that relate to Tivoli Storage Manager, collect the 
  information that is shown in Table 18-6. For specific Tivoli Storage Manager errors, see 
  *Collecting Data: Read First for Tivoli Storage Manager Products,*reference number 1263547*.*