Product readme for WebSphere MQ File Transfer Edition, Version 7.0.1

Content

IBM WebSphere MQ File Transfer Edition, Version 7.0.1 readme
June 2009

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

CONTENTS
-----------------
- Update history
- Description and useful links
- Prerequisites and corequisites
- Installing WebSphere MQ File Transfer Edition, Version 7.0.1
- Updates in WebSphere MQ File Transfer Edition, Version 7.0.1
- Limitations and known problems
- List of fixes included from Fix Pack 7.0.0.1 onwards
- Trademarks


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

README FILE UPDATE HISTORY:

05 June 2009 - file published online
18 May 2009 - file resent to translation
24 April 2009 - file sent for translation


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


DESCRIPTION
----------------------
This readme file for the IBM WebSphere MQ File Transfer
Edition Version 7.0.1 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


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

The SupportPac 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 website at:
http://www.ibm.com/software/integration/wmq/support/

Web documentation updates
The latest version of the WebSphere MQ File Transfer
Edition documentation is available online at:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/welcome/WelcomePagev7r0.html

Announcement letter
The announcement letter for WebSphere MQ File Transfer Version 7.0.1
in US English is available on the Web at
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&htmlfid=897/ENUS209-118
(for distributed platforms),
or
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&htmlfid=897/ENUS209-119
(WebSphere MQ for z/OS).

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



PREREQUISITES AND COREQUISITES:
--------------------------------------------------------------
Prerequisites and corequisites for WebSphere MQ File Transfer Edition are listed
at the following website:
http://www.ibm.com/software/integration/wmq/filetransfer/requirements/v701.html



INSTALLING WEBSPHERE MQ FILE TRANSFER EDITION VERSION 7.0.1
-----------------------------------------------------------------------------------------------------------
You can install Version 7.0.1 over an existing Version 7.0.0.0 or Fix
Pack 7.0.0.1 product.

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

As with Versions 7.0.0.0 and 7.0.0.1 of WebSphere MQ File Transfer Edition, there are
three possible Version 7.0.1 components that you can install: Server, Client, or
Remote Tools and Documentation. The following topics describe how to install each
component onto distributed platforms.

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

To install any of the components onto z/OS, use the information in the
following topic:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/zos_install.htm



NEW FUNCTION AND UPDATES IN VERSION 7.0.1
---------------------------------------------------------------------------
WebSphere MQ File Transfer Edition Version 7.0.1 includes
the following new features:

- Apache Ant
- Resource monitoring
- Database logger
- Unattended (silent) installation
- Generation data group support
- z/OS tape support


Apache Ant
-----------------
Ant extensions
WebSphere MQ File Transfer Edition now includes a number of extensions
for Apache Ant that allow you to carry out certain tasks. The documentation
describing this new feature starts with the following topic:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/using_ant.htm

- fteAnt command:
Runs an Apache Ant script in the WebSphere MQ File Transfer Edition Ant
environment. This removes the need to include the WebSphere MQ File Transfer
Edition Ant extensions in any Ant scripts that might need them.
For more information about to use this command, see:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/fteant.htm


Resource monitoring
-----------------------------
You can now monitor a resource (for example, the contents of a directory) using
WebSphere MQ File Transfer Edition. When a trigger condition is
successfully met in this monitored resource, a task is started,
like a file transfer.

For example, you can use a resource monitor in the following way:
an external application puts one or more files in a known directory
and when processing is complete, the external application places
a trigger file in a directory monitored by WebSphere MQ File
Transfer Edition. The trigger file is then detected and a defined
file transfer starts, which copies the files from the known
directory to a destination agent.

fteCreateMonitor is the command to create a resource monitor and
is described at:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/create_monitor_cmd.htm
You can also create resource monitors using the WebSphere MQ File
Transfer Edition plug-in for WebSphere MQ Explorer.

fteDeleteMonitor is the command to delete an existing resource
monitor and is described at:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/delete_monitor_cmd.htm

fteListMonitors is the command to list existing resource
monitors and is described at:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/list_monitors_cmd.htm


Database logger
-----------------------
When WebSphere MQ File Transfer Edition transfers files, it publishes information
about its actions to a topic on the coordination queue manager.
The database logger is a new optional component of WebSphere MQ File Transfer
Edition that you can use to copy this information into a database for analysis
and auditing purposes.

The database logger is a stand-alone Java(TM) application that is installed on a machine
that hosts the coordination queue manager and the database.

You must install and configure your WebSphere MQ File Transfer Edition coordination
queue manager before you install the database logger. See the following topics for
details:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/installing_wizard.htm
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/installing_summary.htm

For information about how to install and configure the database logger, start with the information here: http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/database_logger.htm


Unattended or silent installation
---------------------------------------------
You can now you install WebSphere MQ File Transfer Edition in an unattended
or silent mode. Unattended mode means the installation wizard runs without
any user interaction and installation is completed according to a predefined
set of options contained in a response file.

For information about how to run an unattended installation, start with the information here: http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/silent_overview.htm


Generation data group support
--------------------------------------------
WebSphere MQ File Transfer Edition now supports generation data
groups (GDGs) for source and destination data sets on the z/OS
platform. Both absolute and relative GDG names are supported.

For more information, start with the information here:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/start_new_transfer_cmd.htm


z/OS tape support
--------------------------
WebSphere MQ File Transfer Edition now supports tape data sets.

When you transfer a file or data set to tape, any existing data set that
is already on the tape is replaced. The attributes for the new data set are
set from attributes passed in the transfer definition. If no attributes are
specified, attributes are set to the same as the source data set or to the
default values when the source is a file. The attributes of an existing tape
data set are ignored.


Reporting of Transfer Log publication failures
---------------------------------------------------------------
WebSphere MQ File Transfer Edition agents publish Transfer Log messages
to the SYSTEM.FTE queue on the coordination queue manager. The coordination
queue manager then publishes the messages on the SYSTEM.FTE queue to
the SYSTEM.FTE topic. If the publication fails for some reason,
the coordination queue manager attempts to send a reply to the
SYSTEM.FTE.COMMAND.<sourceAgentName> queue on the
source agent's queue manager. For this to work, you must set up WebSphere MQ
intercommunications between the coordination queue manager and source agent's
queue manager so that the coordination queue manager can send messages to
the source agent's queue manager. The source agent reads the reply messages
from the SYSTEM.FTE.COMMAND.<sourceAgentName> queue and logs a warning message
in the agent's event log: outputn.log. The warning message shows the transfer
ID and the reason codes for the failure.


Data set performance improvements and Java(TM) SDK upgrade for z/OS
------------------------------------------------------------------------------------------------
Performance for data set transfers has been improved in WebSphere MQ
File Transfer Edition for z/OS. To fully take advantage of these
performance enhancements, upgrade the Java SDK that WebSphere MQ File
Transfer Edition for z/OS uses to Version 5.0, SR9.


Maximum data set size limit on z/OS - earlier restriction lifted
----------------------------------------------------------------------------------
Previously for z/OS systems, there had been a limit to
the maximum size of data set that could be transferred. This size restriction
has now been lifted.


Change to sandboxRoot property
-------------------------------
For V7.0.1, you can now specify more than one path in the sandboxRoot
property. For more information, see the Properties topic:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/properties.htm



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 Access Program code.


Upgrading the WebSphere MQ Explorer plug-in from V7.0.0 to V7.0.1
-----------------------------------------------------------------
If you install Version 7.0.1 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 Access Program drivers
-----------------------------------------------------------
If you have previously installed an Early Access 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,
or V7.0.1. You must also remove any configuration associated with the driver.

For all platforms, carry out 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>
6. Delete the following queues on the coordination queue manager:
* SYSTEM.FTE.DATABASELOGGER.REJECT
* SYSTEM.FTE.DATABASELOGGER.COMMAND
7. 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 Access 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.


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 here:
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.


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


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


Maximum number of file transfers
----------------------------------------------
By default WebSphere MQ File Transfer Edition processes a maximum of 25
inbound and 25 outbound file transfers at one time. If these limits are
exceeded, any additional transfers are rejected and listed as "cancelled"
in the transfer log.

This might be a problem if the file transfer agent is stopped for an
extended period of time and a backlog of more than 25 transfer requests
builds up. You can configure the number of transfers that an agent
processes using the 'maxSourceTransfers' and 'maxDestinationTransfers'
parameters. These parameters are described here:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/properties.htm

If you increase the maximum number of transfers, this increases
the resources consumed by an agent. To accommodate this you might
want to adjust the amount of memory that the agent's JVM
uses. You can override the default agent JVM settings by setting
the "FTE_JVM_PROPERTIES" environment variable before you start the agent.
For example, specifying a FTE_JVM_PROPERTIES environment variable of
"-Xmx512M", sets the maximum amount of memory that the agent uses to
512 MB.


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


Resource monitors with names that contain the characters * or %
-------------------------------------------------------------------------------------------
If you create a resource monitor with a name that contains either the
asterisk (*) or percent sign (%) character, this resource monitor
will not be listed when you issue an fteListMonitors command.
However, the resource monitor functions correctly and you can delete the
monitor with the fteDeleteMonitor command as normal.

In a future fix pack, the characters * and % will be rejected
as invalid characters for resource monitor names.


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.


Using fteCreateTransfer to copy an existing PDS data set to a new data set
---------------------------------------------------------------------------------------------------------
When you use the fteCreateTransfer command to copy an existing PDS data
set to a new data set that is to be created by fteCreateTransfer, a PDSE
data set is created by default.

For example the following command copies the PDS data set
'test.pds.orig' to a new data set 'test.pds.new':
fteCreateTransfer -sa ZOS2 -da ZOS1 -dp "//test.pds.new" "//test.pds.orig"

You can create a PDS rather than the default PDSE by specifying the
DSNTYPE(PDS) attribute. For example:

fteCreateTransfer -sa ZOS2 -da ZOS1 -dp "//test.pds.new;DSNTYPE(PDS)" "//test.pds.orig"


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.


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 here:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/welcome/WelcomePagev7r0.html

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 here:
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.1
----------------------------------------------------------------------------------------------
Version 7.0.1 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


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

TRADEMARKS

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

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

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