ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Error: "XCOMU0286E Error setting local user id" initiating from Linux


Article ID: 4831


Updated On:


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


Received message "XCOMU0286E Error setting local user id" when trying to initiate a transfer from Linux. All other Linux systems are working properly. 


The most likely cause of this error is that the xcom binaries are missing their required security permissions. They need to: 

- Be owned by root 

- Be assigned to group xcomadm created during installation 

- have setuid and/ setgid privileges 




XCOM r11.6 12091 for Linux


If you have a working box, you can compare things in order to adjust them in the failing box. 

As an example, in a working box, ls -l shows our binaries this way: 

-r-xr-xr-x 1 root xcomadm 16588 9. Mar 2015 cleanlog 

-r-xr-xr-x 1 root xcomadm 15194052 9. Mar 2015 

-r-xr-xr-x 1 root xcomadm 1501562 9. Mar 2015 

-r-xr-xr-x 1 root xcomadm 2441730 9. Mar 2015 

-r-xr-xr-x 1 root xcomadm 3266836 9. Mar 2015 

-r-xr-xr-x 1 root xcomadm 7582 9. Mar 2015 

-r-xr-xr-x 1 root xcomadm 1083310 9. Mar 2015 xcomencr 

-r-xr-xr-x 1 root xcomadm 1083485 9. Mar 2015 xcomossl 

-r-xr-sr-x 1 root xcomadm 1753915 9. Mar 2015 xcomqm 

-r-xr-xr-x 1 root xcomadm 1085311 9. Mar 2015 xcomsmtp 

-r-sr-sr-x 1 root xcomadm 1752097 9. Mar 2015 xcomtcp 

-r-xr-sr-x 1 root xcomadm 1930341 9. Mar 2015 xcomtool 

-r-xr-xr-x 1 root xcomadm 1094471 9. Mar 2015 xcomtrst 


Just as a reminder in case of need: 

- To change the owner, 'chown root filename' 

- To change the group, 'chgrp xcomadm filename' 

- To set permissions to -r-sr-sr-x, 'chmod 6555 filename' 

- To set permissions to -r-xr-sr-x, 'chmod 2555 filename' 

- To set permissions to -r-xr-xr-x, 'chmod 555 ffilename' 


If this does not help, please do as follows: 

- Add XTRACE=10 to the command line and reproduce the problem 

- Note the numeric TID=nnnnnn in the messages 

- collect file nnnnnn.tra from $XCOM_HOME/trace (which is the TRACE_PATH= set in your xcom.glb 

- Send us the trace file as well as xcom.log file