Product readme file for WebSphere MQ File Transfer Edition version 7.0.2.1

Content

IBM WebSphere MQ File Transfer Edition, version 7.0.2.1 readme file March 2010

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

CONTENTS
--------
- Readme file update history
- Description
- Announcement
- System requirements
- Installing WebSphere MQ File Transfer Edition Fix Pack 7.0.2.1
- Limitations and known problems
- List of fixes included from Fix Pack 7.0.0.1 onwards
- Useful links
- Notices and trademarks

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

README FILE UPDATE HISTORY:

February 3 2010 - readme file shipped to translation
March 10 2010 - readme file published online

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


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

For the very latest version of this readme file always refer
to:
http://www.ibm.com/support/docview.wss?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



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 THIS FIX PACK
------------------------
Before you can install this fix pack, you must already have installed
one of the following previous versions of WebSphere MQ File Transfer Edition:
7.0.0.0, 7.0.0.1, 7.0.1, or 7.0.2.

The fix pack installer uses your existing product configuration so
you will not be asked to enter any configuration information during fix
pack installation.

As with previous versions of WebSphere MQ File Transfer Edition, there are
three possible components for the fix pack: Server, Client, or Remote Tools
and Documentation.

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

AIX:
AIX_ppc/Disk1/InstData/VM

HP-UX on Itanium:
HPUX_IA64//Disk1/InstData/VM

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

Linux on System x:
Linux_x86/Disk1/InstData/VM

Linux on System p:
Linux64_SystemP/Disk1/InstData/VM

Linux on System z:
Linux_Systemz/Disk1/InstData/VM

Solaris:
Solaris_SPARC/Disk1/InstData/VM

Windows:
Windows_x86/Disk1/InstData/VM

IBM i:
IBMi/Disk1/InstData/VM

Installing on UNIX, Linux, and Windows platforms
------------------------------------------------

1. Extract the contents of the fix pack .zip file.

2. Launch the fix pack installation wizard, using the executable file or
binary file.

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

3. Select the language that you want to use for the installation process.
Click OK.

4. On the Introduction panel, click Next.

5. Read the software license agreement and select the option to accept
the terms of the license. Click Next.

6. Select the same installation directory as you used to install the previous
version of the product. Click Next.

7. Click Update existing install.

8. Read the summary panel and click Install.

9. Wait while the fix pack is installed and click Done.


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 fix pack installer on an IBM i platform, complete the following
steps:

1. Download and copy the fix pack eAssembly image to an IFS directory on your
IBM i system. You are recommended to create a subdirectory with the
following name for this purpose:
/home/<your user profile>/QFTEfp7021
This subdirectory will be referred to in subsequent steps.

2. Quiesce FTE operations:
a. Use the IBM i command WRKSBSJOB SBS(QFTE) to display QFTE jobs and
agents that are currently running.
b. If the QFTE subsystem is active and agent jobs are present,
use Qshell fteStopAgent commands to end the agents that are currently
running.
c. To end the QFTE subsystem, use the IBM i command ENDSBS SBS(QFTE).

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

While you are in PASE complete the following steps:

a. Change directory to the directory you used in step 1 above. For example:
cd /home/<your user profile>/QFTEfp7021

b. Start the installer using the following command:
./IBMi/Disk1/InstData/VM/install -i console

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

c. 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 are complete. You will then
receive another message indicating that you should press F3=Exit function
key to exit the PASE environment.

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

5. Restart the agents that were running before you began installation. These
are the agents you ended in step 2.


Installing on z/OS
---------------------
Apply the PTF for APAR PM06862.


WebSphere MQ File Transfer Edition components
---------------------------------------------
As with earlier versions of WebSphere MQ File Transfer
Edition, there are three possible Version 7.0.2.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.

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



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

Installing V7.0.2.1 Fix Pack to AIX
-----------------------------------
If you apply the V7.0.2.1 Fix Pack to an existing installation of the Server,
Client, or Remote Tools and Documentation on AIX, you might see a number
of file lock errors reported in the install.log file.

To work around these errors, complete the following steps:
1. Stop all agents that you have created in previous versions of WebSphere
MQ File Transfer Edition using the fteStopAgent command.
2. After the agents have stopped, run the AIX command "slibclean".
You will need root administrator privileges to run "slibclean"
3. Rerun the fix pack installer.


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 Fix Pack V7.0.2.1 silently
-------------------------------------
If you want to install Fix Pack 7.0.2.1 silently, perform a console
installation of V7.0.2.1 first to create a response file as described in
the following topic:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/response_file_console.htm
Then use the newly-created V7.0.2.1 response file to install silently.

You cannot use a V7.0.2.0 response file that you previously created to install
V7.0.2.1 silently.


Interoperation between different levels of WebSphere MQ File Transfer
Edition
---------------------------------------------------------------------
Interoperation between agents at Version 7.0.2.1 (Fix Pack 7.0.2.1 on
distributed systems and PM06862 on z/OS) and agents at Versions 7.0.1 and 7.0.2 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 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 is 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, V7.0.2, or V7.0.2.1. 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 by using the following command:
rm -rf /QIBM/ProdData/WMQFTE
c. Remove the WMQFTE configuration by 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
----------------------------------------
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/database_logger.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™ 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.1
---------------------------------------------------------------------
You can find the list of fixes included in Fix Pack 7.0.2.1 at:
http://www.ibm.com/support/docview.wss?uid=swg27015313



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

The SupportPac(TM) Web page is at:
http://www.ibm.com/support/docview.wss?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/support/entry/portal/Software/WebSphere/WebSphere_MQ

Web documentation updates
The latest version of the WebSphere MQ File Transfer Edition product documentation 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




++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
NOTICES AND TRADEMARKS

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, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

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.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan

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

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR
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,
Winchester,
Hampshire,
England
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.

COPYRIGHT LICENSE:

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

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.

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.