xcom.log file not showing all expected messages for remotely initiated file transfer

Products

• XCOM Data Transport
• XCOM Data Transport - Windows
• XCOM Data Transport - Linux PC

Issue/Introduction

Our xcom.log file shows the full xcom transfer messages on some of the servers while not on some others (XCOM transfer works on all servers regardless).
In below examples Server1 xcom.log only shows the initial message for the remote connection (XCOMU0793I Remote TCP/IP Connection Established.XCOMU0793I) while Server2 xcom.log shows the additional XCOMU0026I, XCOMU0805I and XCOMU0011I messages.

Transfer initiated to both servers as below.

$ ./sendXCOM_FP.sh
2019/11/27 14:08:51 TID=113618 [/home/user/tt.txt --> /tmp/test.txt at server1]

    XCOMU0029I Locally initiated transfer started.

2019/11/27 14:08:51 TID=113618

    XCOMU0011I Transfer ended; 1 blocks (6 bytes) transmitted in 0 seconds (6 bytes/second)


2019/11/27 14:08:55 TID=113622 [/home/user/test.txt --> /tmp/test.txt at server2]

    XCOMU0029I Locally initiated transfer started.

2019/11/27 14:08:55 TID=113622

    XCOMU0011I Transfer ended; 1 blocks (6 bytes) transmitted in 0 seconds (6 bytes/second)

Server1 xcom.log file:
2019/11/27 14:08:55 TID=REMOTE PRG=xcomtcp PID=3833 IP=xxx.xxx.xxx.xxx
    XCOMU0793I Remote TCP/IP Connection Established.

 
Server2 xcom log file:
2019/11/27 14:08:51 TID=REMOTE PRG=xcomtcp PID=27953 IP=xxx.xxx.xxx.xxx
    XCOMU0793I Remote TCP/IP Connection Established.

2019/11/27 14:08:51 TID=139977 [/home/user/test.txt at xxx.xxx.xxx.xxx --> /tmp/test.txt]
    XCOMU0026I Remotely initiated first try.

2019/11/27 14:08:51 TID=139977 PRG=xcomtcp PID=27953 IP=xxx.xxx.xxx.xxx
    XCOMU0805I TCP/IP Connection Ended.

2019/11/27 14:08:51 TID=139977
    XCOMU0011I Transfer ended; 1 blocks (6 bytes) transmitted in 0 seconds (6 bytes/second)

Environment

• XCOM™ Data Transport® for Windows
• XCOM™ Data Transport® for Linux PC

Cause

These symptoms can occur when the xcom.log permissions are not correctly set for the local USERID being used in the remote transfer command.

Resolution

The local USERID used to transfer the file did not have permissions to write to the xcom.log life.
After updating the permissions for the /opt/CA/XCOM directory and /opt/CA/XCOM/xcom.log file, the problem was resolved.