IBM Support

Product readme for WebSphere MQ File Transfer Edition, Version

Product Readmes


IBM WebSphere MQ File Transfer Edition, Version readme file
April 2013


- Readme file update history
- Description
- Compatibility
- System requirements
- Installing WebSphere MQ File Transfer Edition
- New function and updates in Version
- Limitations and known problems
- List of fixes included in Version
- Useful links
- Copyright and trademark information


December 2013 - information added about fix pack installation
April 2013 - readme published online


This readme file for IBM WebSphere MQ File Transfer Edition Version
details updates, fixes, limitations, and known problems.

For the very latest version of this readme file always refer to:

You can install Version over a previous version of WebSphere MQ File
Transfer Edition. If you have an Early Design Program driver on your system,
you must uninstall it before installing Version

Before installing Version, back up any previous versions of WebSphere
MQ File Transfer Edition that are installed on your system, by copying the
installation directory for the previous version to a new directory.

If you have already installed a version of WebSphere MQ File Transfer Edition
earlier than, you can choose to reuse your existing product
configuration so you will not be asked to enter any configuration information
during the installation. Alternatively, you can select a different
installation directory from the one you used to install the existing version of
WebSphere MQ File Transfer Edition to allow both versions of the product to
coexist on the same machine.

The prerequisites and corequisites for WebSphere MQ File Transfer Edition for
all platforms are listed at the following website:

You can find the installers (either install.bin, install.exe, or install) in
the following directories:


HP-UX on Itanium:


Linux on System x:

Linux on System p:

Linux on System z:

Solaris on SPARC:

Solaris on System x:


IBM i:

WebSphere MQ File Transfer Edition components
There are three possible Version components that you can install:
Server, Client, or Remote Tools and Documentation. The following topics
describe how to install each component onto distributed platforms.

You cannot install Remote Tools and Documentation natively on an IBM i platform
or on z/OS. However, you can install and use Remote Tools and Documentation on
other supported platforms, such as Windows, to monitor file transfers involving
agents that are running remotely on IBM i platforms or z/OS. For example, you
can use the WebSphere MQ File Transfer Edition plug-in for WebSphere MQ Explorer
on Windows to start a transfer of save files between agents running on IBM i



Remote Tools and Documentation:

Installing an IBM WebSphere MQ File Transfer Edition Fix Pack
For information about how to install a WebSphere MQ File Transfer Edition Fix Pack, see


Enabling the new function in Version
To enable this function for agents and command-line tools, add the
enableFunctionalFixPack property to the file. For more
information, see

Version includes the following new function:
- 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. Set this property in the 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. Set this
property in the 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. Set this property in the 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 or binary mode. In text mode, the data
is automatically converted from EBCDIC.

- 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 about the new function, see


Restrictions of the Connect:Direct bridge
The Connect:Direct bridge has a number of restrictions. For more information,

Using SMS parameters in a transfer to a z/OS Connect:Direct node
If you are transferring to a data set on a z/OS Connect:Direct node, and you
specify any SMS-specific parameters for the data set, the transfer might fail
with a Connect:Direct error message. This issue only occurs if your
Connect:Direct bridge agent is on Windows, and is because of a limitation of
Connect:Direct. To work around the issue, you can submit a user-defined
Connect:Direct process and specify any required SMS-specific parameters within
the SYSOPTS parameter.

For a list of the SMS-specific parameters supported by Connect:Direct, see
the Connect:Direct Process Language Reference Guide.

For more information about submitting a user-defined Connect:Direct process
from a file transfer request, see

Transfers using the Connect:Direct bridge to a z/OS destination node
If you issue a transfer that resolves to a destination file with a parenthesis
in its name, the following error is produced: "A member name was specified for
non-PDS file". To work around this, either rename the source file and remove
the parentheses, or specify a destination file without the parentheses.

If you are transferring from a z/OS agent where you only specify the directory
and not the individual member names, the following error is produced: "A member
name was specified for non-PDS file". To work around this, specify each member,
for example 'A.B.C(aaa)'.

Text transfers from Connect:Direct to a V7.0.3 destination agent
If you are using the Connect:Direct bridge to transfer a text file from a
Connect:Direct node to a WMQFTE V7.0.3 or earlier destination agent, and either
you have requested a destination encoding of UTF-8 or the default encoding of
the destination platform is UTF-8, the end-of-line characters will not be
converted from those in the original file. This problem will be particularly
noticeable if the source Connect:Direct node is on a Windows system and the
destination WMQFTE agent is on a Linux system. This problem will not occur if
the destination agent is a WMQFTE V7.0.4, or later agent.

Deploying the Web Gateway application and JEE database logger
The Web Gateway application cannot be deployed to a WebSphere Application
Server cluster. You can only deploy the Web Gateway application to a single
application server instance. This limitation also applies when you are
deploying the Java(TM) Platform, Enterprise Edition (JEE) database logger.

Running the stand-alone database logger as a background task
On all platforms, the stand-alone database logger provided with V7.0.4.3 does
not currently run as a background task. To use the database logger, start the
database logger in the foreground using the -F parameter or start it as a
Windows service.

Using the database logger with an Oracle database
If you use the stand-alone database logger provided with V7.0.4.3 with an
Oracle database, be aware that some of the database fields might not be
populated. This has been observed to happen to the START_ID, COMPLETE_ID, and
SCHED_ID fields in the TRANSFER table.

Running a console installation on Windows XP and Windows Server 2003 from a
DOS shell
If you run a console installation from a DOS shell on Windows XP or Windows
Server 2003, be aware that the install.exe command immediately returns to the
command prompt and does not wait for the installation to complete.

Installing Version silently
If you want to install Version silently, perform a console installation
of Version first to create a response file as described in the
following topic:
Then use the newly-created V7.0.4.3 response file to install silently.

You cannot use a response file that you previously created from an earlier
release to install V7.0.4.3 silently.

An example response file is provided in the following location in V7.0.4.3:

Installing Remote Tools and Documentation silently
The Remote Tools and Documentation silent install now appends a '/tools'
subdirectory at the end of the install file path. There is no need to specify
this in a silent install properties file. It is possible that if you generate a
response file using the Remote Tools and Documentation console install, there
might be a '/tools' subdirectory at the end. If this subdirectory exists, you
should remove it from the response file.

Interoperation with Early Design Program drivers
There is no interoperation support for agents running any level of Early Design
Program code. If you have previously installed an Early Design Program driver
for WebSphere MQ File Transfer Edition, you must uninstall the driver before
installing V7.0.4.3. You must also remove any configuration associated with the

For information about how to uninstall and remove an Early Design Program
driver, see:

Upgrading the WebSphere MQ Explorer plug-in from V7.0.0 to a newer version
If you have previously installed the WebSphere MQ File Transfer Edition plug-in
for WebSphere MQ Explorer 7.0.0, you might experience errors when upgrading to
a more recent version of the plug-in. The errors occur when WebSphere MQ
Explorer starts and they refer to being missing.

To fix this error, run one of the following commands:
strmqcfg -i


strmqcfg -c

The command with the -i parameter does not start WebSphere MQ Explorer, but
this command parameter does resolve the problem for the next start of WebSphere
MQ Explorer.

The command with the -c parameter resolves the problem and also starts
WebSphere MQ Explorer. You should only need to run strmqcfg with the -i or
-c option once to permanently resolve this issue.

These errors do not appear if you have not previously installed the plug-in for
WebSphere MQ Explorer that was provided with WebSphere MQ File Transfer Edition
Version 7.0.0 on the system: it is an issue with upgrading only.

Installing into an existing empty configuration directory
The installer does not write configuration information directly into an
existing directory. This affects you if you do not accept the default
installation location and instead manually create a directory before

For example, if you create a "/var/fte_config" directory on a UNIX system and
then enter this directory as the configuration directory in the installer, the
installer treats this empty directory as an existing complete configuration.
The installer will prompt you to reuse "/var/fte_config", and will not write
any new configuration.

Work around this by manually creating a "/var/fte" directory and then entering
"/var/fte/config" as the configuration directory in the installer. The result
is the directory "config" is created in the existing "/var/fte" directory,
with the correct contents.

Installation locations
You must ensure that you have write permission for the directory that you want
to install WebSphere MQ File Transfer Edition into.

The silent installer will appear to allow you to install into a location that
you do not have permission to install into. The silent installer does not warn
you that you do not have write permission on the directory.

You are also recommended to use different locations for the installation
directory and configuration directory.

On the IBM i platform the installation location and the config location are
fixed. The product binaries are installed in the /QIBM/ProdData/WMQFTE/V7
directory and the data directory is /QIBM/UserData/WMQFTE/V7/config.

Installing on Security-Enhanced Linux
If you are running Security-Enhanced Linux (SELinux), install WebSphere MQ File
Transfer Edition using the following steps, which depend on the on Linux
distribution you are using:
1. If you are using SuSE Linux, set the SELinux mode to permissive.

If you are using Red Hat Enterprise Linux, enable the following
option for your SELinux policy:
"Allow all unconfined executables to use libraries requiring text
relocation that are not labeled textrel_shlib_t"

2. For both SuSE Linux and Red Hat Linux: install WebSphere MQ File Transfer

3. If you are using SuSE Linux, re-enable the SELinux policy.

4 For both SuSE Linux and Red Hat Linux, run the following command:
chcon -R -t texrel_shlib_t WMQFTE_INSTALL_DIR/jre

Installing the Remote Tools and Documentation CD on platforms other than
Windows or Linux
If you install the Remote Tools and Documentation CD on any platform apart
from Windows or Linux, you cannot use either the WebSphere MQ Explorer plug-in
or the information center. You can only use the remote command line tools,
Ant and database logger parts of the installation, even though you might have
selected to install the WebSphere MQ Explorer plug-in and the information center.

Missing file after a Remote Tools and Documentation
During an installation of Remote Tools and Documentation, if you choose to
"Use existing" configuration or "Skip configuration", no sample file is created. For information about what this
file needs to contain and how to configure it, see:

Uninstalling on Windows platforms
When you uninstall WebSphere MQ File Transfer Edition from Windows, the jre
directory that is located in the WebSphere MQ File Transfer Edition
installation directory might not be deleted if it is in use. To complete the
uninstall, restart the system and the directory will automatically be removed.

Retaining transfer log message information
The transfer log information generated by WebSphere MQ File Transfer Edition,
is sent to the coordination queue manager where the information is published
to any subscribers. If there are no subscribers, the message will not be
delivered to any parties and will not be retained. To ensure that transfer
log messages are retained, you are strongly recommended to take one of several
actions before submitting the first file transfer to WebSphere MQ File Transfer
Edition. For more information, see

Running the commands on z/OS
When you use the WMQFTE commands on z/OS, the commands need to know where the
WebSphere MQ Java Native libraries are located. The commands are not able to
get this information on z/OS systems because there is no default location.

To successfully use the WMQFTE commands on your z/OS system, set the system
environment variable "LIBPATH" to the directory location of your WebSphere
MQ Java Native libraries. For example:

export LIBPATH=$LIBPATH:<WMQ Java Native Library Location>

This variable is not set by default and causes the commands to fail.

z/OS coordination queue managers and SYSTEM.QPUBSUB.QUEUE.NAMELIST namelist
If you are using a z/OS queue manager as a coordination queue manager and you
make any changes to the SYSTEM.QPUBSUB.QUEUE.NAMELIST namelist, you must
restart the coordination queue manager's channel initiator (CHINIT) to pick
up the namelist changes.

Sandboxing IBM i save files
Standard sandboxing does not work for IBM i save file transfers. Do not set the
sandboxRoot property if you plan to transfer save files, otherwise the agent
might crash. However, you can use the new user authority checking to sandbox
agent actions without problems.

JVM file encoding and EBCDIC data on IBM i Systems
Users must use ASCII file encoding to create or configure WebSphere MQ File
Transfer Edition agents on IBM i systems. ASCII is the default file encoding
for the JSE 5.0 32-bit JVM that WebSphere MQ File Transfer Edition requires.
Users who have created a file in their /home/<user>
directory with a file.encoding record that specifies an EBCDIC encoding must
change the file.encoding record to specify an ASCII encoding and then start a
new QShell session for creating or configuring agents on IBM i systems.

Special considerations are needed when transferring files containing EBCDIC
data. In these cases users who start the agent must set their JVM file encoding
to an EBCDIC encoding so that data conversion during text mode transfers work
correctly. For more information, see

Pending transfers in WebSphere MQ Explorer
When viewing Pending Transfers in the WebSphere MQ Explorer, the information in
the Name column is unique only for the source agent handling the pending
transfer. Because the Explorer can show pending transfers from multiple agents,
the Name can appear to be duplicated. The unique reference for a pending
transfers consists of the Source column and Name column.

Documentation for WebSphere MQ File Transfer Edition
You can find the most current WebSphere MQ File Transfer Edition Information
Center at:

The information center that you can install from the WebSphere MQ File Transfer
Edition Remote Tools and Documentation DVD is supported on Windows and Linux on
x86 platforms only.

You can find the list of fixes included in Version at:

In addition to this readme.txt file, you can find more information on the
WebSphere MQ File Transfer Edition website at:

The SupportPac Web page is at:

For current information on known problems and available fixes, see the Support
page of the WebSphere MQ website at:

The latest version of the WebSphere MQ File Transfer Edition Information
Center for V7.0.4.3 is available online at:



This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this
information in other countries. Consult your local IBM representative for
information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or
imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe
any IBM intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any non-IBM
product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this information. The furnishing of this information does not give
you any license to these patents. You can send license inquiries, in writing,
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785

For license inquiries regarding double-byte character set (DBCS) information,
contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this
statement may not apply to you.

This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the information. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
information at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those
Web sites. The materials at those Web sites are not part of the materials for
this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of
the information which has been exchanged, should contact:
IBM United Kingdom Laboratories,
Mail Point 151,
Hursley Park,
SO21 2JN

Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.

The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Programming License Agreement, or any equivalent agreement
between us.

Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy
of performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products. This information includes examples of data and
reports used in daily business operations. To illustrate them as completely
as possible, the examples include the names of individuals, companies, brands,
and products. All of these names are fictitious and any similarity to the names
and addresses used by an actual business enterprise is entirely coincidental.


This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for
the operating platform for which the sample programs are written. These
examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these
programs. You may copy, modify, and distribute these sample programs in any
form without payment to IBM for the purposes of developing, using, marketing,
or distributing application programs conforming to IBM's application
programming interfaces.

The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
AIX IBM System p System x System z WebSphere z/OS

Connect:Direct is a registered trademark of Sterling Commerce, Inc., an IBM

Windows is a trademark of Microsoft Corporation in the United States, other
countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.

UNIX is a registered trademark of The Open Group in the United States and other

Linux is a trademark of Linus Torvalds in the United States, other countries,
or both.

Itanium is a registered trademarks of Intel Corporation or its subsidiaries in
the United States and other countries.

Other company, product, or service names may be trademarks or service marks of

For more information, see

[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"WMQ File Transfer Edition","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018