On AIX XCOM can transmit files as administrator user root but not as application user user1 and receive error:
XCOMU0436E TP ended abnormally
For example:
# xcomqm -D000033 ===== CA XCOM Data Transport transfer record =====
Transfer ID..................: 000033
Start time...................: Thu Nov 21 13:55:17 2024
Transfer type................: Send file
Local file...................: /usr/test/report1.csv
Remote file..................: \\server1\XCOMXFER\report1.csv
Initiated by.................: LOCAL site
Remote System................: server1
End time.....................: Thu Nov 21 13:55:17 2024
TP pid.......................: 14024952
Owned by user................: user1 from group users
Current Condition............: DONE
Current Status...............: ABENDED
Current TP state.............: XCOMU0152I LOCAL_SEND
Message......................: XCOMU0436E TP ended abnormally.
XCOM™ Data Transport® for UNIX - Release 11.6
XCOM™ Data Transport® for Linux - Releases 11.6, 12.0
XCOM™ Data Transport® for Windows - Releases 11.6, 12.0 (error would be XCOMN0436E)
From the nature of the remote file being a UNC format shared drive the remote system server is running XCOM for Windows.
The error XCOMU0436E containing the 'XCOMU*' (UNIX) seems to indicate a problem on the sending side rather than on the remote Windows system which would return a 'XCOMN*' message.
Initial trace files from setting XTRACE=10 on the xcomtcp command did not show any helpful diagnostic information and the transfer just stopped here after a queue entry was successfully created:
*** ...
MakeQfileName() - result=/opt/CA/XCOM/Q/000039.MBR
security.c 2416: Change owner for file /opt/CA/XCOM/Q/000039.MBR, to user=5078 group=208
xfree: (12) freeing 1100ca890
dummy debug_leak_delete for 1100ca890
fsmachin.c 3962: Setting local userid 5078 and group 5050
security.c 2465: getpwuid() from user 0 ok for uid=5078, gid=5050
security.c 2474: Xsetuid: ruid=0, euid=0, rgid=0, egid=208,
security.c 2486: Successfully set group list via initgroups for
security.c 2526: About to call setegid()
***
Only after setting XTRACE=10 in the file $XCOM_HOME/config/xcom.glb and restarting the xcomd service was useful information found after a transfer failure.
The trace files had some lines about certain activities not being allowed and after checking the eTrust Security app being used the end user found it was blocking.
After the relevant support team enabled those activities the XCOM file transfers started to work.