XCOM for Linux/UNIX successful transfers end with return code 3

Products

• XCOM Data Transport
• XCOM Data Transport - Linux PC

Issue/Introduction

Why do successful XCOM transfers initiated from a Linux/UNIX server with return code 3 (RC=3) instead of return code 0 (RC=0)?

Environment

XCOM™ Data Transport® for UNIX/Linux PC

Cause

If an XCOM program is copied from one directory to another then the sticky bits are removed.

Resolution

After installing XCOM on Unix the program xcomtcp has the so-called “Sticky Bits” SETUID and SETGID assigned. This "ls -la" command shows these bits as ‘s’:

/opt/CA/XCOM/bin> ls -la xcomtcp
-r-sr-sr-x 1 root root 1752097 18. Aug 11:31 xcomtcp

If the xcomtcp program is copied into this directory from another place then SETUID and SETGID are removed. Program xcomtcp still executes successfully but the return code (RC) displayed with command “echo $?” shows 3 instead of 0.

If the bits SETUID and SETGUID are missing for xcomtcp, login as root and use this command to restore them:
chmod 6555 /opt/CA/XCOM/bin/xcomtcp


Additonal programs:

Program xcomqm only has the bit SETGUID set. If that is missing login as root and use this command to restore it:
chmod 2555 /opt/CA/XCOM/bin/xcomqm

If the bits SETUID and SETGUID are missing for xcomd, login as root and use this command to restore them:
chmod 6550 /opt/CA/XCOM/sbin/xcomd

Additional Information

NOTE: If this behaviour occurs on an AWS EC2 Cloud server the problem may be due to other factors.
See related article: XCOM for Linux successful transfers end with return code 3 (AWS EC2 Cloud)