Product readme for WebSphere MQ File Transfer Edition, Version 7.0.2

Content

IBM WebSphere MQ File Transfer Edition, Version 7.0.2 readme
November 2009

++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++

CONTENTS
-----------------
- Update history
- Description
- Announcement
- Compatibility
- System requirements
- Installing WebSphere MQ File Transfer Edition, Version 7.0.2
- New function and updates in WebSphere MQ File Transfer Edition, Version
7.0.2
- Limitations and known problems
- List of fixes included from Fix Pack 7.0.0.1 onwards
- Useful links
- Trademarks

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

README FILE UPDATE HISTORY:

October 19 2009 - readme file shipped to translation
November 27 2009 - readme file published online

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


DESCRIPTION
----------------------
This readme file for the IBM(R) WebSphere(R) MQ File Transfer Edition Version
7.0.2 details updates, fixes, limitations, and known problems.

For the very latest version of this file always refer
to the readme at:
http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006097


ANNOUNCEMENT
--------------------------
The announcement letter for WebSphere MQ File Transfer Version 7.0.2 in US
English is available on the Web at
http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&htmlfid=897/ENUS209-300


See the announcement letter for the following types of information:
- Detailed product description, including description of new function
- Product-positioning statement
- Ordering details
- Hardware and software requirements


COMPATIBILITY
-------------------------
You can install Version 7.0.2 over an existing Version 7.0.0.0, Fix Pack
7.0.0.1, or Version 7.0.1 product.

If you have already installed a version of WebSphere MQ File Transfer Edition
earlier than 7.0.2, you can choose to reuse your existing product
configuration so you will not be asked to enter any configuration information
during the 7.0.2 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.


SYSTEM REQUIREMENTS:
----------------------------------------
The prerequisites and corequisites for WebSphere MQ File Transfer Edition for
all platforms are listed at the following Web site:
http://www.ibm.com/software/integration/wmq/filetransfer/requirements/v702.html


INSTALLING WEBSPHERE MQ FILE TRANSFER EDITION VERSION 7.0.2
-------------------------------------------------------------------------------------------------------------
You can find the installers (either install.bin, install.exe, or install) in the
following directories:

AIX(R):
AIX_ppc/Disk1/InstData/VM

HP-UX on Itanium(R):
HPUX_IA64//Disk1/InstData/VM

HP-UX on PA-RISC:
HPUX_PARISC/Disk1/InstData/VM

Linux(R) on System x(R):
Linux_x86/Disk1/InstData/VM

Linux on System p(R):
Linux64_SystemP/Disk1/InstData/VM

Solaris:
Solaris_SPARC/Disk1/InstData/VM

To run the installer on UNIX(R) or Linux systems, use the following command:
sh ./install.bin

Windows(R):
Windows_x86/Disk1/InstData/VM

IBM i:
IBMi/Disk1/InstData/VM


Installing on IBM i platforms
--------------------------------------
The user who performs the install or the uninstall must have a user profile
of *SECOFR class.

To run the installer on an IBM i platform, complete the following steps:

1. Mount the DVD media containing the product on your IBM i system's optical
drive.

2. From an IBM i command line, start PASE using the following command:
CALL QP2TERM

3. When you are in PASE, change directory using the command:
cd /QOPT/IBMi/Disk1/InstData/VM

4. Start the installer using the following command: ./install -i console

This command starts the installer in interactive console mode. (The
graphical installer is not supported on IBM i systems.)

5. Respond to installer prompts as needed.
When you receive a message indicating that you have successfully installed
the product and are instructed to press ENTER to exit the installer, you
must press ENTER. Do NOT press F3=Exit.

Wait a few minutes until cleanup operations and the configuration of the
QFTE runtime environment are complete. You will then receive another
message indicating that you should press F3=Exit function key to exit the PASE
environment.

6. After you exit PASE, use the IBM i command line to start the QFTE subsystem
with the following command:
STRSBS QFTE/QFTE

7. Continue with additional QFTE subsystem startup, coordination queue manager,
command queue manager, and agent setup activities as described in the
product documentation. Start with the following topic: http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/configuring_agents_first.htm



Installing on z/OS(R)
-----------------------------
To install on z/OS:
1. Download the PAX file (which replaces the previous TAR file).
2. Create a directory for the product (or use the existing directory).
3. CD to the directory.
4. Unpack the PAX file with a "pax -rf filepath" command.
5. CD to the lib subdirectory.
6. Run the command "chtag -t -c ISO8859-1 fteChtagScripts"
7. Run the fteChtagScripts script with "./fteChtagScripts"


WebSphere MQ File Transfer Edition components
-----------------------------------------------------------------------
As with Versions 7.0.0.0, 7.0.0.1, and 7.0.1 of WebSphere MQ File Transfer
Edition, there are three possible Version 7.0.2 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. 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. For example, you can use
WebSphere MQ File Transfer Edition's plug-in for the WebSphere MQ Explorer
on Windows to start a transfer of save files between agents running
on IBM i systems.

Server:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/installing_wizard.htm

Client:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/installing_client.htm

Remote Tools and Documentation:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/installing_tools.htm


NEW FUNCTION AND UPDATES IN VERSION 7.0.2
--------------------------------------------------------------------------

IBM i platform support
------------------------------
WebSphere MQ File Transfer Edition now supports the transfer of files
residing in "root"(/) and QOpenSys file systems, and save files residing
in the QSYS.LIB file system on IBM i platforms.

For an example of a basic client/server environment that you can
set up to support file transfer operations between IBM i systems using
WebSphere MQ File Transfer Edition, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/ibmi_basic_scenario.htm


Protocol bridge
---------------------
The protocol bridge allows your WebSphere MQ File Transfer Edition network to
access files stored on a file server outside your WebSphere MQ File Transfer
Edition network. This file server can use either the FTP or SFTP network
protocols.

For more information about the protocol bridge, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/protocol_bridge.htm


Enhancements to access control
----------------------------------------------
WebSphere MQ File Transfer Edition now supports finer grained checking of
users' authorities, which permits access to be granted (or denied) to
specific product functions for each user. For example, you can choose which
users have the authority to schedule transfer operations to happen at a future
time. For more information, start with the following topic:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/wmqfte_resource_access.htm


Support for multi-instance queue managers
--------------------------------------------------------------
WebSphere MQ Version 7.0.1 supports the creation of multi-instance queue
managers. Check the WebSphere MQ Supported Software Web pages to determine
the support details for your platform:
http://www.ibm.com/support/docview.wss?rs=171&uid=swg27012075

WebSphere MQ File Transfer Edition Version 7.0.2 supports
connection to multi-instance agent queue managers and a multi-instance
coordination queue manager. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/multi_instance_qms.htm


Maximum concurrent transfer limit - behavior change
-------------------------------------------------------------------------
When an agent reaches the limit of its maxSourceTransfers property (the
default value is 25), any additional transfer requests no longer fail. The
additional transfer requests are accepted and queued by the agent until the
agent has capacity to run the transfers. The queued transfer requests are
processed in transfer priority and age (time when request was added to the
queue) order. That is, the agent will choose the highest priority, oldest
transfer request. The agent will queue up to the limit of maxQueuedTransfers
requests before rejecting the request with a SOURCE_CAPACITY_EXCEEDED (44)
return code.

For more information about these properties, refer to the topic "Properties
files for WebSphere MQ File Transfer Edition" in the product documentation.



LIMITATIONS AND KNOWN PROBLEMS
----------------------------------------------------------

Interoperation between different levels of WebSphere MQ File Transfer
Edition
---------------------------------------------------------------------------------------------------
Interoperation between agents at Version 7.0.0.1 (Fix Pack 7.0.0.1 on
distributed systems and UK45574 on z/OS) and agents at Version 7.0.1 is
supported.

Interoperation with the general availability release, 7.0.0.0, is supported
only if the agents have had service applied to update them to V7.0.0.1 (z/OS
UK45574).

There is no interoperation support for agents running any level of Early
Design Program code.


Upgrading the WebSphere MQ Explorer plug-in from V7.0.0 to V7.0.2
-------------------------------------------------------------------------------------------------
If you install Version 7.0.2 of the WebSphere MQ File Transfer Edition plug-in
for WebSphere MQ Explorer over Version 7.0.0 of the same plug-in, this might
generate errors when WebSphere MQ Explorer starts up that refer to
com.ibm.wmqfte.bootstrap being missing.

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

or

strmqcfg -c

The command with the -i parameter does not start the 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 WebSphere MQ
Explorer Version 7.0.0 on the system: it an issue with upgrading only.


Uninstalling Early Design Program drivers
---------------------------------------------------------
If you have previously installed an Early Design Program driver for WebSphere
MQ File Transfer Edition, you must uninstall the driver before installing any
general availability (GA) version of WebSphere MQ File Transfer Edition, that
is V7.0.0.0, V7.0.0.1, V7.0.1, or V7.0.2. You must also remove any configuration
associated with the driver.

Complete the following steps before uninstalling the driver:
1. Stop all agents that are running using the fteStopAgent command.
2. Remove the SYSTEM.FTE name from the SYSTEM.QPUBSUB.QUEUE.NAMELIST namelist
on the coordination queue manager.
3. Delete the SYSTEM.FTE queue on the coordination queue manager.
4. Delete the SYSTEM.FTE topic on the coordination queue manager.
5. Delete all agent queues on the agent queue managers. Each agent has the
following queues:
* SYSTEM.FTE.COMMAND.<agent_name>
* SYSTEM.FTE.DATA.<agent_name>
* SYSTEM.FTE.EVENT.<agent_name>
* SYSTEM.FTE.REPLY<agent_name>
* SYSTEM.FTE.STATE.<agent_name>
* SYSTEM.FTE.AUTHADM1.<agent_name>
* SYSTEM.FTE.AUTHAGT1.<agent_name>
* SYSTEM.FTE.AUTHMON1.<agent_name>
* SYSTEM.FTE.AUTHOPS1.<agent_name>
* SYSTEM.FTE.AUTHSCH1.<agent_name>
* SYSTEM.FTE.AUTHTRN1.<agent_name>
6. Delete the following queues on the coordination queue manager:
* SYSTEM.FTE.DATABASELOGGER.REJECT
* SYSTEM.FTE.DATABASELOGGER.COMMAND
7. For all platforms except IBM i, delete the WebSphere MQ File Transfer
Edition configuration directory. By default this directory is called
"config".


If you are on Windows, you must then use the following steps to uninstall:
1. Uninstall WebSphere MQ File Transfer Edition from your system.
2. Restart your machine.
If you do not restart your machine after uninstalling an Early Design
Program driver and before installing the GA version, there might still be
files marked for deletion. This file deletion still occurs, even if you
have installed a new version. This might cause your new install to stop
working after a future restart.
3. Delete the WMQFTE directory if the directory still exists.
4. Install the GA version of WebSphere MQ File Transfer Edition.


If you have been using the EDP driver on IBM i, the uninstaller is currently
not functional, therefore you must uninstall the driver manually by completing
the following steps:
1. Stop any running agents.
2. From an IBM i command line, complete the following steps:
a. End the QFTE subsystem with the following command: ENDSBS QFTE
b. Start PASE using the following command: CALL QP2TERM
3. In PASE, complete the following steps:
a. Run the pre-uninstall script as follows:
./QIBM/ProdData/WMQFTE/V7/lib/ftePreUninstall

After running the ftePreUninstall script, if
/QIBM/ProdData/WMQFTE or any subdirectories still exist then
use the following step 3b to complete the cleanup. Otherwise step 3b is
not necessary.
b. Remove the WMQFTE product directory using the following command:
rm -rf /QIBM/ProdData/WMQFTE
c. Remove the WMQFTE configuration, using the following
command:
rm -rf /QIBM/UserData/WMQFTE


Text-only (console) installation
------------------------------------------
You can install WebSphere MQ File Transfer Edition using a text-only option
(console installation): -i console

This method is documented at:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/console_install.htm


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
installation.

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 installer will appear to allow you to install into a location that you do
not have permission to install into. The installer does not warn you that you
do not have write permission on the directory. This means you can go through
the install panels and only get an error message at the end, which asks you to
check the error log. However, the error log probably does not exist because it
cannot be written to your install root because of these permission
restrictions.

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(R)
--------------------------------------------------------
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 Edition.

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.


Database logger on IBM i platform
------------------------------------------------
The database logger is not supported for the IBM i platform.


Missing databaselogger.properties file after a Remote Tools and Documentation
installation
---------------------------------------------------------------------------------------------------------------
During an installation of Remote Tools and Documentation, if you choose to
"Use existing" configuration or "Skip configuration", no sample
databaselogger.properties file is created. For information about what
this file needs to contain and how to configure it, see step 7 in the
following topic:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/dl_install_standalone.htm


Uninstalling on UNIX and Linux platforms
----------------------------------------------------------
When you uninstall WebSphere MQ File Transfer Edition from UNIX and Linux,
the jre directory is not removed. To complete the uninstall, manually delete
this directory.


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:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/retain_log.htm


Running the fteCreateAgent command on z/OS
------------------------------------------------------------------
When you use the fteCreateAgent command to create an agent with a bindings or
local queue manager connection, the command needs to know where the WebSphere
MQ Java(TM) Native libraries are located. The command is not able to get this
information on z/OS systems because there is no default location and you will
see the following informational message:

BFGMQ1007I: The coordination queue manager cannot be contacted or has refused
a connection attempt. The WebSphere MQ reason code was 2495. The agent's
presence will not be published.

To successfully register the agent on your WebSphere MQ File Transfer Edition
network when you subsequently run the fteStartAgent command, 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 informational message.

By setting the javaLibraryPath in the agent.properties file for the agent, the
presence of the agent will be registered anyway at the first use of the
fteStartAgent command.


z/OS coordination queue managers and SYSTEM.QPUBSUB.QUEUE.NAMELIST
namelist changes
------------------------------------------------------------------------------------------------------------------
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.


protocolServerPort property behavior
---------------------------------------------------
Setting the protocol bridge property "protocolServerPort" is currently
affecting the following areas of protocol bridge behavior:
- The maximum number of files that you can transfer in a single transfer,
where you have specified a directory or wild card in the source file name.
- The timeout periods and connection retries to the protocol file server.

Where possible, do not set the protocolServerPort property or use the -bp
(server_port) parameter in the fteCreateBridgeAgent command. By default, the
FTP or SFTP standard default port numbers are used.


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.

This will be fixed in a future release.


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 J2SE 5.0 32-bit JVM that WebSphere MQ File Transfer Edition
requires. Users who have created a SystemDefault.properties 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 "Transferring files to
or from IBM i systems" at:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/ibmi_transfers.htm


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
product documentation at:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/wmqfte_intro.htm

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.

If you have installed the version of the information
center supplied on the WebSphere MQ File Transfer Edition
Remote Tools and Documentation DVD, you must download the most
current information by clicking the Update button on the
information center toolbar. The instructions for updating
the information center are described in the topic "Using
the WebSphere MQ File Transfer Edition documentation".
Or you can view the instructions online at:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/infocenter.htm



LIST OF FIXES INCLUDED IN WEBSPHERE MQ FILE TRANSFER EDITION V7.0.2
------------------------------------------------------------------------------------------------------------------------
Version 7.0.2 includes the following fixes, which were first included in Fix
Pack 7.0.0.1:

- IC59979 CSQX541E when using WMQFTE via MQ Explorer view on Windows to
connect to the z/OS queue manager

- PK80076 error EDC5024I an attempt was made to close a file that had been
opened by another thread while transferring QSAM files to z/OS

- IC59697 (DOC) WMQFTE wild card behavior is not correct as stated in the
manual

- IC59671 MQ FTE is not handling correctly the standard output stream when
double byte character sets are used

- IC59506 WMQFTE scheduling transfer doesn't work when using Japanese locale

- IC60263 Path delimiter in exits is inconsistent with an exit

- PK82916 Problem with end of line characters with text transfers to a DBCS
EBCDIC file



USEFUL LINKS
----------------------
In addition to this readme.txt file, you can find more information on the
WebSphere MQ File Transfer Edition Web site:
http://www.ibm.com/software/integration/wmq/filetransfer/

The SupportPac(TM) Web page is at:
http://www.ibm.com/support/docview.wss?rs=977&uid=swg27007205

For current information on known problems and available fixes, see the Support
page of the WebSphere MQ Web site at:
http://www.ibm.com/software/integration/wmq/support/

Web documentation updates
The latest version of the WebSphere MQ File Transfer Edition Information
Center for V7.0.2 is available online at:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/wmqfte_intro.htm




++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

TRADEMARKS

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

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

Java and all Java-based trademarks and logos are trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.

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

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

Itanium is a registered trademark of Intel(R) Corporation or its subsidiaries in
the United States and other countries.


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