The TRS tracing facility provides entry/exit tracing, tracing of the TRS interface with the back-end transport protocol, and TDS header and data tracing. When you enable tracing, tracing information is written to a set of error logs.
Ordinarily, you do not need to trace TRS activity. The tracing facility is provided to help Sybase Technical Support assist you if you call about certain errors. Tracing can also be useful for diagnosing local area network (LAN) and client application problems. For more information about tracing, see the sections describing the TRS TraceTRS, TraceProtocol, ProtocolTraceFile, and TDSTraceFile configuration properties in Chapter 2, “Creating a TRS Library.”
Mainframe-based tracing is described in the Mainframe Connect Server Option Programmers Reference guides. COBOL and PL/1 versions of this guide are available.
To enable or disable entry/exit tracing, set the server’s TraceEntryExit property. TRS entry/exit tracing accesses the following file:
For UNIX:
/<install_dir>/DC-15_0/srvname/log/srvname.trc
For Windows:
C:\<install_dir>\DC-15_0\srvname/log\srvname.trc
To enable or disable TDS tracing before TRS starts running, set the appropriate properties in the TRS configuration file. See the sections describing the TRS TraceTRS and TDSTraceFile configuration properties in Chapter 2, “Creating a TRS Library”.
To enable or disable protocol tracing before TRS starts running, set the appropriate properties in the TRS configuration file. See the sections describing the TRS TraceProtocol and ProtocolTraceFile configuration properties in Chapter 2, “Creating a TRS Library.”
You can also use DirectConnect Manager to enable and disable tracing while TRS runs.
