How to Trace Transfers with CA XCOM Data Transport for z/OS


Article ID: 15147


Updated On:


CA XCOM Data Transport CA XCOM Data Transport - z/OS


How to turn on tracing for CA XCOM for z/OS.


Release: XCOM Data Transport-for z/OS
Component: xcmvs


To trace TYPE=EXECUTE batch transfers
     use TRACE=YES in the XCOMJOB PARM.
     for example,   PARM='TYPE=EXECUTE,TRACE=YES'

The trace is written to the output of the XCOMJOB.

NOTE: This is the only way to trace TYPE=EXECUTE transfers on the sending side.  On the receiving side, use the console command and trace the specific destination.

To trace the TYPE=SCHEDULE only
     for example, PARM='TYPE=SCHEDULE,TRACE=YES'    Note this traces the schedule to the server only,  not the transfer itself.

The trace is written to the output of the XCOMJOB.


For TYPE=SCHEDULE and ISPF transfers, use the console modify command and specify TRACE to turn tracing on and NOTRACE to turn tracing off

 To trace all transfers:

        F xcomstc,trace,*   

      This will trace EVERYTHING in the server, so it would be best to do it at an off time, or (even better) use a test server with no other transfer activity  going on.

 To trace a specific destination

This will trace only activities between the server and the partner at nnn.nnn.nnn.nnn IP address. 

        F xcomstc,trace,ipname (or address)     to trace a transfer to a specific IP destination only

        NOTE: To enable tracing for a specific IP partner,  you must have 12.0 PTF RO96651 SELECTIVE TRACING BY IP ADDRESS NOT WORKING CORRECTLY

       F xcomstc,trace,luname                        to trace a transfer to a specific LU only

    where xcomstc is the xcom started task name

XCOM opens a TRACE DD in output of the server job.

To terminate all tracing 

/F xcomstc,NOTRACE,* 

or specify the remote destination to turn off tracing selectively.


Additional Information

Documentation for CA XCOM Data Transport for z/OS 12.0