| Transfer Description
|
Process Name
|
This eight-character field describes the application which is initiating the transfer. As an alternative to an 8 character description the parameter $ (TIME) can be used in this field to give an 8 digit time for the process name.
This field can be used for automating transactions from the Host. See Appendix C Automated Operations of the
MFT Platform Server for z/OS User’s Guide.
|
| User Data
|
Any alpha, numeric or national characters of up to 25 characters that are logged into the history files that decriptive information on the transfer. This field is optional.
This field can be used for automating transactions from the Host. See Appendix C Automated Operations of the
MFT Platform Server for z/OS User’s Guide.
|
| Thread Priority
(Level)
|
Assigns priority to transactions that are executed simultaneously and are competing for resources. This is the priority is assigned when creating the transfer thread. This is not the priority used in the work queue.
The levels of priority that can be assigned are as follows: highest, above normal, normal, below normal, lowest, and idle.
|
| Check Point
Interval
|
Checks Point periodically sends packets of data with the file transfer that inform the receiver of the current point of the file transfer. The receiver takes the latest data received to the file system and records the sender’s checkpoint and its own checkpoint in the persistent queue. In the event of a failure, the initiator and the responder negotiate with the saved checkpoint information and restart from the last known good checkpoint.
The MFT Platform Server for Windows checkpoint uses a time interval to determine when to send a checkpoint. Since Check Point is time-based, the checkpoint always occurs at a regular interval.
Check Point Interval is specified in minutes and is a valid range 1 to 90 minutes.
|
| Compression
|
Compresses data on the sender side of the transfer and decompresses the data on the receiver side of the transfer. This will result in fewer packets being sent between systems, and reduce network traffic. The compression provided by MFT Platform Server for Windows is Smart compression because it removes a level of complexity from the user.
When you compress certain types of data, the compressed data is larger than the original data. Smart Compression solves this problem by transmitting only the data packets which are smaller than the original. This saves the increased network bandwidth of the larger compressed packet and saves the CPU cycles on the receiving side.
This field provides the following compression algorithms:
- LZ (Limpel-Zev): Provides better compression ratios and compresses a wider variety of different data types than RLE. Choose LZ if you need better compression ratios and can spare CPU cycles.
- RLE (Run Length Encoding): More data-dependent than LZ. That is, the compression ratio varies widely based upon the type of data being compressed. Choose RLE if you network bandwidth is not a critical bottleneck for your network and you need to save CPU cycles.
- ZLIB1 through ZLIB9: Refers to levels of ZLIB compression. Level 1 is very fast but hardly compresses. Levels 7 to 9 yield the best compression but is much slower. Level 2 (ZLIB2) typically offers the best compromise of compression and speed. We suggest using ZLIB2 unless there is a specific need for higher compression and CPU utilization is not an issue.
- None: No compression is used for this transfer.
- Default: If Default is chosen, the type of compression is taken from the Node setting or set to None for non-Node transfers.
|
| Encryption
|
Turns encryption on and off. The encryption contains the following methods:
- DES (56 bit encryption): Data Encryption Standard (DES) is a symmetric cryptographic algorithm, in which one secret key is used for encryption and decryption of the data being sent. DES uses a 56 bit encryption key.
- Triple DES (112 bit encryption): Triple DES is just DES done three times with two secret keys applied in a particular order giving you 112 bit encryption.
- Blowfish (56 bit encryption): Blowfish is a block encryption algorithm that can use keys from 40 to 448 bits long. The MFT Platform Server implementation of Blowfish uses a 56 bit encryption key.
- Blowfish Long (448 bit encryption): This Blowfish block encryption algorithm uses a key 448 bits long (AKA. Blowfish Long encryption). It is very fast, about six times faster than DES, and about fifteen times fast than 3DES.
- AES (Rijndael) (256 bit encryption): AES is a symmetric block encryption algorithm that uses a key length of 256 bits. It was selected as the Advanced Encryption Standard (AES) by the US Government. When encrypting data, we suggest using this encryption algorithm.
- None: No encryption used for this transfer.
- Default: The type of encryption is taken from a Node that had been configured or it will be set to None for non-Node transfers.
|
| Custom Code Page Conversion
|
LocalCTFile
|
Translates on the local side. This parameter need to contain the name of the file.
|
| RemoteCTFile
|
Translates on the remote side. This parameter need to contain the name of the file.
Note: When defining the RemoteCTFile, you need to set the LocalCTFile to
Null in order that no translation takes place locally.
|
| UTF8BOM
|
Defines whether the UTF8BOM is added or removed by z/OS. Valid Options are:
- None - no UTF8BOM processing takes place
- Add - The UTF8BOM is added by z/OS
- Remove - The UTF8BOM is removed by z/OS
- Both - The UTF8BOM is added and removed by z/OS
|
