Explanation and recovery from xcomd return codes for service specific errors 473, 474, 651, 652, 1060 and 1067 when starting xcomd.
Release: XCOM Data Transport Windows, Linux
Component: xcpcnt, xclx86
473 - problems parsing xcom.glb or xcom.tid. (Also see additional information below)
NOTE: Run xcomqm -r from the \xcomnt directory to check the syntax of xcom.glb.
474 - xcomd is already running
If there is still a problem, force down xcomd with xcomd -cy and start it again. NOTE: Never use xcomd -cy for normal shutdown
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. Warning: This will remove any pending transfers.
1067
NOTE: reinstalling the product will clear up the problem in many cases.
Also please see KD4011