Send and Receive Save File Parameters

The following table lists all the parameters in alphabetical order for easy reference as well as provides a brief description. Some command parameter fields with brief descriptions are already listed in the Send and Receive File Parameters section. Please see the Send and Receive File Parameters section if the command parameter is not listed here.

Parameter Description
CRC Check Specifies whether the CRC check validation method is used in this transfer. CRC check validation adds an extra layer of security and file integrity. The CRC check validation checks the data sent and received over the network between MFT Platform Server Initiator and Responder Programs.
The CRC Check defined to MFT Platform Server for the given remote node via the Work With Node Configuration (CFWRKNET) or Global Parameter Update (CFUPDGLB) command is used. Valid values are:
  • Y - CRC check validation method is used.
  • N - CRC check validation method is not used.
If node name is selected in Connection Type, the CRC check value is retrieved from the MFT Platform Server Node Configuration File record based on the node name selected. If the node name does not exist, a default value is used. If IP address or IP name is selected in Connection Type, the CRC check value is retrieved from the MFT Platform Server Global Parameter File record. But you can override any default value by entering the CRC check value selection in any transfer command.
Class Of Service Name Specifies the name of the Class Of Service used in the transfer. Class Of Service is used to set the send and receive buffer sizes of sockets. Valid values are:
  • blank - Default bracket name is used. Parameters SBUFSIZE and RBUFSIZE contained within brackets. Default name values are used.
  • Class Of Service Name - Name entered in bracket name is used. Located in the Class Of Service Table (CFCOS) that is distributed with the MFT Platform Server product. Parameters values for SBUFSIZE and RBUFSIZE contained within the bracket name that was entered are used.
Compression Sets the data compression to be used for this transfer. Valid values are:
  • None – No data compression is used.
  • LZ – LZ 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. LZ compression uses a lot of CPU cycles. We strongly suggest using ZLIB compression instead of LZ compression. ZLIB compresses better and uses far fewer CPU cycles.
  • RLE – RLE is more data-dependent than LZ. That is, the compression ratio may vary 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.
  • ZLIB – ZLIB Data Compression method is used.
Local Save File Options Specifies whether to create a file and add data records or use an existing file and replace data records when a file is received. Valid values are:
  • C - If the local save file does not exist, a local save file is created with the name specified in the Local Save File Name parameter. Then the received remote save file data records are added to the local save file. If the local save file does not exist, the command ends with an escape message. In addition to the normal validity checks, the following special conditions must all be true for the receive save file operation to create the local save file.
    • A library name must be specified on the Local Save File Name parameter. The special value *LIBL must not be used when creating the save file.
    • To run this command, you must be authorized to add the local save file to the specified local library and you must also have operational rights to the Create Save File (CRTSAVF) command.
  • R - The received remote save file data records replace all existing records in the local save file that is used. The local save file is cleared before the received remote save file data records are added.

    The local save file must exist when this command is executed. If a local save file is not created to receive the remote save file data records. The command ends with an escape message.

  • X - If the local save file does not exist, a new local save file is created and the received remote save file data records are added to the local save file that is used.

    If the local save file exists, it replaces all existing records in the local save file that is used. The local save file is cleared before the received remote save file data records are added.

Local Save File Name

- Library

Specifies the local save file name and library where the save file is located.
Note: The library name is set to *LIBL means the library list is used to locate the name of the local save file. This is only valid when sending/receiving save files to/from another IBM i system.
Remote Save File Options Specifies whether to create a file and add data records or use an existing file and replace data records when a file is sent. Valid values are:
  • C - If the remote save file does not exist, a file is created with the name specified in the Remote Save File Name parameter. Then the sent local save file data records are added to the remote save file. If the remote save file does not exist, the command ends with an escape message. In addition to the normal validity checks, the following special conditions must all be true for the send save file operation to create the remote save file.
    • A library name must be specified on the Remote Save File Name parameter. The special value *LIBL should not be used when creating the save file.
    • To run this command, you must be authorized to add to the remote save file to the specified remote library, and you must also have operational rights to the Create Save File (CRTSAVF) command.
  • R - The sent local save file data records replace all existing records in the remote save file that is used. The remote save file is cleared before the sent local save file data records are added.

    The remote save file must exist when this command is executed. A remote save file is not created to receive the sent local save file data records. The command ends with an escape message

  • X - If the remote save file does not exist, a new remote save file is created and the local records are added to the remote save file that is used.

    If the remote save file exists, all existing records are replaced in the remote save file that is used. The remote save file is cleared before the sent local save file data records are added.

Remote Save File Name

- Library

Specifies the remote save file name and library where the save file is located.
Note: If you specify *LOCALFILE for this parameter, MFT Platform Server tries to give the Remote Save File Name and Library parameter the same location as the Local Save File Name and Library parameter. This is valid only for IBM i system to IBM i system transfers only.
Transport Layer Security Processes the request transfer using the TCP/IP security protocol. The Transport Layer Security defined to MFT Platform Server for the given remote node via the Work With Node Configuration (CFWRKNET) command is used.

The Transport Layer Security value is retrieved from the MFT Platform Server Node Configuration File by the Remote Location Name or the IP Address command parameter field values, if the remote node record exists. Valid values are:

  • Y - Specifies that the Transport Layer Security is required for this data transfer request transaction job.
  • N - Specifies that the Transport Layer Security is not required for this data transfer request transaction job.
  • T - Specifies that the Transport Layer Security Tunnel is required for this data transfer request transaction job.
ZLIB Comp Level Indicates the ZLIB data compression level from 0 to 9 controlling the level of compression that is used to process all MFT Platform Server outgoing data transfer request transactions for a particular remote node.

The ZLIB compression level defined to MFT Platform Server for a given remote node via the Work With Node Configuration (CFWRKNET) command is used.

You can set the ZLIB data compression level to be used for a transfer. 0 is no ZLIB compression level. 1 is the fastest and produces the least data compression. 9 is the slowest and produces the most data compression.
Note: We suggest using ZLIB2 since this offers a high level of compression and does not use too many CPU cycles.
Valid values are:
  • 0 - No ZLIB data compression level
  • 1 - ZLIB data compression level 1 method
  • 2 - ZLIB data compression level 2 method
  • 3 - ZLIB data compression level 3 method
  • 4 - ZLIB data compression level 4 method
  • 5 - ZLIB data compression level 5 method
  • 6 - ZLIB data compression level 6 method
  • 7 - ZLIB data compression level 7 method
  • 8 - ZLIB data compression level 8 method
  • 9 - ZLIB data compression level 9 method