Different values for checksum for the source and destination files for XCOM for Windows

Products

• XCOM Data Transport
• XCOM Data Transport - Windows

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.

Environment

XCOM™ Data Transport® for Windows

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.

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:
XCOM DATA TRANSPORT FOR WINDOWS 12.0 > Reference > List of Parameters > 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:
MAXRECLEN
CKPT
CHECKPOINT_COUNT