Tracing data for the client

You can enable tracing on the client or client application programming interface (API) by altering the client options file.

1. Determine the trace classes to enable from the following table:

   Trace Class Name	Description	When to use	Additional Notes
   SERVICE	Display general processing information for the client.	Useful in many cases. Generally recommended for protocol violations, transaction processing errors, or in cases where the client is stopped and not responding.
   VERBINFO	Collect information regarding the client-server protocol used by IBM® Tivoli® Storage Manager.	To debug protocol violations, transaction processing errors, or in cases where the client is stopped and not responding.
   VERBDETAIL	Detailed information regarding the client-server protocol used by Tivoli Storage Manager. This displays internal memory buffers containing the verbs sent and received by the client.	To debug session data corruption issues that might be caused by the network.	This generates a large amount of output.

2. Enable the trace by adding the following text to the client options file: traceflag <trace class name>.
   Attention: <trace class name> might be a comma-delimited list of trace classes. For example, this text could be entered as traceflag service,verbinfo,verbdetail.
3. Configure trace to begin and issue the trace messages to a file by adding the following text to the client options file: tracefile <file name>.
4. Perform the operation that is causing the problem.
   Tip: Tracing might also be configured and started by invoking the client from a command prompt and specifying the flags above. For example, dsm -traceflags=service -tracefile=file.out.