Transfer processing

A transfer is a set of processes that result in the exchange of data between systems, where one system is the source and the other is the target. This type of data exchange between applications is a flow.


In Central Governance, you can create and deploy flows, which are triggered at the system level.

Transfer CFT provides a complete processing workflow that includes transfer processing, pre- and post-processing scripts, error scripts, and acknowledgment script execution. For more information on defining these in your flow, see Source processing and Target processing scripts.

The transfer processing configuration fields help to define transfer operations. The following fields include information on the user executing the transfer, sending groups of files, running scripts during the flow, and other general processing options.

Multiple steps are required to define a flow. For more information, see:


The user interface indicates default values.

User for file access

Account used to read/write the files to be transferred.

  • Transfer CFT system account - To read and write files, the Transfer CFT uses the same system account that launched the Transfer CFT.
  • USERID variable - The user is set at runtime when performing a transfer. For example, the user is the one defined in the CFTUTIL utility SEND or RECV command. On the sender side, the system user who initiates the SEND is used to execute the end-of-transfer procedure by default. On the receiver side, the USERID is specified in the corresponding CFTRECV object. This gives the user referenced by the user ID the rights to execute end-of-transfer procedures.

If you select USERID variable, you must define rights for the account on the Transfer CFT. To enable system users in Unix or Linux, use the CFTSU process and give special rights to the CFTSU executable. Log on as root and execute the following commands:

  • chown root:root $CFTDIRINSTALL/bin/CFTSU
  • chmod u+s $CFTDIRINSTALL/bin/CFTSU

User for script execution

Transfer CFT can execute scripts as the system user or on behalf of another user as defined by the USERID option.

This field is not supported on Transfer CFTs running on z/OS computers.

  • Transfer CFT system account - Transfer CFT executes the script as the system user.
  • USERID variable - Transfer CFT executes the script on behalf of another defined user, other than the system user.

For an unknown flow

Action to take when the flow is unknown.

Use the system default - The transfer is performed using the default flow identifier.

Reject request - No transfer occurs when the flow is unknown and an error code and message is returned in response to the CFTUTIL utility SEND and RECV commands.

Transmit files individually

Indicates whether the transmission of a group of files is done individually, file by file, or grouped when possible.

The method for transmitting the group of files depends on the operating systems of the Transfer CFTs involved in the flow, and their configurations.

  • When  necessary - When the source and target systems have the same operating system, you can send multiple files as an archive file.
  • Always - Select this option when you are certain that the operating systems are different. In this case, the transfer always sends files individually for each file in the group. Note that when using the Always option, Transfer CFT transmits files individually even if the operating systems are the same.

See Transferring groups of files.

Select Always if uncertain about the transfer point platform. For example, a Windows system archives a group of files as a ZIP file, but a receiving UNIX transfer point expects the TAR file format. In this case, an error occurs on both sides.

When requesting all files

Action to perform if any one of the transfers fails.

Defines the desired behavior when a Transfer CFT requests all available files from another Transfer CFT.

  • Stop on error - The file reception stops at the first error. For example, if there are 10 files to send and an error occurs while transferring the third file in the group, then the remaining files (4 through 10 in our example) are not transferred.
  • Continue - When using this option, Transfer CFT continues with the request for the remaining files (4 through 10 in our example) even though it did not receive the third file.

On error when transferring multiple files

Defines the policy for a group-of-files type of transfer if there is an error.

  • Continue transfer (default): Keep the existing behavior, which creates as many transfer requests as there are lines in the input file.
  • Abort transfer: If the input is not a file, this gives the current transfer aborts and no other child requests are created.

When file exists


Defines the target retry characteristics for the file renaming functionality when the file exists.

  • Retry frequency - Delay in seconds between two retries to rename the file. If the file is not successfully renamed after the first delay, the time doubles for the next retry period.
  • Maximum number of retries - Maximum number of retries.

Default scripts

The following describes the types of processing scripts you can specify on the source and target.

When configuring default scripts you can specify an existing script on the Transfer CFT or upload a new script to it.

If you upload a script file, it is available on the Transfer CFT after the configuration is deployed successfully on it. The script is uploaded with the default path:


The new file overwrites an existing file if present.

Select None if a processing script is not needed.


You can specify for the transfer source:

  • Post-processing: the script to run after a file is sent.
  • Acknowledgment: the script to run after an acknowledgment is received for a sent file.
  • Error: the script to run after an error occurs when sending a file.
  • None: no script for any category.

For more information, see Transfer CFT source fields in flows.


You can specify for the transfer target:

  • Post-processing: the script to run after a file is received.
  • Error: the script to run after an error occurs while a file is received on the target.
  • None: no script for these categories.

For more information on defining targets, see Transfer CFT target fields in flows.


Central Governance | Document Directory

Related Links