Turning on the internal TCP/IP trace for CA XCOM for AS/400 i5/OS r11 SP1

Products

• XCOM Data Transport

Issue/Introduction

This is a summary of how to use the CA XCOM internal TCP/IP trace. This may only be turned on for all remote TCP transfers at once. The TCP tracing is logged in QPRINT spool files.

 

Environment

Release:  r11 SP1 or higher

Component: XCAS4R

Resolution

How to turn on the Trace
You can use the parameter TCPTRACE(*ON) to start CA XCOM internal TCP/IP tracing with the following commands:

• When starting a TCP/IP listener (STRXCTCP, STRXCTCPS, STRXCTCP6, or STRXCTCP6S)
   
• When issuing a transfer command (SENDFILE, GETFILE, SENDJOB, or SENDREPORT)

Where to find the Trace

• When tracing a listener, output is generated for the listener and all its worker jobs.
   
• When tracing a transfer command, trace output is generated in the job where the CA XCOM file transfer is run, as follows:
  • For a foreground transfer (parameter ENQ(*NO)) this is the current job.
     
  • For a background transfer (parameter ENQ(*YES)) this is one of the background jobs XCOMBGxx in the XCOM2SBS subsystem.

Turning off the Trace

• This is for the listeners. Issue a stop for the listener, for example, STPXCTCP OPTION(*IMMED), and restart it normally with the parameter STRXCTCP TCPTRACE(*OFF).

Additional Information

For more information about using CA XCOM internal TCP/IP tracing, please see the section CA XCOM Internal TCP/IP Tracing in our online documentation.