WHAT DO THE ERROR CODES MEAN WHEN STARTING XCOMD?

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

Question:

What do the error codes mean when starting XCOMD service?

Answer:

Return codes for service specific errors (473, 474, 651, 652, 1060, 1067) when starting xcomd.

473 - problems parsing xcom.glb or xcom.tid.
Make sure parameters (except paths, userids and passwords or anything that must be lower case) are in upper case.
Make sure the drive letter is specified correctly for paths.
Make sure there are no extraneous blank lines.
Make sure that all comments are validly commented out.
Make sure there are not extraneous characters on a line.
Make sure that all parameters are valid for the release and are spelled correctly.
Make sure xcom.tid contains a non-zero 6 digit number. This is your next transfer id number.

NOTE: Run xcomqm -r from the \xcomnt directory to check the syntax of xcom.glb.

474 - xcomd is already running

651 - Indicates errors in setting the PROTOCOL= and TP_CMD parameters. If you are using the TCPIP protocol only and did a "typical" install, set

PROTOCOL=TCPIP
TP_CMD=

There should be nothing on the line after the = sign until the carriage return. Do not comment it out. Your .cnf files should not have PROTOCOL=SNA.

If you get this error and SNA is installed, the SNA stack must be installed and running to bring up xcomd. Check that environment variables are set up properly for your APPC (if required).

652 - XCOM cannot find SNA. Check the registry.

1060 - Corrupted member(s) in xcomnt\Q directory. Delete *.MBR and *.IDX files in xcomnt\Q directory and stop and start xcomd. NOTE: This will remove any pending transfers.

1067 - The TP_CMD parameter is not set to the correct path. Invalid parameter in xcom.glb.
Missing required parameter in xcom.glb. parameter= with no value (if required).
NOTE: reinstalling the product will clear up the problem in many cases.