Template Name

Defines the name of the MVS template that is defined in MVS File Template Management, as described in MVS file template management.

Load

Loads the name of the MVS template that is defined in MVS File Template Management.

Record Format

Determines the value for the record format.

Logical Record Length

Determines the logical record length values between 0-32760.

Block Size

Determines the block size values between 0-32760.

Translate Table

Determines what table is used by the FTP server during transfer for translation (8 characters maximum or select from list).

If you want to add or delete values to and from the list, you need to add them as comma separated values, to the XLT.dat file in the following location:

<Control-M/Agent_Directory>/cm/AFT/data

DBCS Encoding

Determines which DBCS data sets are used for the transfer.

Allocation Units

Determines which allocation unit type is used for the transfer.

Volume

Defines the volume value (6 characters maximum).

Unit

Defines unit value (8 characters maximum).

Primary

Defines the primary allocation amount between 1-16777215.

Secondary

Defines the secondary allocation amount between 0-16777215.

Transfer Mode

Determines the mode used to transfer files:

• Block: Transfers the file as a series of data blocks preceded by one or more header bytes.
• Stream: Transfers the file as a stream of bytes.

SMS Management Class

Determines which SMS Management Class is assigned to a new data set.

SMS Data Class

Defines the SMS Data Class provided by your organization for the FTP server.

Additional Options (Host1, Host2)

Defines MVS FTP Server SITE command sub-parameters and values (214 characters maximum).

To work with GDG data sets, type: DCbdsn=model_dataset_name.

Transfer to unique file

Creates a file with a unique name on the remote system instead of overwriting an existing file. The FTP server on the remote system sends the name of the created file back to the MFT client.

When you select this option, you cannot do any of the following:

• Use a temporary prefix for the destination file
• Rename the destination file
• Rerun from point of failure