Large XCOM file transfer from Linux to Mainframe ends abnormally

Products

• XCOM Data Transport
• XCOM Data Transport - Linux PC
• XCOM Data Transport - Windows
• XCOM Data Transport - z/OS

Issue/Introduction

Trying to use XCOM to transfer a file containing 5 million records from Linux to Mainframe but Mainframe side is not receiving the entire file.
The file is successfully transferred if it has less records i.e. 3 to 4 million. 
XCOM for Linux 12.0 is being used i.e.

# xcomd -r
xcomd: CA XCOM Data Transport r12.0 23010 SP00 64bit (for <no SNA support>)

Cause

In the xcom.log file, 26 minutes after transfer starts ("XCOMU0786I TCP/IP Connection Established"), this message is seen:
XCOMU0309E Error reading local input file : No space left on device

Therefore the root cause appears to be due to a file system filling up.

The transfer .cnf file being used shows parameter XTRACE=8.
Having XTRACE=8 would explain the problem because a large trace (*.TRA) file would be created in directory $XCOM_HOME/trace which is the default location for the TRACE_PATH parameter (parameter value also confirmed in the provided file xcom.glb) i.e. the large trace file would cause the XCOM file system to gradually fill up until it reaches capacity 26 minutes into the transfer.
That trace file will get deleted after the EXPIRATION_TIME in xcom.glb has passed. EXPIRATION_TIME is set to 3000 which equates to 50 minutes.
Therefore depending on when this transfer occurs if no-one is checking the file system space at the time of the transfer or within an hour of the transfer ending, by the time it is checked later the trace file would have been deleted and the XCOM file system could look healthy.

Resolution

Change XTRACE=8 to XTRACE=0 in the transfer .cnf file.