The Log Options tab displays the attributes associated with the log for all data sources. It also contains the name of the file, the PROCESS ID, and the type of trace that is appended to the data set name. For example, if the log file name were set to a value of “winxp.log” in the Log File Name field and the Client Trace check box for ODBC were selected. The actual file name would be “winxp.xxxxxxxx.odbc.log, where xxxxxxxx is the process ID.
Follow these steps:
The Log Options dialog appears.
The types of traces available include:
Traces all of the similar in format ODBC API calls to the Microsoft ODBC trace in format layout.
Shows the operations of steps necessary to format and prepare a request from the code in CADCDB32 or CADCDB64 as each step in the process to prepare an ODBC or JDBC request to be shipped to the mainframe server.
Traces only the CCI or TCP/IP interface calls. It does not provide CCI tracing but rather the information that is used to build CCI and TCP/IP requests.
Traces only the JDBC API calls. If a more robust trace is desired for JDBC, there are trace facility options embedded in JDBC code that allow for additional tracing. This is only valid if NOJIN=false is set. Otherwise this option is ignored.
Provides statistics for each round trip to the mainframe.
Provides timing for each round trip to the mainframe.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|