IBM Support

Connect:Direct for Windows: Capturing a Trace using the Command Line Interface.

How To


Summary

Provide instructions for capturing a Connect:Direct for Windows (CDW) trace using the Command Line Interface (CLI).

Objective

For a CDW trace, by default, the trace file size is set at 10Mb and the tracing process will wrap around and start overwriting data.

This can be undesirable when tracing a long running process when you want a complete trace start to finish.

The Web Services tool, both standalone and integrated, does not allow you to override these default settings.

This document provides instructions for capturing a trace and overriding the default file size and wrap status.

Environment

Supported CDW running on supported Windos OS.

Steps

Follow these steps to capture a trace using the CDW 'direct' CLI.

 

1. Login to the CDW server OS with the user ID that owns the CDW instance.

2. Open a command prompt with 'Run as administrator'.

3. Navigate to the '[CDW_Installation_Path]\Connect Direct v6.x.0\Common Utilities' folder.

4. Run 'direct' to start the CDW CLI.

    You should see the following.

    

     If you get an error stating, "Not enough connection information was supplied....", use the following command string.

      direct -nNode_Name -uUser_ID -pPassword   <<<No spaces between the flag and the value>>>

5. Run the following command string to start the tracing process.

    traceon type=(cmgr pmgr smgr comm) level=full file=c:\temp\cdtrace.cdt filesize=0 wrap=no;

    You can specify your own path for the trace file.

    The "filesize" and "wrap" parameters allow the file to grow as needed and to not wrap and overwrite data.

    You should see the following.

    

 

6. Run the process that generates the issue being investigated.

7. Once the process finishes, run the following command string to turn off tracing.

    traceoff type=(cmgr pmgr smgr comm);

    You should see this.

    

 

8. Enter "q;" to exit the CLI.

9. Login to the CDW server using the Integrated Web Services tool.

10. Capture a Statistics log for the same time period as the trace was run.

      Follow the instructions in this Technote.

      Pay special attention to Step 5.

      We use the Statistics data to help locate pertinent sections in the trace file; this helps especially when the trace file is very large.

11. Also, if you have not already done so, run the CDW Data Collector to capture the CDW configuration data.

      Reference this section of the CDW online System Guide.

12. Upload the Trace, Statistics, and configuration files to the case.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRRVY","label":"IBM Sterling Connect:Direct for Microsoft Windows"},"ARM Category":[{"code":"a8m0z000000cwUdAAI","label":"CD PROCESS"},{"code":"a8m0z000000cwUuAAI","label":"STATS"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"and future releases;6.3.0;6.4.0"}]

Document Information

Modified date:
26 January 2026

UID

ibm17258032