|
|
|
The tracing parameters are used to collect information at the request of CA XCOM Data Transport Customer Support in order to diagnose a problem. The trace output is primarily intended to provide information to Customer Support, and they will usually request a level of tracing for you to use. The -t option of the XCOM62 or XCOMTCP command will direct trace output to STDERR, the standard error output.
This trace facility collects information about a transfer from the point where a transfer is queued or submitted and a connection is established. The resulting trace data is stored in a file named TIDNUMBER.TRA, where TIDNUMBER = the transfer ID.
Note: In the GUI, the Trace section of the Global Parameters tab provides access to CA XCOM Data Transport system-level trace facilities. For more information, see the chapter "Using CA XCOM Data Transport."
Note that setting trace options may generate large files of trace data and significantly impact performance.
Example 1:
In the following example, the XCOM62 command is used. The configuration file is MYCONFIG.CNF, the trace level is set to 10 to provide full tracing information and the trace information is written to a trace file.
XCOM62 -f MYCONFIG.CNF XTRACE=10
Example 2:
In the following example, the XCOMTCP command is used.
XCOMTCP -f MYCONFIG.CNF XTRACE=10 PROTOCOL=TCPIP
The configuration file is MYCONFIG.CNF, the trace level is set to 10 to provide full tracing information and the trace information is written to a trace file. The protocol is specified by the PROTOCOL parameter.
| Copyright © 2012 CA. All rights reserved. |
|