TRS does the following:
Receives requests from client applications
Converts the requests to the appropriate communications protocol call
Sends the requests to the mainframe
Each instance of TRS has a unique service name, which clients use to select a service for communication. Each instance of TRS has its own set of configuration information, defined globally in the TRSL configuration file.
As shown in the previous figures, TRS uses the following files:
<srvlibname>.tds for tracing Sybase TDS traffic between TRS on UNIX platforms and mainframe SNA
ngtds.<srvlibname> for tracing Sybase TDS traffic between TRS on PC platforms and mainframe SNA
svr.log for logging TDS traffic between TRS and client workstations, and for recording errors
The Transaction Router Service Library (TRSL) SNATraceFile configuration property specifies the file to which the SNA side of the TRS trace file is written. Formatted TDS traces and errors are logged and written to this file.
The associated TRSL name is appended to these files so that the TRS administrator can differentiate the log for each instance of TRS. For more information, refer to the Mainframe Connect DirectConnect for z/OS Option Users Guide for Transaction Router Services.
The DirectConnect for z/OS Option server logs TDS traffic between TRS and client workstations, and records errors. For more information, refer to the Enterprise Connect Data Access and Mainframe Connect Server Administration Guide.
