XCOM for Windows DOMAIN parameter precedence
search cancel

XCOM for Windows DOMAIN parameter precedence

book

Article ID: 225992

calendar_today

Updated On:

Products

XCOM Data Transport XCOM Data Transport - Windows

Issue/Introduction

For incoming transfers, it is required to set the DOMAIN parameter on the receive server xcom.glb file so that parameter is automatically set and thus avoid existing partners having to set it on their command line when sending files to that server.
However for outgoing transfers from the same server that DOMAIN parameter should not be set because it may cause problems at the receive server due to the DOMAIN parameter not being recognised or that server already having it set in its xcom.glb to be used as the default.
What are the options to stop the DOMAIN parameter being set for outgoing transfers?

Environment

Release : 11.6

Component : CA XCOM Data Transport for Windows

Resolution

For outgoing transfers support tested with the XCOM initiate server having DOMAIN parameter set in its xcom.glb and the XCOM receive server first not having it set and then having it set. Tests done using a transfer .cnf file but the same results are valid for direct command line parameter use:
a. XCOM initiate server has DOMAIN parameter set to DOMAIN1 in xcom.glb and XCOM receive server has no DOMAIN parameter set in xcom.glb.
 -  If transfer .cnf file has DOMAIN set to no value ("DOMAIN=") then the trace file at the XCOM receive server shows "domain=<DOMAIN1>"
 -  If transfer .cnf file has DOMAIN set to single space ("DOMAIN= ") then the trace file at the XCOM receive server shows no domain value i.e. "domain=<>"
b. XCOM initiate server has DOMAIN parameter set to DOMAIN1 in xcom.glb and XCOM receive server has DOMAIN parameter set to DOMAIN2 in xcom.glb 
 - If transfer .cnf file has DOMAIN set to no value ("DOMAIN=") then the trace file at the XCOM receive server shows "domain=<DOMAIN1>"
 - If transfer .cnf file has DOMAIN set to single space ("DOMAIN= ") then the trace file at the XCOM receive server shows "domain=<DOMAIN2>"
So setting DOMAIN to a single space ("DOMAIN= ") for the transfer will both override the initiate server xcom.glb DOMAIN value and will itself be overridden by the receive XCOM server xcom.glb DOMAIN parameter if it is set.

Additional Information

Also, see parameter order of precedence referenced in CA XCOM™ Data Transport® for Windows 11.6 Service Packs > Using > Command-Line Interface > How to Create and Use Configuration Files