Previous Topic: Command Examples for Metatransfers and Inquire on Status

Next Topic: Return Codes


Tracing Problems

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 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.

Example 1

In the following example, the xcom62 command is used. The configuration file is /myconfig, the XTRACE parameter is used to set the trace level 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.

xcom62 -c1 -f /myconfig XTRACE=10 PROTOCOL=SNA

This section contains information about collecting information to diagnose problems when requested by CA XCOM Data Transport Customer Support.

Example 2

In the following example, the xcomtcp command is used. The configuration file is /myconfig, the XTRACE parameter is used to set the trace level 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.

xcomtcp -c1 -f /myconfig XTRACE=10 PROTOCOL=TCPIP