What's new in Version 7.0.4.3?

Learn about the new function in WebSphere® MQ File Transfer Edition Version 7.0.4.3.

Version 7.0.4.3 is a fix pack containing new function. By default, this new function is not enabled. To enable the function, add the enableFunctionalFixPack property to the wmqfte.properties file and set it to 7043. For more information, see The wmqfte.properties file.

  • You can now submit a large one file to one message transfer, up to a file size of 100 MB. To reduce memory usage for large one file to one message transfers, you are recommended to set the -qs parameter on the fteCreateTransfer command equal to the size of message being written. If you have a file larger than 100 MB, and you also specify the -qs parameter on the fteCreateTransfer command, the file is split into multiple messages.

    In the case of recovery of binary one file to message transfers, the transfer restarts from the point that the last checkpoint was written. In the case of recovery of text transfers, the transfer restarts from the beginning of the file, which might result in an incomplete group of messages on the destination queue. When the failed text transfer is restarted, a completely new group of messages is written.

  • Transfer progress log messages are now published for transfers that fail early. You can then use the information published about the transfer items in the failed transfer to resubmit that transfer.
  • The commandMessagePriority property sets the priority of both internal messages and command messages for the fteStopAgent, fteCancelTransfer, ftePingAgent, and fteSetAgentTraceLevel commands. You can also use the commandMessagePriority property to set the priority of internal acknowledgement and acknowledgement-expected messages. You can set commandMessagePriority to a value to prioritize internal WebSphere MQ File Transfer Edition messages above new transfer requests, which can improve agent performance. For more information, see The wmqfte.properties file.
  • You can use the maxInlineFileSize property to set the maximum size of file that is included in the transfer request message for single file-to-file or file-to-message transfers. This might improve transfer performance. For more information, see The agent.properties file.
  • You can use the enableMemoryAllocationChecking property to ensure that the agent checks whether there is sufficient memory available to run a transfer before the transfer is started. If there is insufficient memory available, the transfer is put into recovery, which prevents the agent from failing with an out-of-memory error. For more information, see The agent.properties file.
  • Transfer log publications for file-to-message and message-to-file transfers now contain all the transfer request attributes.
  • You can now transfer physical file members in the QSYS.LIB file system on IBM® i.

    This support is limited to transferring file members in program-described files only and does not support the use of externally-described files or source physical files. You can transfer file members to a destination file member on another IBM i system or to a stream file residing in an IBM i system or other platforms such as Windows or UNIX. You can also transfer stream files to a destination file member. When transferring to a file that does not exist, a program-described file is created with a record length of 5000. There is currently no support for specifying the record length, CCSID, or other attributes for creating the file during the transfer. If you want to specify a value or attribute, you must create the destination file before the transfer occurs, although you could also do this using a pre-destination transfer task.

    You can transfer file members in text mode only. The data is automatically converted from EBCDIC.

    For more information, see Transferring physical file members that reside in the QSYS.LIB file system on IBM i systems.

  • On IBM i, you can use the user exit samples provided in WMQFTE for the following tasks:
    • Transfer files in the QDLS file system.
    • Automatically transfer physical file members from an IBM i library in the same way as a WMQFTE file monitor.
    • Delete an empty file object when the source file member is deleted as part of the transfer.
    For more information, see Sample IBM i user exits.

Concept Concept

Feedback

Timestamp icon Last updated: Tuesday, 30 January 2018
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/new_7043.htm