Generating .CSV Files About Check-out Operations

Before you run the utility, you must enable tracing for the server configuration. With tracing enabled, the server generates a trace record for each checked out file and saves the information in a trace file (Checkout.cotrc). The utility uses the trace file as input and outputs a *.csv file containing data about the check-out operations.

The Check-out Trace utility takes one or more check-out trace (*.cotrc) files as input and outputs one *.csv text file containing check-out trace data as comma-delimited values. The default filename for the .csv file is identical to the name of the trace file with the extension .csv. For example, when the trace filename is Checkout.cotrc, then the csv output filename is Checkout.cotrc.csv.

To run the Check-out Trace utility

At the command prompt, navigate to the CheckoutTraceDump.exe file in the StarTeam Server root installation folder.
The -go option signals the utility to run with default options. You can set many parameters for the utility. For a list of all of the available options, review the command line operations for the utility at the link referenced at the bottom of this topic.
Note: By default, the server saves the trace files in the Trace folder (a subfolder of the repository folder Checkout.cotrc). You cannot run the utility against the current trace file, but you can copy the trace file and run the utility against the copy.

Tip: If you want to run the utility from a workstation rather than on the server, you can copy CheckoutTraceDump.exe and OSSup.dll to the alternate location. Be cautious not to move OSSup.dll to the new location because the server configuration also relies on it. Additionally, the utility depends on the Microsoft .NET Runtime, so it must be available on the alternate workstation.