File transfer with special character in the file name fails with XCOM for Windows
search cancel

File transfer with special character in the file name fails with XCOM for Windows

book

Article ID: 138850

calendar_today

Updated On:

Products

XCOM Data Transport XCOM Data Transport - Windows XCOM - SUPPORT

Issue/Introduction

We encounter a problem when trying to transfer a file with the following name which contains a special character.  The following happens:

"C:\Program Files\CA\XCOM"\XCOMTCP -f "C:\Program Files\CA\XCOM"\CONFIG\PtoPXcom.xml REMOTE_SYSTEM=ipname LOCAL_FILE="c:\temp\2019-8-31 ORG PUB*" REMOTE_FILE=D:\temp\* CODE_FLAG=BINARY QUEUE=NO FILE_OPTION=REPLACE xtrace=10

TID=217508 [c:\temp\2019-8-31 ORG PUB* --> D:\temp\* at <IP Address>]

XCOMN0029I Locally initiated transfer started.

TID=217508

XCOMN0011I Transfer ended; 16 records (470781 bytes) transmitted in 2 seconds (235390 bytes/second)

  • source file:  2019-8-31 ORG <file name>° (1098).pdf
  • destination file: 2019-8-31 ORG <file name>

After transferring the file,  the name is not complete and leaves it without extension.   When you try to open the said file, it cannot and shows it as damaged.   

The same source file, the name is modified by removing the special character "°" and the transfer is successful.

Environment

XCOM™ Data Transport® for Windows

Cause

The cause is due to the double byte character being used on the file name.

Resolution

XCOM does not support file names with double byte characters at this time.