Product readme for WebSphere MQ File Transfer Edition, Version 7.0.4.1

Content

IBM WebSphere MQ File Transfer Edition, Version 7.0.4.1 readme file
November 2011

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

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

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

README FILE UPDATE HISTORY:
October 11 2011 - readme file sent for translation
November 28 2011 - readme published online

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


DESCRIPTION
-----------
This readme file for IBM WebSphere MQ File Transfer Edition Version 7.0.4.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?rs=171&uid=swg27006097


COMPATIBILITY
-------------
You can install Version 7.0.4.1 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 7.0.4.1.

Before installing Version 7.0.4.1, 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 7.0.4.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.4.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.


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


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

AIX:
AIX_ppc/VM

HP-UX on Itanium:
HPUX_IA64/VM

HP-UX on PA-RISC:
HPUX_PARISC/VM

Linux on System x:
Linux_x86/VM

Linux on System p:
Linux64_SystemP/VM

Linux on System z:
Linux_Systemz/VM

Solaris on SPARC:
Solaris_SPARC/VM

Solaris on System x:
Solaris_x86/VM

Windows:
Windows_x86/VM

IBM i:
IBMi/VM


WebSphere MQ File Transfer Edition components
---------------------------------------------
There are three possible Version 7.0.4.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 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 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.4.1
-------------------------------------------

Enabling the new function in Version 7.0.4.1
--------------------------------------------
To enable this function for agents and command-line tools, add the enableFunctionalFixPack property to the wmqfte.properties file. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/props_wmqfte.htm

This property does not enable the new function in the WebSphere MQ Explorer plug-in. After installing V7.0.4.1 and starting WebSphere MQ Explorer, you can enable the new function from the Preferences pane.


Enhancements to the protocol bridge
-----------------------------------
- You can use a protocol bridge agent to transfer files to and from multiple protocol file servers. For more information, see http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/protocol_bridge.htm

and http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/protocol_bridge_properties_format.htm

- The protocol bridge supports a subset of the FTPS protocol. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/ftps_support.htm

and http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/protocol_bridge_config_ftps.htm

- You can use FTP in passive mode by setting the passiveMode attribute. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/protocol_bridge_properties_format.htm


Enhancements to existing commands
--------------------------------
- You can redirect command trace from the current directory to your specified directory. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/tracing_cmds.htm

- To specify programs to start at the source and destination agents, you can now use the fteCreateTransfer command, in addition to the previous method of using an Ant task. For more information, see http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/start_new_transfer_cmd.htm

and
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/invoking_examples.htm

- Use the com.ibm.wmqfte.propertyset property to specify a set of configuration options to use for Ant tasks. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/fteant.htm

- ftePingAgent command messages now time out rather than going to the designated dead-letter queue if a wait time has been set. The command messages will not time out if the command has been set to wait indefinitely. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/ping_agent_cmd.htm

- You can specify a timeout for the fteCreateTransfer command with the -w parameter. Previously, specifying this parameter caused the command to wait indefinitely for the agent to respond. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/start_new_transfer_cmd.htm

- You can use the fteCleanAgent command to specify which transfer-related objects you want to delete (in-progress and pending transfers, resource monitor definitions, or scheduled transfer definitions for a particular agent). For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/clean_agent_cmd.htm

- The output from the -v parameter on the fteShowAgentDetails command now includes host name, product version, trace level, and First Failure Data Capture (FFDC) specification. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/show_agent_cmd.htm

- You can export and import a resource monitor configuration to an XML file using the -ox and -ix parameters on the fteCreateMonitor command. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/create_monitor_cmd.htm

- You can export an existing resource monitor configuration to an XML fileusing the -ox parameter on the fteListMonitors command. For more information, see http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/list_monitors_cmd.htm

- You can update a monitor configuration dynamically either based on an existing XML configuration or starting again from the beginning using the -f and -c parameters on the fteCreateMonitor command. For more information, see http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/create_monitor_cmd.htm

- You can specify record delimiters for binary transfers from data sets using the -srdb parameter on the fteCreateTransfer command. For more information, see http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/start_new_transfer_cmd.htm

- You can select whether to keep or strip trailing spaces from fixed-record format data sets for text transfers using the -skeep parameter on the fteCreateTransfer command. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/start_new_transfer_cmd.htm


Enhancements to the agent
-------------------------
- You can enable WebSphere MQ client channel header compression for individual agents, using the property agentHeaderCompression. For more information, see http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/properties.htm


Enhancements to user exit routines
----------------------------------
- You can manage the properties of a large number of protocol file servers by implementing the com.ibm.wmqfte.exitroutine.api.ProtocolBridgePropertiesExit interface. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/using_protocol_bridge_props_exits.htm

- You can map protocol bridge credentials for multiple endpoints using the com.ibm.wmqfte.exitroutine.api.ProtocolBridgeCredentialExit2 interface. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/protocol_bridge_credentials_exits.htm

- You can configure custom code to perform the underlying file system I/O work for WebSphere MQ File Transfer Edition transfers using the IOExit interfaces. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/using_io_exits.htm


Ease-of-use improvements in the WebSphere MQ Explorer plug-in
-------------------------------------------------------------
- You can sort the columns in any of the panels by left-clicking the column header in the Navigator View.
- The Pending Transfers panel now shows the optional job name assigned to each file transfer.
- There is a new wizard to create transfers, monitors and templates, which replaces previous wizards. The new wizard includes the following features:
- When creating a new file transfer request for local files, you can now use
a Browse button to navigate to the files.
- You can now edit the details in a previously-saved transfer request
template.
- As part of a file transfer request, you can now specify a program,
Ant script, or JCL job to run either before a transfer starts or after it
finishes.
- The wizard provides help in specifying variable substitution values in the
transfer elements.
- You can specify a Job Name for a file transfer.
- There is an improved method of specifying BPXWDYN parameters for data sets.
- You can now edit an existing monitor's configuration by selecting it and
using the right-click context menu on the Monitors panel.


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

Restrictions of the Connect:Direct bridge
-----------------------------------------
The Connect:Direct bridge has a number of restrictions. For more information, see
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/cd_restrictions.htm


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


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.1 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.1 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 7.0.4.1 silently
---------------------------------
If you want to install Version 7.0.4.1 silently, perform a console installation of Version 7.0.4.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.4.1 response file to install silently.

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

An example response file is provided in the following location in V7.0.4.1: <platform_name>/VM


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.1. You must also remove any configuration associated with the driver.

For information about how to uninstall and remove an Early Design Program driver, see:
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/eap_uninstall.htm


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


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


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


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


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 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
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.4.1
-------------------------------------------------------------------
You can find the list of fixes included in Version 7.0.4.1, which were first included in Fix Pack 7.0.2.1, at:
http://www.ibm.com/support/docview.wss?rs=171&uid=swg27015313


USEFUL LINKS
------------
In addition to this readme.txt file, you can find more information on the WebSphere MQ File Transfer Edition website at:
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/

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


++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
COPYRIGHT AND TRADEMARK INFORMATION

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

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

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

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

For more information, see http://www.ibm.com/legal/copytrade.shtml