I do not know about the CA XCOM software that you refer here.
But if it behaves like most other services that run on linux, then probably this type of error can occur if the service was not previously not cleanly stopped. In such a case a previous 'pid' file that stores the process id still exists.
If the 'xcomd' has a stop or shutdown option then try that option first and then try starting it again.
Alternatively, you can try to manually try to move (or delete) the corresponding pid file out of the way. A rough guess for the name and location for this pid file would be /var/run/xcomd.pid. If the xcom.pid file has 7618 stored in it and you are sure that process no longer runs, then remove the pid file and try starting it up again.