How to Take an XCOM Trace with CA XCOM Data Transport for z/VSE?

Products

• XCOM Data Transport

Issue/Introduction

Taking an XCOM trace if you are submitting an TYPE=EXECUTE transfer or TYPE=SCHEDULE transfer.

Environment

Release: CA XCOM Data Transport for z/VSE
Component: XCVSE

Resolution

For TYPE=EXECUTE transfers

1. Specify TRACE=YES as a PARM on the XCOMJOB statement
   
   
2. The trace will be written into the output of the job
   
   NOTE: if you specify TRACE=YES as a PARM on the XCOMJOB statement while performing a TYPE=SCHEDULE transfer, you will take a trace of the transfer being scheduled to the XCOM server.

For TYPE=SCHEDULE or Incoming Transfers

XCOM Operator Commands are used to turn the XCOM trace on and off

Make sure that

// ASSGN SYS001,02E -*- TRACEDD  

is specified in the XCOM JCL.

1. Enter the operator command:
   
   MSG Fx,DATA=TRACE[,{*|luname,[SNA]|ipname}] Fx indicates the partition number.
   
   Examples:
   
   MSG Fx,DATA=TRACE Traces all transfers. The * does not need to be specified.
   MSG Fx,DATA=LU Traces all transfers only for the LU specified. [SNA] is required only in cases where the ipname and ip address are the same.
   
   MSG Fx,DATA=ipname Traces all transfers only for the ipname or ip number specified.
   
   NOTE: The trace function dynamically allocates a SYSOUT file to receive the trace data. This SYSOUT file's class is defined by the DUMPCL parameter of XCOM Default Options Table. It can be overridden in the EXEC PARM of the XCOM task.
   
   
2. After reproducing the problem, turn off the trace with:
   
   MSG Fx,DATA=NOTRACE[,{*|luname|ipname}] To turn off a specific trace
   or
   MSG Fx,DATA=NOTRACE To turn off all tracing
   
   NOTE: NOTRACE causes the TRACEDD spooled output to be segmented and thus be immediately available for print or other processing.

Additional Information

See the XCOM Data Transport for z/VSE Administrator Guide