Readme for WebSphere MQ V7, Fix Pack 7.0.0.1

Content

Readme file for: IBM WebSphere MQ v7 for UNIX and Windows.
Product/Component Release: 7.0
Update Name:Fix Pack WebSphere MQ v7.0.0.1
Fix ID:

* 7.0.0-WS-MQ-AixPPC64-FP0001.tar.Z
* 7.0.0-WS-MQ-HpuxPaRISC64-FP0001.tar.Z
7.0.0-WS-MQ-HpuxIA64-FP0001.tar.Z
* 7.0.0-WS-MQ-SolarisSparc64-FP0001.tar.Z
7.0.0-WS-MQ-SolarisX64-FP0001.tar.Z
* 7.0.0-WS-MQ-LinuxIA32-FP0001.tar.gz
7.0.0-WS-MQ-LinuxX64-FP0001.tar.gz
7.0.0-WS-MQ-LinuxPPC64-FP0001.tar.gz
7.0.0-WS-MQ-LinuxS390X-FP0001.tar.gz
* 7.0.0-WS-MQ-Windows-FP0001-CsCz.zip
7.0.0-WS-MQ-Windows-FP0001-DeDe.zip
7.0.0-WS-MQ-Windows-FP0001-EnUs.zip
7.0.0-WS-MQ-Windows-FP0001-EsEs.zip
7.0.0-WS-MQ-Windows-FP0001-FrFr.zip
7.0.0-WS-MQ-Windows-FP0001-HuHu.zip
7.0.0-WS-MQ-Windows-FP0001-ItIt.zip
7.0.0-WS-MQ-Windows-FP0001-JaJp.zip
7.0.0-WS-MQ-Windows-FP0001-KoKr.zip
7.0.0-WS-MQ-Windows-FP0001-PlPl.zip
7.0.0-WS-MQ-Windows-FP0001-PtBr.zip
7.0.0-WS-MQ-Windows-FP0001-RuRu.zip
7.0.0-WS-MQ-Windows-FP0001-ZhCn.zip
7.0.0-WS-MQ-Windows-FP0001-ZhTw.zip

Publication Date: 19 January 2009
Last modified date: 19 January 2009


Contents

Download location
Prerequisites and corequisites

Installation information
Prior to installation
Downloading the fix pack to an appropriate location
Uncompressing the fix pack installation images
Extract the fix pack install files
Stopping all WebSphere MQ processes
Installation
Perform the necessary tasks after installation

More Information on Installations of JDK and Gskit
GSKit version history
Installing GSKit
Reverting to an earlier level of GSKit
Troubleshoot Installation from Support Site

Uninstalling
Additional Information
New in this fix pack
Known problems and their workarounds (if any)

List of fixes
Copyright and trademark information
Notices
Document change history

Download location

Download WebSphere MQ v7.0 for UNIX and Windows Fix Pack 7.0.0.1 from
the following location:

http://www.ibm.com/support/docview.wss?rs=171&uid=swg24021170 or
access the fix from the table below.

Below is a list of components, platforms, and file names that apply to
this readme file.

Product/Component Name Platform File
---------------------- --------------- ---------------------------------------
WebSphere MQ v7.0.0.1 AIX 7.0.0-WS-MQ-AixPPC64-FP0001.tar.Z
WebSphere MQ v7.0.0.1 HPUX PARISC 7.0.0-WS-MQ-HpuxPaRISC64-FP0001.tar.Z
WebSphere MQ v7.0.0.1 HPUX IA64 7.0.0-WS-MQ-HpuxIA64-FP0001.tar.Z
WebSphere MQ v7.0.0.1 Solaris Sparc 7.0.0-WS-MQ-SolarisSparc64-FP0001.tar.Z
WebSphere MQ v7.0.0.1 Solaris X86-64 7.0.0-WS-MQ-SolarisX64-FP0001.tar.Z
WebSphere MQ v7.0.0.1 Linux X86 7.0.0-WS-MQ-LinuxIA32-FP0001.tar.gz
WebSphere MQ v7.0.0.1 Linux X86-64 7.0.0-WS-MQ-LinuxX64-FP0001.tar.gz
WebSphere MQ v7.0.0.1 Linux s390x 7.0.0-WS-MQ-LinuxS390X-FP0001.tar.gz
WebSphere MQ v7.0.0.1 Linux PPC 7.0.0-WS-MQ-LinuxPPC64-FP0001.tar.gz
WebSphere MQ v7.0.0.1 Windows 7.0.0-WS-MQ-Windows-FP0001-EnUs.zip


Prerequisites and corequisites

Before downloading WebSphere MQ V7.0.0.1, perform the following steps:

1. Ensure that your system meets all of the system requirements:
http://www.ibm.com/software/integration/wmq/requirements/index.html
This action prevents technical problems that might occur after the
installation and configuration of the fix pack.

2. Review the Flashes and Authorized Problem Analysis Reports (APARs)
on the WebSphere MQ for UNIX and Windows product support Web
site:

http://www.ibm.com/software/integration/wmq/support/

APARs describe defects that have been addressed in a fix pack, For a
list of WebSphere MQ V7.0.0.1 APARs, refer to:

http://www.ibm.com/support/docview.wss?rs=171&uid=swg27014224

3. Ensure that you have sufficient file system free space to download
and extract the fix pack. You need to have a file system with one
gigabyte of free space to contain the compressed file and the
uncompressed installation image.

4. Ensure that you have the free space required to install the fix
pack. The free space must be available in the location of the
WebSphere MQ V7.0 copy that you are updating.

To determine the space used by the existing WebSphere MQ products on
UNIX platforms, perform the command:

du -k -s MQDIR

where MQ DIR represents the location where the WebSphere MQ product is
installed.

5. If you already have a WebSphere MQ V7.0 product installed and have
obtained special fixes, contact IBM(R) support to determine whether you
need an updated version of the fixes before you install WebSphere MQ
V7.0.0.1. This helps to ensure that your system is in a consistent
state and that no special fixes are lost.


Installation information

Before proceeding with the installation process, view the online
version of the readme file to check if information has changed since
the readme file download:

http://www.ibm.com/support/docview.wss?rs=171&uid=swg27014225

Prior to installation
---------------------
Before installing WebSphere MQ V7.0.0.1, perform the following steps:

1. Read all of this readme. Note particularly the additional steps
that are necessary if you have installed GSKit in order to use SSL
channels with WebSphere MQ.
2. Download the fix pack to an appropriate location
3. Uncompress the fix pack
4. Stop all WebSphere MQ processes and its applications.

Downloading the fix pack to an appropriate location
---------------------------------------------------
There must not be any spaces in the directory path where you plan to
download and uncompress the fix pack. If there are spaces in the
directory path, the installation will fail. For example, make sure
your directory path resembles the following:

/home/WMQFixPack/FP1/ ...

It should not resemble the following:

/home/WMQ FixPack/FP1/ ...

Uncompressing the fix pack installation images
----------------------------------------------
All fix pack installation images on the download site are compressed in
gz/Z/zip format. Before you can apply the fix pack from this format,
copy the downloaded file to a temporary directory and use
gunzip/uncompress and tar to extract the fix pack installation image.

Extract the fix pack install files
----------------------------------
To extract the fix pack install files, perform the following steps:

1. Copy the gzipped/Z image to a temporary location.
2. Change to the directory where you copied the image.
3. The following are example commands to extract the fix pack
installation image:

gunzip -c filename.tar.gz | tar -xvf -
uncompress filename.tar.gz | tar -xvf -
unzip filename.zip

where filename.tar.gz etc. is the name of the downloaded file.

Note on AIX: gunzip is part of the AIX 5L default installation
setup. If you do not have gunzip, install the rpm.rte fileset from
the AIX 5L installation media. The rpm.rte fileset contains gunzip.
You can also download gzip for AIX 5L from Web site:

http://www.ibm.com/servers/aix/products/aixos/linux/rpmgroups.html

Stopping all WebSphere MQ processes
-----------------------------------
You must ensure that all WebSphere MQ processes are stopped and do not
start automatically during the installation procedure. To stop all
WebSphere MQ processes, perform the following steps:

1. Log in as a user in the mqm group.
2. Use the endmqm command to stop all running queue managers.
3. Stop any listeners associated with the queue managers, using the
command:

endmqlsr -m QMgrName

4. To check that you have stopped all of them, enter the following:

ps -ef | grep mq

Check that there are no processes listed that are running command lines
beginning amq or runmq. Ignore any that start with amqi.

5. Take any further administrative actions (as root if necessary) to
stop all applications that use queue managers on the system, and
prevent them from restarting automatically during the installation
procedure

Installation
------------
Applying WebSphere MQ V7.0.0.1 Fix Pack to update an existing MQ
installation

AIX

1. Display the appropriate smitty panel using this sequence:
Software Installation and Maintenance
Install and Update Software
Install and Update From ALL Available Software
> Alternatively, use a fastpath command (smit[ty] install_update).
2. Select a value for INPUT device / directory for software. Click
the List button (or press the F4 key on smitty) to display a list of
valid values.
3. Complete the SOFTWARE to install field. Enter ALL to install all
applicable fileset updates to your installation.
4. If you think that at a later time you might want to reject the
service updates and return to the backup level, you must ensure that:
1. The COMMIT software updates value is set to no.
2. The SAVE replaced files value is set to yes.
By setting these values, you ensure that the updates are applied, and
the old filesets are saved, not overwritten.
5. Press Enter to display a confirmation message before starting the
update. While the command runs, it displays progress messages ending
with an installp Summary table, confirming which components of
WebSphere MQ for AIX. have been updated. If the command does not
complete successfully, a full error log is saved in the file smit.log
in root's home directory.

HP-UX

1. In the directory where the service update packages are located, use
swinstall to install the maintenance packages:

swinstall -s $PWD/hp-Uxxxxxx.v11 MQSERIES

Selecting to install the package at the product level (MQSERIES), will
automatically install only the components which match the set of
WebSphere MQ components that are already installed on the machine.
Unmatched components will fail at the prerequisite check, a warning
will be shown to inform you that the files will be analyzed before
install.

2. Special note

It is possible your administrator has created a depot containing both
the WebSphere MQ v6.0 product AND fix pack.

Note that you must install the base package first, followed by the
maintenance package. You may not select them both for simultaneous
install.

If you are installing WebSphere MQ v6.0 for HP-UX from a software
depot that has been created this way, you will need to use the install
option "autoselect_dependencies=false".

In the swinstall GUI, this can be done by unchecking the option
"autoselect dependencies when marking software" in the
"Options" -> "Change Options" panel.

Warning: Disabling the autoselect_dependencies will disable some
checking for dependencies and must not be used when uninstalling
maintenance packs.

Linux

1. Log in as root.
2. To find out which packages are installed on your machine, enter the
following:

rpm -q -a | grep MQSeries

For example, if you have a minimum WebSphere MQ installation and SDK
component, at level 7.0.0.0, this will return:

MQSeriesRuntime-7.0.0-0
MQSeriesSDK-7.0.0-0
MQSeriesServer-7.0.0-0

3. Now install all available updates for the packages you have on your
system:

rpm -ivh MQSeriesRuntime-Uxxxx-7.0.0-1.i386.rpm \
MQSeriesSDK-Uxxxx-7.0.0-1.i386.rpm \
MQSeriesServer-Uxxxx-7.0.0-1.i386.rpm

Note: You must install all 7.0.0.1 packages that apply to those 7.0.0.0
packages that are currently installed on your system.

4. Repeat step 2, and you will see that the Runtime, SDK and Server
packages are now at level 7.0.0.1:

MQSeriesRuntime-7.0.0-0
MQSeriesSDK-7.0.0-0
MQSeriesServer-7.0.0-0
MQSeriesRuntime-Uxxxxxx-7.0.0-1
MQSeriesSDK-Uxxxxxx-7.0.0-1
MQSeriesServer-Uxxxxxx-7.0.0-1

Solaris

1. Change into the directory containing the maintenance packages.
2. Enter the following:

pkgadd -d packagename

where packagename corresponds to the image file name, for example,

mqm-Uxxxxxx.img

3. Follow the on screen instructions.

Windows

Before installing this fix pack, remove any installed WebSphere MQ
interim and test fixes.

1. Run the uncompressed executable file installing a maintenance pack.
2. Running this file presents you with a dialog screen on which you
can choose to temporarily unpack or save the executable file. Select
the appropriate option (and if saving select the default folder, or
change it if required) and Click Install
3. Click Finish when the file has been unpacked into the temporary
folder to end the dialog.
4. The installation program AMQICSDN.EXE file now runs and presents
you with a dialog screen on which you can choose a folder in which to
back up any files that are to be changed by the maintenance process.

The Quick Beginnings for Windows manual, Chapter 4, section on
"Silently installing maintenance updates" describes the parameters
which can be passed when installing maintenance. These apply to
attended installations as well, that is when the -s flag is not set.

In particular, the option MQPINUSEOK is useful when the installation
fails reporting that files are in use (eg. AMQ4756).

Example syntax in this case would be:

WebSphereMQMDV7.0.0.1EnUs.exe [-s] -a MQPINUSEOK=1
(For the self extracting version from the web)

AMQICSDN.exe MQPINUSEOK=1
(Running amqicsdn from the unpacked version)

Where
The -s option tells the unpacking to run silently, and
the -a option passes the subsequent parameter to amqicsdn.exe.

Notes for 64-bit Windows operating systems.

Release 7.0.0.0 includes support for the V7.0 32-bit WebSphere MQ
product and 32-bit applications running on Windows XP Professional x64
Edition, Windows Server 2003 (Standard or Enterprise) x64 Edition,
Microsoft Windows Server 2008 (Standard or Enterprise 64-bit Edition)
and Microsoft Windows Vista (64-bit versions of Business, Enterprise or
Ultimate Edition).

To install the MQ v7.0.0.0 or later Fix Pack on x64 version operating
systems the Microsoft Visual C++ 2005 redistributable package must be
installed before the Fix Pack is installed. The language specific
version of "vcredist_x64.exe" is included in the downloadable zip file
and should be run prior to performing the Fix Pack installation on x64
Windows operating systems.

The Fix Pack installation checks to ensure the Microsoft Visual Studio
2005 redistributable version 8.0.50727.42 is correctly installed before
allowing installation of the Fix Pack. If, during the Fix Pack
installation, the correct files are not detected, a message is
displayed asking the user to install the bundled redistributable
"vcredist_x64.exe" on the x64 operating system.

The Fix Pack installation does not need to be cancelled in this case.
After installing the correct redistributable select Retry on the
message box to continue the Fix Pack installation.

When running a silent Fix Pack installation, no message box is displayed
if the correct level of Microsoft Visual C++ 2005 redistributable
cannot be detected. Instead, the Fix Pack installation fails and an
entry is written into the Fix Pack log file detailing the problem. To
automate the Fix Pack installation silently, the Microsoft Visual C++
2005 redistributable can also be silently installed prior to installing
the MQ Fix Pack using "vcredist_x64.exe /Q" option"

Install directories used on 64-bit Windows operating systems.

On 64-bit Windows, the default installation location is 'C:\Program
Files (x86)\IBM\WebSphere MQ'. On 32-bit windows the default is
'C:\Program Files\IBM\WebSphere MQ'.

If the user modifies the default location to 'C:\Program Files\....'
the Microsoft Windows Installer (MSI) will change this to 'C:\Program
Files (x86)\....'. If the user sets the default location to some other
value, MSI does not change its value.

Note - Please also refer the Quick Beginnings manuals for more
information on how to install or remove the fix pack.

Perform the necessary tasks after installation
----------------------------------------------
After installing WebSphere MQ V7.0.0.1, perform the following steps:

1. Verify the installation. Refer Quick beginning guides of the
respective platforms.
2. Restart the MQ Queue Managers

After applying a fix pack, it is not mandatory to recompile
applications. However, to take advantage of any changes to the files
linked to in the application, recompiling applications is recommended.


More Information on Installations of JDK and GSKit
--------------------------------------------------
This fix pack does not include the IBM Java SDK.

The IBM Java SDK shipped with version 7.0.0.0 is 1.5.0 SR5.


GSKit version history
---------------------
The versions of GSKit shipped with the V7.0 products is

WebSphere MQ GSKit
Version version
-------------- -------------
7.0.0.1 7.0.4.20
7.0.0.0 7.0.4.14


Installing GSKit
----------------
Windows

On Windows the new version will be installed automatically when the fix
pack is installed and will be removed if the fix pack is removed.


AIX

Install the gskta.rte and gsksa.rte packages from the installation
media using the installp command, for example, assuming the media
containing the fix pack is the current directory:

installp -ac -d. gskta.rte gsksa.rte

The level of GSKit provided with this fix pack, 7.0.4.20, requires the
following system patches (listed by version of AIX) to be installed
before GSKit is installed.

AIX 5.2.0:
xlC.aix50.rte.6.0.0.3 or later

AIX 5.3.0:
xlC.aix50.rte.6.0.0.3 or later
If running Technical Level 5, bos.rte.libc:5.3.0.53 or greater is required

Solaris

Shut down all MQ applications and any other products that are using
GSKit. Before installing the WebSphere MQ fix pack uninstall the old
level of the GSKit packages using the commands:

pkgrm gsk7bas

pkgrm gsk7bas64

During the uninstallation process you will be warned that other
products have a dependency on the GSKit packages, reply 'Yes' to
continue the uninstallation process.

When installing the WebSphere MQ fix pack the new GSKit packages
gsk7bas and gsk7bas64 will be listed with the WebSphere MQ package.

If the system uses SSL channels, or will use SSL channels, these should
BOTH be selected for installation.

This is because both 64-bit and 32-bit processes may need to load GSKit
libraries.

The level of GSKit provided with this fix pack, 7.0.4.20, requires the
following system patches (listed by version of Solaris) to be installed
before GSKit is installed.

Solaris v8 for SPARC(for both 32 and 64 bit GSkit binaries):
108434-14 or later,
111327-05 or later,
108991 or later,
108993-31 or later,
108528-29 or later,
113648-03 or later,
116602-01or later,
111317-05 or later,
111023-03 or later,
115827-01 or later

Solaris v9 for SPARC(for both 32 and 64 bit GSkit binaries):
111711-08 or later

Linux

Before installing the WebSphere MQ fix pack upgrade the GSKit packages
using the rpm -U command as follows ( xxxx represents the architecture
string for the platform )

For a system where a 32-bit version of GSKit is installed:
rpm -U gsk7bas-7.0-4.20.xxxx.rpm

and

For a system where a 64-bit version of GSKit is installed:
rpm -U gsk7bas64-7.0-4.20.xxxx.rpm

Ensure that, on 64-bit platforms, BOTH packages are installed. This is
because both 64-bit and 32-bit processes may need to load GSKit
libraries.

The level of GSKit provided with this fix pack, 7.0.4.20, requires the
following system patches (listed by version/flavor of Linux) to be
installed before GSKit will install.

Linux on PPC32 / PPC64:
RHEL v5.0 requires compat-libstdc++-33-3.2.3-61 or later

Linux on x86:
Red Hat Enterprise Linux 4.0 ES requires compat-libstdc++-33-3.2.3-47.3
or later
Red Hat Enterprise Linux 5.0 ES requires compat-libstdc++- 33-3.2.3-61
or later

Linux on s390:
Red Hat Enterprise Linux 4.0 AS requires compat-libstdc++-33-3.2.3-47.3
or later
RHEL 5.0 requires compat-libstdc++-33-3.2.3-61 or later

Linux on x86_64:
RHEL 4.0 WS/AS/ES requires compat-libstdc++-33-3.2.3-47.3 or later
RHEL 5.0 ES requires compat-libstdc++-33-3.2.3-61 or later

Linux on s390x:
Red Hat Enterprise Linux 4.0 AS compat-libstdc++- 33-3.2.3-47.3 or
later
RHEL 5.0 compatlibstdc++-33-3.2.3-61 or later

HP-UX

The GSKit packages are included in the same depot as the WebSphere MQ
fix pack. Selection of the MQSERIES filesets for installation will
automatically select the appropriate GSKit packages.

HP-UX for PA-RISC:
The level of GSKit provided with this fix pack, 7.0.4.20, requires the
following system patches (listed by version of HP-UX) to be installed
before GSKit will install.

32-bit HP-UX 11i:
PHSS_26946 or later,
PHSS_33033 or later,
PHCO_34275 or later

64-bit HP-UX 11i:
PHSS_26946 or later,
PHSS_33033 or later,
PHCO_34275 or later


Reverting to an earlier level of GSKit
--------------------------------------
If you need to revert to an earlier level of GSKit you should uninstall
the currently installed level using the appropriate uninstall command
for your operating system and reinstall the required level from the
media on which it was supplied using the instructions that came with
it.

Note that you should normally use the highest level of GSKit required
by any product in use on the system.


Troubleshoot Installation from Support site
-------------------------------------------
Before contacting IBM you are recommended to view the web site
http://www.ibm.com/support/docview.wss?rs=171&uid=swg21229861 which has
specific advice on problem solving and data collection for WebSphere
MQ.


Uninstalling

Prior to uninstallation
-----------------------
You must ensure that all WebSphere MQ processes are stopped. To stop
all WebSphere MQ processes, perform the following steps:

1. Log in as a user in the mqm group.
2. Use the endmqm command to stop all running queue managers.
3. Stop any listeners associated with the queue managers, using the
command:

endmqlsr -m QMgrName

4. To check that you have stopped all of them, enter the following:

ps -ef | grep mq

Check that there are no processes listed that are running command
lines beginning amq or runmq. Ignore any that start with amqi.

5. Take any further administrative actions (as root if necessary) to
stop all applications that use queue managers on the system, and
prevent them from restarting automatically during the installation
procedure

Uninstalling WebSphere MQ Fix Pack 7.0.0.1
------------------------------------------

AIX

1. Display the appropriate smit panel using this sequence:
2. Software Installation and Maintenance
Software Maintenance and Utilities
Reject Applied Software Updates (Use Previous Version)

Alternatively, use a fastpath command (smitty install_reject).
3. Complete the SOFTWARE name field. Enter MQM to restore all
applicable fileset updates to your installation.

Note: Although there is an option to restore only selected fileset
updates for WebSphere MQ for AIX, this still results in all applicable
fileset updates for the service update being restored.

4. Use the displayed default values for all other fields to reject the
current service level and reinstate the previous service or install
level.
5. Press Enter to display a confirmation message, before starting the
reject process. While the command runs, it displays progress messages
terminating with an Installp Summary table, confirming which components
of WebSphere MQ for AIX have been rejected.

HP-UX

1. Use the swremove command to remove the maintenance package from the
system. For example, to remove the 7.0.0.1 maintenance level, use the
command:

swremove MQSERIES,r=7.0.0.1

Make sure that autoselect_dependencies is set to true before you remove
any maintenance packages from the system.

Solaris

1. Use the pkgrm command to remove the latest service update from the
system.

pkgrm packagename

where packagename is the name of the package that you want to remove.
Note: Ignore any error messages of the form <shared pathname not
removed>.

2. If you have installed a WebSphere MQ client, and the client was
updated after installing the service level that is being removed, you
must specifically update your WebSphere MQ client installation again,
after the service level has been removed.

Linux

1. Log in as root.
2. To find out which packages are installed on your machine, enter the
following:

rpm -q -a | grep MQSeries

Using the example given in Applying service, the above command returns:

MQSeriesRuntime-7.0.0-0
MQSeriesSDK-7.0.0-0
MQSeriesServer-7.0.0-0
MQSeriesRuntime-Uxxxxxx-7.0.0-1
MQSeriesSDK-Uxxxxxx-7.0.0-1
MQSeriesServer-Uxxxxxx-7.0.0-1

3. Remove all the updates applied at level 1, with the following commands:

rpm -ev MQSeriesRuntime-Uxxxxxx-7.0.0-1 \
MQSeriesSDK-Uxxxxxx-7.0.0-1 MQSeriesServer-Uxxxxxx-7.0.0-1

4. Repeat step 2 to check that the update packages have been removed:

MQSeriesRuntime-7.0.0-0
MQSeriesSDK-7.0.0-0
MQSeriesServer-7.0.0-0


Windows

1. Ensure that you are logged on as an Administrator.
2. Ensure that all queue managers are stopped.
3. Ensure that all channel listeners are stopped.
4. Ensure that the IBM. WebSphere MQ Service has stopped.
Click either
Start > Programs > IBM WebSphere MQ > Remove Refresh Pack
Start > Programs > IBM WebSphere MQ > Remove Fix Pack
5. Click Remove to start the process. This returns the installation to the
state it was in before the maintenance package was applied.

Note - Please also refer the Quick Beginnings manuals for more
information on how to install or remove the fix pack.


Additional Information


Known problems and their workarounds (if any)
---------------------------------------------
1. If using WebSphere MQ v7.0.0.1 (Distributed) or WebSphere MQ
v7.0.0.0 (z/OS) with WebSphere Application Server 6.0.2 or WebSphere
Application Server 6.1 using MLP with WMQ security enabled, JMS
Connection Factories must use bindings mode. This is only applicable
though if publish/subscribe messaging is in use.

An Unexpected Error is returned from
com.ibm.mq.jmqi.remote.internal.RemoteFAP.MQGET, where the MQGET call
is the result of method
com.ibm.msg.client.jms.internal.JmsSessionImpl.consume, which is used
to consume message references within an application server.

The reason for the failure is that the object handle (HOBJ) being used
to consume the message is invalid/null.

2. RFH2 Publication and Subscription messages do not currently support
the character strings &lt, &gt, &eq, &ne in the RFH2 header.
If an RFH2 message header contains any of these strings, the message
will be rejected with MQRCCF_COMMAND_FAILED.

3. When using WebSphere MQ Version 7 with WebSphere Application Server
Version 6.1 on iSeries, the following error occurs:

java.lang.UnknownError: Exception occurred in ILE native method, see joblog.
at com.ibm.mq.jmqi.local.internal.base.Native.MQCB(Native Method)
at com.ibm.mq.jmqi.local.LocalMQ$6.run(LocalMQ.java:1673)
at com.ibm.mq.jmqi.JmqiWorkerThread.run(JmqiWorkerThread.java:180)

When the error occurs, the joblog contains the following information:

Boundary alignment of pointer or template not valid.
Application error. MCH0602 unmonitored by MQJBND at statement 0000000029, instruction X'0000'.
Boundary alignment of pointer or template not valid.
Application error. MCH0602 unmonitored by MQJBND at statement 0000000029, instruction X'0000'

Workaround: To prevent this error from occurring, configure WebSphere Application Server to
use the Classic JVM, by executing the command:

/QIBM/ProdData/WebSphere/AppServer/V61/Base/bin/enableJVM -jvm classic -profileName <profile name>

and then restart the application server.

4. When WMQ v7.0.0.1 is installed in a non-English environment, some
messages in MQ Explorer may still appear in English and may not
display the latest translation. This is caused by a bug in Eclipse
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=201489).

To install the Eclipse fix for this issue, MQ Explorer first needs to be run in
Eclipse Workbench mode. This can be selected from the Window > Preferences
menu under "WebSphere MQ Explorer". MQ Explorer needs to be restarted
for this to take effect. On Linux platforms in order to be able to view and install
updates the MQ Explorer needs to be run as root.

The update manager can then be launched from the Help > Software Updates
menu. Select "Find and Install..." then ensure "Search for updates of the currently
installed features" is selected, and press Finish. Select "RCP Patch (bug:201489)"
from the available updates and follow the instructions to install the fix. To return
MQ Explorer to standalone mode if required, select the appropriate option from the
"WebSphere MQ Explorer" preferences page.

5. Loop detection has not been implemented for PCF publications. A pcf publisher is
an application doing queued pub/sub using a pcf msg format publication message.

A problem will occur if a hierarchy with active PCF publishers is migrated into a
pub/sub cluster or, a hierarchy which uses clustering for its channel connectivity
has a clustered topic defined.

This will cause an infinite loop where the message will be repeatedly sent between
two or more queue-managers.

If the messages are non-persistent then the problem can be resolved by stopping
and restarting all the queue managers that are part of the loop.

However, if the messages are persistent it will be necessary to alter the
queue-managers to disable pubsub (mqsc: "alter qmgr pubsub(disable")) and then
delete all in-flight messages.

To prevent this situation occurring when migrating hierarchies with PCF publishers
to a pub/sub cluster, all PCF publishing applications should be quiesced for the
duration of the topology migration and only restarted once all the queue managers
have been moved into the cluster and all hierarchy connections have been removed
using mqsc: "alter qmgr parent(' ')".

6. When deploying WMQ v7.0.0.1 on / within a WAS environment on z/OS please refer
to the technote below (as appropriate, inline with the WAS version you are using).

Information about using WebSphere MQ as the JMS provider for WebSphere Application Server Version 6.0.2
http://www.ibm.com/support/docview.wss?rs=0&q1=1307212&uid=swg21307212

Information about using WebSphere MQ as the JMS provider for WebSphere Application Server Version 6.1
http://www.ibm.com/support/docview.wss?rs=0&q1=1307203&uid=swg21307203

Information about using the WebSphere MQ messaging provider for WebSphere Application Server Version 7
http://www.ibm.com/support/docview.wss?rs=171&uid=swg21316899


List of fixes

Fixes included in WebSphere MQ V7.0.0.1:

http://www.ibm.com/support/docview.wss?rs=71&uid=swg27014224


Copyright and trademark information

http://www.ibm.com/legal/copytrade.shtml

Notices

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 jurisdictions 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 publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino,
Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and
Pentium are trademarks or 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.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to certain
software code. The relevant terms and conditions, notices and other
information are provided or referenced below. Please note that any
non-English version of the licenses below is unofficial and is provided
to you for your convenience only. The English version of the licenses
below, provided as part of the English version of this file, is the
official version.

Notwithstanding the terms and conditions of any other agreement you may
have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

* the Excluded Components are provided on an "AS IS" basis
* IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT
LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE
IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE
* IBM will not be liable to you or indemnify you for any claims related
to the Excluded Components
* IBM will not be liable for any direct, indirect, incidental, special,
exemplary, punitive or consequential damages with respect to the
Excluded Components.

Document change history
-----------------------
Date Description of Change
------------- ------------------------------------------------------------
11 Nov 2008 WebSphere MQ V7.0.0.1 memo.ptf file created.
19 Jan 2009 Updated publish date.