CA XCOM file transfer across Windows servers shows different values for MD5 Hash (checksum) for the source and destination files.

book

Article ID: 197590

calendar_today

Updated On:

Products

CA XCOM Data Transport CA XCOM Data Transport - Windows XCOM - SUPPORT

Issue/Introduction

Have recently installed XCOM 11.6 SP3 for Windows on 2 Windows servers.
File transfer is happening successfully without any error.
However, the MD5 hash (checksum) for the file transferred to the remote destination doesn't match the MD5 hash for the original local source file.

Cause

If the file is not transferred in BINARY mode, XCOM may perform various processing on the file i.e. record processing, delimiter translation, encoding translation, etc, which could result in different MD5 hash (checksum) values for the local file and the remote file.

Environment

Release : 11.6
Component : CA XCOM Data Transport for Windows

Resolution

To ensure the destination file is completely unchanged from the source file after the transfer set parameter "CODE_FLAG=BINARY" via .cnf file or command-line parameter:
CA XCOM DATA TRANSPORT FOR WINDOWS 11.6 SERVICE PACKS > Administrating > How to Configure CA XCOM Data Transport > XCOM.CNF Parameters > CODE_FLAG

Additional Information

A binary transfer can also be fine-tuned to give better performance with higher MAXRECLEN and CKPT (CHECKPOINT_COUNT) values:
CA XCOM DATA TRANSPORT FOR WINDOWS 11.6 SERVICE PACKS > Administrating > How to Configure CA XCOM Data Transport > XCOM.CNF Parameters > MAXRECLEN
CA XCOM DATA TRANSPORT FOR WINDOWS 11.6 SERVICE PACKS > Administrating > Reference > List of Parameters > CKPT
CA XCOM DATA TRANSPORT FOR WINDOWS 11.6 SERVICE PACKS > Administrating > How to Configure CA XCOM Data Transport > XCOM.CNF Parameters > CHECKPOINT_COUNT