Naming Convention for Temporary files during UC4 Automic File Transfer
search cancel

Naming Convention for Temporary files during UC4 Automic File Transfer


Article ID: 260200


Updated On:


CA Automic Workload Automation - Automation Engine CA Automic One Automation


What is the logic behind the naming of the temporary files while using UC4 File transfer?


Release : 12.x 21.x

Component: Automation Engine

Functional Area: UC4 File transfer (JOBF)


When transferring large files from one agent to another using JOBF - Automic creates a .tmp file until the transfer is in progress - Once the entire file is copied then it automatically renames it to the desired name as per the settings on the file transfer object. 

Note: This applies only if the file is not already present in the destination location.


Linux as Destination:

In the destination linux machine uc4 creates a tmp file with the extension .tmp (example)

-rw-r--r--. 1 automic automic 231220274 Feb 16 15:34 TAADBIDU_0.tmp 

The name of the file is the alphabetic representation of the run-id  (This can be converted to a run-id using the script functionALPHA2RUNNR )

So TAADBIDU_0.tmp translates to the runid of the filetransfer execution

[ Example Below ]

Run the below script to translate the .tmp name to the corresponding run-id 

:SET &ALPHA# = MID("TAADBIDU_0.tmp", 2, 7)



The returned results are as seen below - This is the corresponding run-id of that execution 

2023-02-16 16:18:21 - U00020408 RunID: 0000000001394010


Windows as the Destination:

The rationale behind the windows temp naming convention is similar to the Unix agent - So the .tmp filename is the file-transfer id (run-id) just converted to B26 form + '_fileId.tmp'"  (example below )