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
- 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 Database Mbr Opt
|
Specifies how to handle database files that exist on the IBM i system, which members are restored. Valid values are:
- M - Matching saved members are restored if the lists of the members where they exist match, member for member, the lists of the current IBM i system version. Database Member Options (*MATCH) is not valid when (*ALL) is specified for the Object Differences parameter.
- A - All members in the saved file are restored.
- N - New members only (members not known to the IBM i system) are restored.
- O - Old members only that already known to the IBM i system are restored.
|
Local Library Name
|
Specifies the local library name to be used for the transfer request.
|
Local Library Options
|
Specifies whether to create a library and add objects or use an existing library and add or replace objects when objects are received. Valid values are:
- C - If the local library does not exist, a local library is created with the name specified in the
Local Library Name parameter. Then the received remote library objects are added to the local library. If the local library exists, 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 library operation to create the local library.
- A library name must be specified on the Local Library Name parameter.
- To run this command, you must be authorized to add the objects to the local library and you must also have operational rights to the
Create Library (CRTLIB) command
- R - The received remote library objects replace or are added to the objects in the local library only by the parameter (Restore Object Options) rules in this MFT Platform Server command. The local library must exist when this command is executed. A local library is not created to receive the remote library objects. The command ends with an escape message
- X - If the local library does not exist, a new local library is created and the received remote library objects are added to the local library that is used. If the local library exists, the received remote library objects replace or are added to the objects in the local library only by the parameter (Restore Object Options) rules in this MFT Platform Server command.
|
Local Obj Differences
|
Specifies whether differences are allowed between the saved objects and the restored objects. By checking the object level ids, authority list and ownership. You must have all object (*ALLOBJ) special authority to specify any value other than
*NONE for this parameter.
If differences are found, the final message for the restore operation is an escape message rather than the normal completion message. Valid values are:
- N - None of the differences listed above are allowed on the restore operation.
- A - All of the differences listed above are allowed on the restore operation.
|
Local Restore Obj Opt
|
Specifies how to handle restoring each library object. This parameter determines how all library objects are restored. Valid values are:
- A - All the objects in the saved library are restored to the library. Objects in the saved library replace the current versions in the system library. Objects not having a current version are added to the system library. Objects presently in the library, but not on the media, remain in the library
- N - New objects in the saved library that do not exist in the current version of the system library are added to the library. Only objects not known to the system library are restored; known objects are not restored. This option restores objects that were deleted after they were saved or that are new to this operation continues
- O - Old objects in the library having a saved version are restored; that is, the version of each object currently in the library is replaced by the saved version. Only objects known to the library are restored. If any saved objects are no longer part of the on-line version of the library, they are not added to the library; an informational message is sent for each one, but the restore continues.
|
Object Names
|
Specifies the names of one or more objects or the generic name of each group of objects to be restored. All the objects must be in the library specified for the Library (LIB) parameter. If
*ALL is specified or defaulted for the Object types (OBJTYPE) parameter, all the object types listed in the description of that parameter are restored, provided they are in the specified library and have the specified names. Valid values are:
- *ALL - All the objects in the specified libraries are restored, depending on the values specified for the OBJTYPE parameter.
- generic-name - One or more generic names of groups of objects in the specified library to be restored. A generic name is a character string that contains one or more characters followed by an asterisk (*). If an * is not specified with the name, the system assumes that the name is a complete object name.
- name - One or more names of specific objects to be restored. Both generic names and specific names can be specified in the same command.
|
Object Types
|
Specifies the types of system objects that are restore. Specify the value for each of the types of objects to be restored, such as command (*CMD), file (*FILE), or program (*PGM). Valid value is:
*ALL - All object types that are specified by name and we saved from the specified library are restored. If *ALL is also specified for the Objects (OBJ) parameter, all objects saved for that library are restored.
|
Remote Database Mbr Opt
|
Specifies how to handle database files that exist on the IBM i system, which members are restored. Valid values are:
- M - Match the saved members are restored if the lists of the members where they exist match, member for member, the lists of the current IBM i system version. Database Member Options (*MATCH) is not valid when (*ALL) is specified for the Object Differences parameter.
- A - All members in the saved file are restored.
- N - New members only (members not known to the IBM i system) are restored.
- O - Old members only that already known to the IBM i system are restored.
|
Remote Library Name
|
Specify the remote library name to be used for the transfer request.
If you specify
*LOCALLIB for this parameter, MFT Platform Server tries to give the
Remote Library Name parameter the same name as the
Local Library Name parameter. This is valid only for IBM i system to IBM i system transfers only.
|
Remote Library Options
|
Specifies whether to create a library and add objects or use an existing library and add or replace objects when objects are sent. Valid values are:
|
Remote Obj Differences
|
Specifies whether differences are allowed between the saved objects and the restored objects. By checking the object level ids, authority list and ownership. You must have all object (*ALLOBJ) special authority to specify any value other than *NONE for this parameter.
If differences are found, the final message for the restore operation is an escape message rather than the normal completion message. Valid values are:
- N - None of the differences listed above are allowed on the restore operation.
-
A - All of the differences listed above are allowed on the restore operation.
|
Remote Restore Obj Opt
|
Specifies how the object(s) should be restored in the library. Valid values:
- A – All objects are written or replaced in the library.
- N – Only objects that are new and do not exist in the library are written.
- O – Only existing objects in the library are replaced.
|
Target Release
|
Specifies which IBM i Operating System Target Release should be used when restoring the object on the IBM i local/remote system while processing the MFT Platform Server object transfer request transaction job. Valid Values are:
- *CURRENT - The current IBM i Operating System release is used when restoring the object.
- *PRV - The previous IBM i Operating System release is used when restoring the object.
- V7R3M0 - The IBM i Operating System V7R3M0 release is used when restoring the object.
- V7R2M0 - The IBM i Operating System V7R2M0 release is used when restoring the object.
- V7R1M0 - The IBM i Operating System V7R1M0 release is used when restoring the object.
|
Transport Layer Security
|
Processes the request transfer using the TCP/IP security protocol. Valid values are: N,
Y,
T. 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.
- 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
|