The Client-Library ct_debug routine has been revised and allows you to trace and dump the Tabular Data Stream™ (TDS) to a file, without being required to download, install and configure capture, or use the Ribo (TDS trace tool). The following are the revisions to the ct_debug routine parameters:
To enable CS_DBG_PROTOCOL, or to set CS_DBG_PROTOCOL_FILE, an application no longer needs to use the devlib (debug) libraries.
If you do not set CS_DBG_PROTOCOL_FILE on a connection, mktemp is called to generate a unique file name to contain the dump of the protocol packets. The prefix string passed to mktemp is “captur” and the resulting protocol file can be decoded by Ribo.
It is possible for you to enable the protocol dump functionality using the ocs.cfg file which will cause both the normal and devlib libraries to create protocol dump files.
