How to diagnose a CA XCOM service startup error 473?

Document ID : KB000009444
Last Modified Date : 14/02/2018
Show Technical Document Details

When XCOM service fails to start due to a syntax error, you can use xcomqm -r to get more information.


When XCOM service fails to start, it will write an event log entry of this form:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 11.01.2011
Time: 11:11:11
User: N/A
Computer: myMachine
The XCOMD Unicenter CA-XCOM Scheduler Service terminated with service-specific error nnn (0xhhh).

When the error code is 473 (0x1D9) the service did not start because it had detected a syntax error in xcom.glb
(in case you try to start the service manually you will also see a message indicating the service-specific error code)

In order to find out which line in xcom.glb is wrong, you can use XCOM's queue management tool 'xcomqm' which also does a syntax check on xcom.glb and issues an appropriate message indicating the line in error.

From a Command Prompt Window just issue the command:

xcomqm -r

You will then receive more detailed information on the syntax error, like in this example:
ERROR: In C:\Xcomnt\config\xcom.glb, expecting a valid name, but found 'XLOGFIL'. Check for possible miss spelling.