File Transfer (JOBF) from Windows Agent fails when wildcards and multi-backslashes are used

Document ID : KB000084548
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
-------------------------------------JOBF WIN to WIN -------------------------------------------------- 
U00011124 Selection started with filter 'C:\temp\\*.DAT' ... 
U00011125 'C:\temp\Test_JOBF.dat' 
U00011126 Files selected: '1'. 
(Win to win) U00011134 ERROR '0' bytes, incorrect transfer of '0' records for file 'C:\temp\Test_JOBF.dat'->''. Duration '00:00:00' 
U00063009 FileTransfer '1593043' not found. 
U00011409 FT '1593043': FileTransfer ended abnormally. 
------------------------------------------JOBF WIN TO UNIX--------------------------------------------- 
U00011124 Selection started with filter 'C:\temp\\*.DAT' ... 
U00011125 'C:\temp\Test_JOBF.dat' 
U00011126 Files selected: '1'. 
(Win to Unix) U00011134 ERROR '0' bytes, incorrect transfer of '0' records for file 'C:\temp\Test_JOBF.dat'->'dest. filename unabled to convert'. Duration '00:00:00'. 
U00063069 Unable to convert filename, mask 'C:\temp\\*.DAT' does not match with filename 'C:\temp\Test_JOBF.dat'. 
U00011409 FT '1593038': FileTransfer ended abnormally. 
--------------------------------------------------------------------------------------- 

A JOBF on a Windows Agent v11.2 encounters an "Unable to convert file name" error when the source Agent is Windows and the path contains double backslashes ("\\")  in the source path. 

This error can also result if wildcards are used in the path.

Double backslashes can be used in the destination paths without issue (if the source path is appropriately configured). 

Cause:
Cause type:
By design
Root Cause: Double backslashes or wildcards in source paths are not supported.
Resolution:
Since using double backslashes or wildcards in a source path is not supported by design, ensure that no double backslashes are used inside the path in the JOBF and/or script.

Fix Status: No Fix

Additional Information:
Workaround :
Revise the scripts to make sure there are no double backslashes in the source path and that any wildcards are disabled.