CA XCOM scheduler xcomd fails with "ERROR: Could not open file 'xcom.glb' for reading (access denied)"
Article ID: 130592
Updated On:
Products
CA XCOM Data Transport
CA XCOM Data Transport - Windows
CA XCOM Data Transport - Linux PC
CA XCOM Data Transport - z/OS
Issue/Introduction
CA XCOM 11.6 scheduler xcomd fails to start with following error:
ERROR: Could not open file 'xcom.glb' for reading (access denied).
2019/04/03 12:03:23 PRG=xcomd PID=8599
XCOMU0473E Error(s) parsing xcom.glb; xcomd cannot start.
Script FAILED: Starting XCOM daemon
The file xcom.glb is owned by the root user and has permissions -rwxrwxrwx
ERROR: Could not open file 'xcom.glb' for reading (access denied).
2019/04/03 12:03:23 PRG=xcomd PID=8599
XCOMU0473E Error(s) parsing xcom.glb; xcomd cannot start.
Script FAILED: Starting XCOM daemon
The file xcom.glb is owned by the root user and has permissions -rwxrwxrwx
Cause
The XCOM code does not directly use directory "/opt/CA/XCOM/config" to locate the xcom.glb file. Rather it uses symbolic link "/usr/spool/xcom/config -> /opt/CA/XCOM/config" to locate the file. It was found that the symbolic link was missing.
Environment
XCOM 11.6
Red Hat Enterprise Linux 7.6
Red Hat Enterprise Linux 7.6
Resolution
After creating the symbolic link "/usr/spool/xcom/config" the xcomd startup problem was resolved:
ln -s /opt/CA/XCOM/config /usr/spool/xcom/config
ln -s /opt/CA/XCOM/config /usr/spool/xcom/config
Feedback
Powered by
