Diagram
This parameter specifies whether target files should be created with a prefix such as "~" and have to be renamed to the target file name after the file transfer has been completed without errors. This mechanism is useful if the target directory is monitored for incoming files by an application such as JobScheduler and if files are required to appear atomically - i.e during transfer - instead of being shown after transfer has been completed. The value of this parameter is the temporary prefix. This parameter specifies whether target files should be created with a suffix such as "~" and have to be renamed to the target file name after the file transfer has been completed without errors. This mechanism is useful if the target directory is monitored for incoming files by some application and if files are required to appear atomically instead of being subsequently written to. This setting is recommended should target directories be monitored by an application or the JobScheduler. The value of this parameter is the temporary suffix. 
Atomicity - AtomicityType
Element
Type
Required
Description
AtomicPrefix
string
Optional
Notes
AtomicSuffix
string
Optional
Notes
Explanations
Atomicity can be useful when transferring files when the transfer target directory is being monitored by an application such as the JobScheduler, which will then start further processing of the file.
To avoid the possibility of further processing being started while the file is still being transferred, an atomic prefix and/or suffix are added to the file name at the target system and are selected so as to mask its presence from the monitoring system file name filters.
File transfer itself occurs under the file's original name.
Atomic prefixes and/or suffixes are used in Transactional transfer.