IBM Support

Product readme for V6.0.0.0

Product readme


Abstract

This document contains the WebSphere® MQ readme for product version 6.0.0.0.

Content

---------------------------------------------------------------------

IBM® WebSphere MQ, Version 6.0 release notes for all distributed platforms: AIX®, HP-UX, iSeries™, Linux®, Solaris, and Windows®.

© Copyright International Business Machines Corporation 2005. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

---------------------------------------------------------------------


Welcome to the IBM WebSphere MQ V6.0 release notes for all distributed platforms: AIX, HP-UX, iSeries, Linux, Solaris, and Windows.

This release notes file applies to WebSphere MQ documentation dated May 2005.

  • Description
  • Update history
  • Supported hardware and software
  • Getting started
  • Updates, limitations, and known problems
  • Documentation updates
  • Contacting IBM Software Support
  • Trademarks

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

DESCRIPTION

This release notes file contains information that was not available in time for our publications. It also details updates, limitations, and known problems. In addition to this file, README.TXT, you can find more information on the WebSphere MQ Web site:

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

The SupportPac™ Web page is at:

http://www-1.ibm.com/support/docview.wss?rs=977&uid=swg27007205

For current information on known problems and available fixes, see the Support page of the WebSphere MQ Web site at:

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


Web documentation updates:
The latest updates to the Web-based WebSphere MQ documentation are now available from the WebSphere MQ Web site at:

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

If you do not have access to the Internet, any additions to the readme file made between translation and the manufacturing of this media can be found on the server installation CD at:

pathname\READADD.txt

Announcement letter

The announcement letter for WebSphere MQ Version 6.0 (US English) is available on the Web at http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&htmlfid=897/ENUS205-094

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

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

UPDATE HISTORY
29 Apr 2005 - US English version of this file sent to translation.

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

SUPPORTED HARDWARE AND SOFTWARE

See the announcement letter (US English) for details at:
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&htmlfid=897/ENUS205-094

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

GETTING STARTED

This section covers critical information related to installation, migration, upgrade, or configuration.


Getting started on all WebSphere MQ distributed platforms

Important information for Beta driver users

If you have previously installed a WebSphere MQ V6.0 Beta driver, you MUST uninstall this driver and clean up any remaining files BEFORE you install the GA version of WebSphere MQ V6.0.

Migrating to WebSphere MQ V6.0

Immediately after you migrate to WebSphere MQ V6.0, you must start your queue manager at least once to migrate your file system structure before you start any WebSphere MQ listeners. Otherwise, you will not be able to start WebSphere MQ listeners after migration.

Cryptographic hardware

The following cards have not been confirmed to be working with IBM WebSphere MQ V6.0 at the time of publication:

IBM 4758-023 on Windows and AIX

IBM 4758-002 on i5/OS(TM)

Eracom Orange on Windows

4960 on Linux (x86) and Linux (zSeries)®

PCICA on Linux (zSeries)

Additional note:
The BHAPI interface is a legacy interface and is no longer being actively updated by the cryptographic card manufacturers. It is potentially unreliable when working with modern key formats. Its continuing support by GSKit is also in doubt. So WebSphere MQ are now only going to support this interface to continue support already provided on WebSphere MQ V5.3, for the nCipher nFast 200 on Solaris 8.

SOAP interoperability

WebSphere MQ supports the interoperation between WebSphere Application Server SOAP/JMS and SOAP/WebSphere MQ. All scenarios work with the base level of WebSphere
Application Server SOAP/JMS, except WebSphere Application Server SOAP/JMS client invoking a SOAP/WebSphere MQ Web .NET Web service. For this scenario to function, you require the following WebSphere Application Server APARs:

WebSphere Application Server 5.x - PK05013
WebSphere Application Server 6.x - PK05012

WebSphere MQ also supports the interoperation between CICS® SOAP/JMS and SOAP/WebSphere MQ. This functionality has a prerequisite of CICS APAR PK04615.

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

Getting started on WebSphere MQ for AIX

Installing the WebSphere MQ for AIX client without SSL

This information was not available in time for the WebSphere MQ for AIX V6.0 Quick Beginnings before it was sent to translation.

To install the AIX client without SSL code, do NOT select the following filesets for install:
mqm.keyman.rte
gsksa.rte
gskta.rte

JDK prerequisites for WebSphere MQ for AIX

When you install the JDK shipped with WebSphere MQ for AIX for the first time, the fileset: Java14.ext.java3d 1.4.2.0 has a prerequisite of the following two fileset updates:
OpenGL.OpenGL_X.rte.base 5.1.0.50
OpenGL.OpenGL_X.rte.soft 5.1.0.50

If you require these two updates, you will receive an error message to that effect.

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

Getting started on WebSphere MQ for HP-UX

Installing WebSphere MQ V6.0 on HP-UX where the product and
maintenance packs have been put into the same software depot.


If you are attempting to install WebSphere MQ V6.0 for HP-UX from a software depot that also contains a WebSphere MQ V6.0 maintenance package, you will need to use the install option "autoselect_dependencies=false". In the swinstall GUI, you can select this by unchecking the option "autoselect dependencies when marking software" in the "Options"->"Change Options" panel.

You must install the base package first, followed by the maintenance package. You can not select them both for simultaneous install.


GC34 - 6479 - WebSphere MQ for HP-UX Quick Beginnings

The information between <added text> and <end added text> is new and was written after the following book was sent to translation.

Chapter 2 "Installing a WebSphere MQ server"

Section: "Preparing for installation"
"Checking prerequisite hardware and software"
"Checking the operating environment"
"Operating System"

The operating system supported by WebSphere MQ for HP-UX, Version 6.0 is:

HP-UX 11i v1 (11.11) 64 bit plus Dec. 2003 Quality Pack

<added text>
To use SSL applications with HP-UX 11i v1, install the following patches or equivalent:
superseding levels before you install WebSphere MQ Version 6.0.
PHSS_26946
PHCO_29960
PHCO_27434
PHKL_28489
PHSS_28871
<end added text>

HP-UX 11i v2 (11.23) 64 bit


Chapter 3 "Installing a WebSphere MQ Client"

Section: "Preparing to install"
"Checking hardware and software requirements"
"Checking the operating environment"
"Operating System"

The information between <added text> and <end added text> is new and was written after the book was sent to translation.

The operating system supported by WebSphere MQ for HP-UX, Version 6.0 is:

HP-UX 11i v1 (11.11) 64 bit plus Dec. 2003 QPK

<added text>
To use SSL applications with HP-UX 11i v1, install the following patches or equivalent
superseding levels before you install WebSphere MQ Version 6.0.
PHSS_26946
PHCO_29960
PHCO_27434
PHKL_28489
PHSS_28871
<end added text>

HP-UX 11i v2 (11.23) 64 bit

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

Getting started on WebSphere MQ for iSeries

SSL channels between WebSphere MQ for iSeries, V5.3 and
WebSphere MQ, V6.0

If you are running SSL channels between queue managers on WebSphere MQ for iSeries, V5.3 and queue managers on WebSphere MQ, V6.0 (any platform), you must install Fix Pack 11 (CSD11) to ensure interoperability.

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

Getting started on WebSphere MQ for Linux

Migrating from earlier versions of WebSphere MQ for Linux

If you are migrating from a previous version of WebSphere MQ for Linux, you must uninstall your current version before installing WebSphere MQ Version 6.0. See WebSphere MQ for Linux V6.0 Quick Beginnings for instructions.

The use of RPM upgrade tools to migrate directly from one version of WebSphere MQ to another is not supported.

If you have already tried to upgrade WebSphere MQ using rpm -U or rpm -F, you might have deleted your old WebSphere MQ package entries from the RPM database without removing the product from your system. You might also have partially installed WebSphere MQ Version 6.0.

To continue upgrading to WebSphere MQ V6.0:
1. Find out which WebSphere MQ packages still have entries in your RPM database using:

rpm -qa | grep MQSeries


2. Remove all remaining WebSphere MQ packages of any level from your system using:
rpm -e <package name>

3. Remove the /opt/mqm directory by typing:
rm -rf /opt/mqm

4. Install WebSphere MQ Version 6.0 using the instructions provided in WebSphere MQ for Linux V6.0 Quick Beginnings.


Installing the WebSphere MQ for Linux client without SSL

This information was not available in time for the WebSphere MQ for Linux V6.0 Quick Beginnings before it was sent to translation.

To install the Linux clients without SSL code, do NOT include the following packages in the install commands:

Linux (x86 platform)
gsk7bas-7.0-3.15.i386.rpm
MQSeriesKeyMan-6.0.0-0.i386.rpm

Linux (zSeries platform)
gsk7bas-7.0-3.15.s390.rpm
MQSeriesKeyMan-6.0.0-0.s390.rpm

Linux (POWER platform)
gsk7bas64-7.0-3.15.ppc64.rpm
gsk7bas-7.0-3.15.ppc32.rpm
MQSeriesKeyMan-6.0.0-0.ppc64.rpm


Prerequisite software for GSKit, JRE and SDKs on WebSphere MQ for Linux, V6.0 (zSeries platform):

The zSeries 31-bit 1.4.2 Java(TM) JRE and SDKs supplied with WebSphere MQ V6.0, depend on shared libraries that are not installed by default for Red Hat Enterprise Linux (RHEL) 3.0.

The RPM that contains these libraries is:
compat-libstdc++-7.2-2.95.3

If you intend to use the IBM Global Security Kit V7 or the supplied V1.4.2 Java SDK with WebSphere MQ for Linux, V6.0 (zSeries platform) on Red Hat Enterprise Linux (RHEL) 3.0,
you must ensure you install the above package.


WebSphere MQ Explorer for V6.0 - error connecting to a migrated queue manager


If you cannot connect to a migrated queue manager and see an error like "SYSTEM.MQEXPLORER.REPLY.MODEL not defined", run:

strmqm -c

on that queue manager.

This command refreshes the default system objects, including creating the queue required by WebSphere MQ Explorer.


Starting the WebSphere MQ Explorer on Linux

The command to start the WebSphere MQ Explorer on Linux is " strmqcfg", which is described in chapter 17 "The control commands" of the WebSphere System Administration Guide. Use this command to ensure the WebSphere MQ Explorer launches correctly.

WebSphere MQ Quick Tour

If you have opened the WebSphere MQ Quick Tour from the Getting Started section of the Information Center, the text might occasionally not display when you select a language. If this happens, click on the navigation buttons at the bottom right corner of the Quick Tour window, and the text will then display.

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

Getting started on WebSphere MQ for Solaris


GC34 - 6477 - WebSphere MQ for Solaris Quick Beginnings

The information between <start changed text> and <end changed text> was updated after the following book was sent to translation.

The information between <start new text> and <end new text> is new and was written after the following book was sent to translation.

Chapter 2 "Installing a WebSphere MQ server"

Section: "Preparing for installation"
"Checking prerequisite hardware and software"
"Checking the operating environment"
"Operating System"

The operating systems supported by WebSphere MQ for Solaris, Version 6.0 are:

Sun Solaris 8 (64 bit) with SunSolve recommended Patch Cluster level

Install the following patches or equivalent superseding levels before you install WebSphere MQ Version 6.0.
108827-12
111177-06
112396-02
108987-12 (requires 112396-02)
110910-01
109147-21
108434-10
<start changed text>
108435-14
108987-12
108528-29 (requires 108987-12)
<end changed text>
In addition to use SSL, install the following patches:
<start changed text>
111327-05
108991
108993-31
113648-03
116602-01
111317-05
111023-03
115827-01
<end changed text>

Sun Solaris 9 (64 bit) with SunSolve recommended Patch Cluster level
<start new text>
In addition to use SSL, install the following patches:
111711-08
111712-08
<end new text>


Chapter 3 "Installing a WebSphere MQ Client"

Section: "Preparing to install"
"Checking hardware and software requirements"
"Checking the operating environment"
"Operating System"

The operating systems supported by WebSphere MQ for Sun Solaris, Version 6.0 are:

Sun Solaris 8 (64 bit) with SunSolve recommended Patch Cluster level

Install the following patches or equivalent superseding levels
before you install WebSphere MQ Version 6.0.
108827-12
111177-06
112396-02
108987-12 (requires 112396-02)
110910-01
109147-21
108434-10
<start changed text>
108435-14
108987-12
108528-29 (requires 108987-12)
<end changed text>
In addition to use SSL, install the following patches:
<start changed text>
111327-05
108991
108993-31
113648-03
116602-01
111317-05
111023-03
115827-01
<end changed text>

Sun Solaris 9 (64 bit) with SunSolve recommended Patch Cluster level
<start new text>
In addition to use SSL, install the following patches:
111711-08
111712-08
<end new text>

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

Getting started on WebSphere MQ for Windows


Install fails on Windows 2000 from a mapped network drive using Terminal Services


You might experience an install failure if you try to install WebSphere MQ V6.0 on Windows 2000 from a mapped network drive using Terminal Services. This problem is caused by a
Microsoft® bug: the Microsoft Knowledge Base article is Q255582. As a result, there is no IBM fix for this problem. You must use the workaround suggested in the Microsoft Knowledge Base.

A direct link to the article is:
http://support.microsoft.com/kb/255582/en-us


Starting the WebSphere MQ Explorer on Windows

The command to start the WebSphere MQ Explorer on Windows is " strmqcfg", which is described in chapter 17 "The control commands" of the WebSphere System Administration Guide.

On Windows, the WebSphere MQ Explorer can also be started from the "IBM WebSphere MQ" Start menu.

Use either of these methods command to ensure the WebSphere MQ Explorer launches correctly.



Problems with Windows XP and Windows 2003 in a COM+ environment

There are three related problems introduced with Windows XP and Windows 2003 when used in a COM+ environment.

  • MQRC_UOW_ENLISTMENT_ERROR (2354) on Windows 2003 Server

This problem occurs on Windows 2003 only.

XA transactions are disabled by default. WebSphere MQ uses the Microsoft Distributed Transaction Coordinator using the XA mechanism. You need to enable XA transactions
to participate in transactions.

Problem: If you are using a transactional .NET component, you might see errors when you issue a Get method on an MQQueue object to get a message within a COM+ transaction.

You will not see any additional information associated with the failure and the Microsoft Distributed Transaction Coordinator (MSDTC) in the event viewer.

Solution: To enable XA transactions, change a setting in Component Services for the machine experiencing the failure:
Component Services -> "Computer Name" -> Right click ->
Properties -> MSDTC tab and check the 'XA Transactions'
check box

If XA Transactions are already enabled, check if you have an XADLL tag (see the following problem for more details).


  • MQRC_UOW_ENLISTMENT_ERROR (2354) on Windows 2003

This problem occurs on Windows 2003 only.

In order to participate in an XA transaction, your XA DLL needs to be registered to the system. WebSphere MQ will try to do this during install.

Problem: You have XA transactions enabled, but you still see a 2354 reason code when you try to get or put a message in a COM+ transaction or using a .NET application that inherits from ServicedComponent.

On Windows XP, if the transaction does time out, the next WebSphere MQ call returns reason code 2354 (MQRD_UOW_ENLISTMENT_ERROR) as expected and documented.

On Windows 2003, however, on the FIRST instance of MQPUT, WebSphere MQ returns reason code 2354 (MQRD_UOW_ENLISTMENT_ERROR).

Solution: Add the WebSphere MQ XA resource manager DLL to the list of DLLs in the XADLL key of the registry:
HKLM\SOFTWARE\Microsoft\MSDTC\XADLL

The DLL name is amqmtsxatm.dll. It has a value type of REG_SZ. The value of the installed location of the DLL is <mqmtop>\bin\amqmtsxatm.dll.

  • MQRC_UOW_ENLISTMENT_ERROR (2354) on Windows 2003

This problem occurs on Windows 2003 and Windows XP only.

If the COM+ transaction also contains resources that are remote, you might need to authorize Microsoft Distributed Transaction Coordinator to talk on the network.

Problem: Symptoms include reason code MQRC_UOW_ENLISTMENT_ERROR (2354) or reason code 2195 with 0XC0C11007 logged in BizTalk event log message 264.

You require additional definitions to enable COM+ (Microsoft Transaction Server) transactions with the MSDTC coordinating with other machines.

Solution: You need to follow the solution instructions for the two problems described above. That is, enable XA transactions, and register a resource manager DLL.

After you have completed these two tasks, you might still experience problems. These are 2195 reason codes and MQRC_UOW_ENLISTMENT_ERROR (2354) reason codes if the DTC needs to be involved in a transaction that requires access to the network. If this is the case, you also need to enable MSDTC network access

Go to the Component Services GUI (in Administrative Tools), and go to My Computer and right click -> Properties -> MSDTC. Click the "Security Configuration" button, and enable the ability
for the MSDTC to talk on the network.


WebSphere MQ Quick Tour

If you have opened the WebSphere MQ Quick Tour from the Getting Started section of the Information Center, the text might occasionally not display when you select a language. If this happens, click on the navigation buttons at the bottom right corner of the Quick Tour window, and the text will then display.


National language help panels for the Prepare Wizard

The US English Prepare Wizard help text panels were updated with important changes, which were included in the "WebSphere MQ Migration Information: some issues affecting migration to WebSphere MQ Version 6.0" manual shortly before it was translated. At WebSphere MQ V6.0, the national-language versions of these help text panels will be shipped without these changes. The up-to-date translations of these panels should be shipped as soon as possible.


WebSphere MQ Explorer for V6.0 - error connecting to a migrated queue manager

If you cannot connect to a migrated queue manager and see an error like "SYSTEM.MQEXPLORER.REPLY.MODEL not defined", run:

strmqm -c

on that queue manager.

This command refreshes the default system objects, including creating the queue required by WebSphere MQ Explorer.


Uninstalling IBM WebSphere Eclipse Platform on Windows

After you uninstall IBM WebSphere Eclipse Platform, you must delete additional files created during installation of WebSphere Eclipse Platform from the "Eclipse SDK30" install directory.
This ensures you can install a newer version of WebSphere Eclipse Platform correctly at a later date.

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


UPDATES, LIMITATIONS, AND KNOWN PROBLEMS

This section details updates, limitations, and known problems for WebSphere MQ V6.0


UPDATES, LIMITATIONS, AND KNOWN PROBLEMS THAT APPLY TO ALL DISTRIBUTED PLATFORMS

The following restrictions apply to all distributed platforms:

REFRESH SECURITY TYPE(SSL) command

When you issue the REFRESH SECURITY TYPE(SSL) MQSC command (or its PCF equivalent), all running SSL channels are stopped and restarted. Sometimes SSL channels can take a long time to shut down and this means that the refresh operation takes some time to complete.

There is a time limit of 10 minutes for an SSL refresh to complete, so it can potentially take 10 minutes for the command to finish. This can give the appearance that the refresh operation has "frozen". (On z/OS®, the refresh timeout is 1 minute.)

The refresh operation will fail with an MQSC error message of AMQ9710 or PCF error MQRCCF_COMMAND_FAILED if the timeout is exceeded before all channels have stopped.

This is likely to happen if:

(a) The queue manager has many SSL channels running simultaneously when the refresh command is invoked, or

(b) The channels are handling large numbers of messages.

If a refresh fails under these conditions, you are recommended to retry the command later when the queue manager is less busy.

In the case where many channels are running, you can choose to stop some of the channels manually before invoking the REFRESH command.

UPDATES, LIMITATIONS, AND KNOWN PROBLEMS THAT APPLY TO THE AIX PLATFORM ONLY

The following restriction applies to the AIX platform only:

SOAP
If you are using generated queue names during deployment and a URL is specified, destination must be the first parameter in the URL after the initial 'jms:/queue' string.



UPDATES, LIMITATIONS, AND KNOWN PROBLEMS THAT APPLY TO THE HP-UX PLATFORM ONLY

The following restrictions apply to the HP-UX platform only:

JAVA_HOME environment variable on HP-UX
On HP-UX, you must set the JAVA_HOME environment variable to:
export JAVA_HOME=/opt/mqm/ssl/jre


HP-UX 32-bit WMQ clients: SSL not FIPS-certified
Note if you are using SSL on 32-bit WebSphere MQ clients on HP-UX 11i V1, the cryptography included in the 32-bit GSKit, which is used to provide the SSL support for such clients, is not
FIPS-certified. If you attempt to start an SSL channel in this environment with the MQSSLFIPS environment variable set to YES or, on an MQCONNX call with the FipsRequired value in the MQSCO set to MQSSL_FIPS_YES, the attempt will fail with error message AMQ9620.

SOAP
If you are using generated queue names during deployment and a URL is specified, destination must be the first parameter in the URL after the initial 'jms:/queue' string.


UPDATES, LIMITATIONS, AND KNOWN PROBLEMS THAT APPLY TO THE ISERIES PLATFORM ONLY

The following restrictions apply to the iSeries platform only:

Ensure you have applied the latest cumulative i5/OS fix packs so that WebSphere MQ operates correctly.

PTFs required for RCVJRNE exit that fails intermittently
The problem where an RCVJRNE exit fails intermittently is described in APAR MA30012. The PTFs for this problem are available for V5R2M0 and V5R3M0 (5722SS1):

R520 MF34442
R530 MF34310



UPDATES, LIMITATIONS, AND KNOWN PROBLEMS THAT APPLY TO JMS ONLY

The following restrictions apply to JMS only:

Limitation on iSeries bindings transport with messages greater than 16 MB.
For details of this restriction, see:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzamp/rzampother.htm

XA transactions using DB2 8.2
If you close a JDBC XAConnection while a transaction is in flight, it results in the JDBC drivers attempting to commit and failing. You are recommended to avoid closing the connection before disconnecting from the queue manager. This applies to DB2 JDBC type-2 drivers only.


SSLKeyReset is not working in conjunction with FIPS compliance assurance using IBM JDK 1.4.2
SSLKeyReset does not work with Sun JDKs; client authentication does not work when using a FIPS-compliant cipher suite.


FIPS compliance support and SOAP function
There is no FIPS compliance support or SOAP function on 64-bit HP-UX and Solaris because the 64-bit IBM JDKs are not shipped on these platforms yet.


JDBC/XA switch libraries dependencies
THE JDBC/XA switch libraries no longer have a dependancy on the JVM. Therefore, the restrictions relating to the use of the JDBC/XA with levels of Java are no longer valid.

Also, the instructions relating to the setting of the JAVA_HOME variable when building the switch library are no longer valid. This is applicable to all platforms.

There is a dependancy on the installed WebSphere MQ libraries. The makefiles used to build the switch libraries are coded to use the standard location of the WebSphere MQ libraries.
You must ensure the WebSphere MQ libraries are correctly installed.

Running the JMS postcard in a Linux environment
If you have an entry in your /etc/hosts file that maps the hostname to the loopback device (127.0.0.1) on the receiver machine when you run the JMS postcard in a Linux environment, the default JMS Postcard configuration will fail whenever communication is attempted between two different machines.


UPDATES, LIMITATIONS, AND KNOWN PROBLEMS THAT APPLY TO THE LINUX PLATFORM ONLY

The following restriction applies to the Linux platform only.

SOAP
If you are using generated queue names during deployment and a URL is specified, destination must be the first parameter in the URL after the initial 'jms:/queue' string.



UPDATES, LIMITATIONS, AND KNOWN PROBLEMS THAT APPLY TO THE SOLARIS PLATFORM ONLY

The following restriction applies to the Solaris platform only.

SOAP
If you are using generated queue names during deployment and a URL is specified, destination must be the first parameter in the URL after the initial 'jms:/queue' string.



UPDATES, LIMITATIONS, AND KNOWN PROBLEMS THAT APPLY TO THE WINDOWS PLATFORM ONLY

The following restrictions apply to the Windows platform only.

SSL secret key reset
SSL secret key reset cannot be used on an SSL channel involving a WebSphere MQ V5.3 or WebSphere MQ V5.3.1 Windows queue manager, or a WebSphere MQ V5.3 or WebSphere MQ V5.3.1 Windows client.


Configuring additional authority for Windows applications connecting to WebSphere MQ

You might experience problems if you have Windows applications, for example ASP pages, connecting to WebSphere MQ that are configured to run at a security level higher than usual.

WebSphere MQ requires SYNCHRONIZE access to application processes in order to coordinate certain actions. APAR IC35116 changed WebSphere MQ so that the appropriate privileges are specified. However, the account under which WebSphere MQ processes run might need additional authorization before the requested access can be granted. Directions for configuring additional authority are given below.

To configure additional authority to the user ID under which WebSphere MQ processes are running:
  • Bring up the Local Security Policy tool, click on Security Settings ->Local Policies->User Right Assignments, click on "Debug Programs".
  • Double click "Debug Programs", then Add your WebSphere MQ user ID to the list.
If the system is in a Windows domain and the effective policy setting is still not set, even though the local policy setting is set, the user ID must be authorized in the same way at domain level,
using the Domain Security Policy tool.

SOAP
If you are using generated queue names during deployment and a URL is specified, destination must be the first parameter in the URL after the initial 'jms:/queue' string.



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

DOCUMENTATION UPDATES

  • GC34 - 6479 - WebSphere MQ for HP-UX Quick Beginnings

Chapter 2 "Installing a WebSphere MQ server"

Section: "Preparing for installation"
"Checking prerequisite hardware and software"
"Checking the operating environment"
"Operating System"

The information between <added text> and <end added text> is new and was written after the book was sent to translation.

The operating system supported by WebSphere MQ for HP-UX, Version 6.0 is:

HP-UX 11i v1 (11.11) 64 bit plus Dec. 2003 Quality Pack

<added text>
To use SSL applications with HP-UX 11i v1, install the following patches or equivalent:
superseding levels before you install WebSphere MQ Version 6.0.
PHSS_26946
PHCO_29960
PHCO_27434
PHKL_28489
PHSS_28871
<end added text>

HP-UX 11i v2 (11.23) 64 bit


Chapter 3 "Installing a WebSphere MQ Client"

Section: "Preparing to install"
"Checking hardware and software requirements"
"Checking the operating environment"
"Operating System"

The information between <added text> and <end added text> is new and was written after the book was sent to translation.

The operating system supported by WebSphere MQ for HP-UX, Version 6.0 is:

HP-UX 11i v1 (11.11) 64 bit plus Dec. 2003
QPK

<added text>
To use SSL applications with HP-UX 11i v1, install the following patches or equivalent
superseding levels before you install WebSphere MQ Version 6.0.
PHSS_26946
PHCO_29960
PHCO_27434
PHKL_28489
PHSS_28871
<end added text>

HP-UX 11i v2 (11.23) 64 bit

  • GC34 - 6477 - WebSphere MQ for Solaris Quick Beginnings

The information between <start changed text> and <end changed text> was updated after the following book was sent to translation.

The information between <start new text> and <end new text> is new and was written after the following book was sent to translation.

Chapter 2 "Installing a WebSphere MQ server"

Section: "Preparing for installation"
"Checking prerequisite hardware and software"
"Checking the operating environment"
"Operating System"


The operating systems supported by WebSphere MQ for Solaris, Version 6.0 are:

Sun Solaris 8 (64 bit) with SunSolve recommended Patch Cluster level

Install the following patches or equivalent superseding levels before you install WebSphere MQ Version 6.0.
108827-12
111177-06
112396-02
108987-12 (requires 112396-02)
110910-01
109147-21
108434-10
<start changed text>
108435-14
108987-12
108528-29 (requires 108987-12)
<end changed text>
In addition to use SSL, install the following patches:
<start changed text>
111327-05
108991
108993-31
113648-03
116602-01
111317-05
111023-03
115827-01
<end changed text>

Sun Solaris 9 (64 bit) with SunSolve recommended Patch Cluster level
<start new text>
In addition to use SSL, install the following patches:
111711-08
111712-08
<end new text>


Chapter 3 "Installing a WebSphere MQ Client"

Section: "Preparing to install"
"Checking hardware and software requirements"
"Checking the operating environment"
"Operating System"

The operating systems supported by WebSphere MQ for Sun Solaris, Version 6.0 are:

Sun Solaris 8 (64 bit) with SunSolve recommended Patch Cluster level

Install the following patches or equivalent superseding levels before you install WebSphere MQ Version 6.0.
108827-12
111177-06
112396-02
108987-12 (requires 112396-02)
110910-01
109147-21
108434-10
<start changed text>
108435-14
108987-12
108528-29 (requires 108987-12)
<end changed text>
In addition to use SSL, install the following patches:
<start changed text>
111327-05
108991
108993-31
113648-03
116602-01
111317-05
111023-03
115827-01
<end changed text>

Sun Solaris 9 (64 bit) with SunSolve recommended Patch Cluster level
<start new text>
In addition to use SSL, install the following patches:
111711-08
111712-08
<end new text>

  • SC34 - 6604 - WebSphere MQ Migration Information: some issues affecting migration to WebSphere MQ Version 6.0

Chapter "Migrating Windows Secure Sockets Layer (SSL) connections"

Section "Points to consider" - new bullet point.

The following words are new and were written after the book was sent to translation:

The chain checker application used to verify all the required certificates are there before migrating certificates from the WebSphere MQ for Windows V5.3 store to the GSKit store will be available in WebSphere MQ V5.3 Fix Pack 10 (CSD10).

  • SC34 - 6584 - WebSphere MQ System Administration Guide

Chapter 4 "Administering local WebSphere MQ objects"

Section: "Working with services"
"Additional environment variables"

Replace the existing words in the entire section with the following words:

"When a service is started, the environment in which the service process is started is inherited from the environment of the queue manager. It is possible to define additional environment
variables to be set in the environment of the service process by adding the variables you wish to define to one of the environment override files, service.env

There are two possible files to which you can add environment variables:
  • The machine scope service.env file is located in the WebSphere MQ data directory, this is '/var/mqm' on the UNIX® platforms and the data directory as defined during the WebSphere MQ installation.
  • The queue manager scope service.env file is located in the queue manager data directory.

For example on UNIX, the location of the file for a queue manager called QMNAME is:
/var/mqm/qmgrs/QMNAME/service.env

On Windows for a similarly named queue manager the file is:
C:\Program Files\IBM\Websphere MQ\qmgrs\QMNAME\service.env

Both files are processed if available, with definitions in the queue manager file taking precedence over those if the machine scope service.env file."


Chapter 4 "Administering local WebSphere MQ objects"

Section: "Replaceable inserts on service definitions"
"Common tokens"

The following new common tokens should be added to this section:
  • MQ_DATA_PATH - The WebSphere MQ data directory
  • MQ_SERVICE_NAME - The SERVICE name
  • MQ_SERVER_PID - The pid of the active SERVICE (SERVTYPE=SERVER only)
  • MQ_Q_MGR_DATA_PATH - The queue manager data directory
  • MQ_Q_MGR_DATA_NAME - The name of the queue manager



Chapter 7 "Administration using the WebSphere MQ Explorer"

Section: "Using the WebSphere MQ Explorer"

New section "Starting WebSphere MQ Explorer in Rich Client Platform (RCP) mode "
(should appear after the section "Using the WebSphere MQ Taskbar application (Windows only)

"By default, WebSphere MQ Explorer starts up the first time in Rich Client platform (RCP) mode, so all you see is related to configuring WebSphere MQ.

If you are an experienced user, who is familiar with Eclipse you might want to see WebSphere MQ Explorer and use the other perspectives available in Eclipse, including the Eclipse workbench toolbar and menu options. You can switch from RCP startup mode by going to the WebSphere MQ Explorer preferences page and selecting the appropriate radio button under "Startup"."


Chapter 9 "Configuring WebSphere MQ"

Section: "Changing configuration information on UNIX systems"
"Editing configuration files"

This is new additional information for this section that was not ready in time for translation of the WebSphere MQ System Administration Guide:

"Comments can be included in configuration files by specifying a ; or # character followed by the text you wish to include as a comment. If you need to include a ; or # character in a configuration file and do not want it to represent the start of a comment, you should prefix the ; or # with a \ to have the ; or # used as part of the configuration data."


Chapter 17 "The control commands"

Section "amqmdain (WebSphere MQ Services control)"

The refresh option was not documented in time for translation.

"The refresh option of the amqmdain command is used to refresh or check the status of a queue manager

You can issue the command from the command line as follows:
amqmdain refresh

However, currently the refresh option does not do anything explicitly: the functionality is implemented during initialization. You will not see anything returned on the screen after issuing
this command."


Appendix C "Directory structure (UNIX systems)"

Section: "Figure 36 - Default directory structure (UNIX systems) after a queue manager has been started"

A new entry in the figure below qmstatus.ini:

"service.env"

Appendix "WebSphere MQ and UNIX process priority"


This is a completely new appendix for the WebSphere MQ System Administration Guide:

"It is important that all WebSphere MQ processes and applications utilizing WebSphere MQ are run with the same UNIX nice value. If you run a process in the background, that process can be given a higher nice value (and hence lower priority) by the invoking shell. This might have general WebSphere MQ performance implications. In highly-stressed situations, if there are many ready-to-run threads at a higher priority and some at a lower priority, operating system scheduling characteristics can deprive the lower priority threads of CPU time.

If a process utilizing WebSphere MQ needs to be run in the background, it should be done in a way that preserves the foreground nice value. Ensure the shell does not assign a higher
nice value to background processes. For example, in ksh, use the setting "set +o bgnice" to stop ksh from raising the nice value of backgrounded processes. You can verify the nice values of running processes by examining the NI column of a "ps -efl" listing."
  • SC34 - 6588 - WebSphere MQ Security

Chapter 13 "Working with the Secure Sockets Layer (SSL) on UNIX and Windows systems"

Section "Migrating SSL security certificates in WebSphere MQ for Windows" - addition to the first paragraph.

The following words are new and were written after the book was sent to translation:

The chain checker application used to verify all the required certificates are there before migrating certificates from the WebSphere MQ for Windows V5.3 store to the GSKit store will be available in WebSphere MQ V5.3 Fix Pack 10 (CSD10).


Appendix A "Cryptographic hardware"

Section "Notes"

The version that was sent to translation read as follows:

"nCipher nFast
Interface: BHAPI plug-in under BSAFE 4.0
Platforms:
  • Windows
  • Solaris 2.8

Rainbow Swift
Interface: BSAFE 3.0
Platforms:
  • Windows

IBM 4758-002
Interface: PKCS #11
Platforms:
  • i5/OS

IBM 4758-023
Interface: PKCS #11
Platforms:
  • Windows
  • AIX

IBM 4960
Interface: PKCS #11
Platforms:
  • Linux (zSeries)

IBM PCICA
Interface: PKCS #11
Platforms:
  • Linux (x86)
  • Linux (zSeries)

nCipher nForce
Interface: PKCS #11
Platforms:
  • Windows
  • AIX
  • HP11i
  • Linux
  • Solaris
If SSL cryptographic hardware symmetric cipher operations are enabled within WebSphere MQ, the cryptography used on an SSL channel will be provided by nCipher. This card is currently supported for symmetric cipher operations using Triple DES encryption.

Eracom Orange
Interface: PKCS #11
Platforms:
  • Windows
If SSL cryptographic hardware symmetric cipher operations are enabled within WebSphere MQ, the cryptography used on an SSL channel will be provided by Eracom Orange. This card is currently supported for symmetric cipher operations using Triple DES encryption.

IBM e-business Cryptographic Accelerator (#4960)
Interface: PKCS #11
Platforms:
  • Linux (x86)
  • Linux (zSeries)"

This entire section should be replaced by the following:

"nCipher nFast 200
Interface: BHAPI plug-in under BSAFE 4.0
Platforms:
  • Solaris 8

IBM 4758-002
Interface: PKCS #11
Platforms:
  • i5/OS - OS/400 V5R3

IBM 4758-023
Interface: PKCS #11
Platforms:
  • Windows - Windows 2000 Pro SP4
  • AIX - R5V2 64bit

IBM e-business Cryptographic Accelerator (#4960)
Interface: PKCS #11
Platforms:
  • Linux (x86)
  • Linux (zSeries)

IBM PCICA
Interface: PKCS #11
Platforms:
  • Linux (zSeries)

nCipher nForce 300
Interface: PKCS #11
Platforms:
  • Windows 2000 Pro SP4
  • AIX R5V2 64bit
  • HP11i
  • Linux - RedHat 3 Advanced Server
  • Solaris 8
If SSL cryptographic hardware symmetric cipher operations are enabled within WebSphere MQ, the cryptography used on an SSL channel will be provided by nCipher. This card is currently supported for symmetric cipher operations using Triple DES encryption.

Eracom Orange
Interface: PKCS #11
Platforms:
  • Windows 2000
If SSL cryptographic hardware symmetric cipher operations are enabled within WebSphere MQ, the cryptography used on an SSL channel will be provided by Eracom Orange. This card is currently supported for symmetric cipher operations using Triple DES encryption."

  • SC34 - 6597 - WebSphere MQ Script (MQSC) Command Reference

Chapter 2 "The MQSC commands"

Section "REFRESH SECURITY" command "Usage note 4"

The existing paragraph:
"Sender, server and cluster-sender channels using SSL are allowed to complete the current batch. Then they run the SSL handshake again with the refreshed view of the SSL key
repository."

should be replaced with:
"Sender, server and cluster-sender channels using SSL are allowed to complete the current batch. In general they run the SSL handshake again with the refreshed view of the SSL key repository. However, the user must manually restart a requester-server channel on which the server definition has no CONNAME parameter."

  • SC34 - 6598 - WebSphere Programmable Command Formats and Administration Interface

Chapter 3 "Definitions of PCFs"

Section "Refresh Security"
"SecurityType (MQCFIN)"
"MQSECTYPE_SSL"

The existing paragraph:
"Sender, server and cluster-sender channels using SSL are allowed to complete the current batch. Then they run the SSL handshake again with the refreshed view of the SSL key
repository."

should be replaced with:
"Sender, server and cluster-sender channels using SSL are allowed to complete the current batch. In general they run the SSL handshake again with the refreshed view of the SSL key repository. However, the user must manually restart a requester-server channel on which the server definition has no CONNAME parameter."

  • GC34 - 6601 - WebSphere MQ Messages

Chapter 8 "API compilation and reason codes"

Section: "Completion and reason codes"

The following reason code is missing from this section:

"MQRC_PARTICIPANT_NOT_DEFINED (2372, X'0944')
Participating resource manager not defined.

Explanation: An MQQueueManager.begin() call was issued to start a unit of work coordinated by the queue manager, but one or more of the resource managers that had been registered by the application using the getJDBCConnection() call had not been defined to the queue manager.

This reason code can also occur on the getJDBCConnection() call if the application attempts to register a undefined resource manager after the start of the unit of work.

This reason code occurs in the following environments:
AIX, HP-UX, OS/2®, AS/400®, Sun Solaris, Windows NT.

Completion code: MQCC_FAILED

Programmer Response: Modify the application to register only resource managers that have been defined to the queue manager. Alternatively, request the system support programmer
to define the needed resource managers in the queue manager's configuration file by adding definitions for the relevant switch libraries."

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

CONTACTING IBM SOFTWARE SUPPORT


IBM Software Support provides assistance with product defects. Before you submit your problem to IBM Software Support, ensure that your company has an active IBM software
maintenance contract, and that you are authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:

For IBM distributed software products (including, but not limited to, Tivoli, Lotus, and Rational products, as well as DB2 and WebSphere products that run on Windows or UNIX operating systems), enroll in Passport Advantage in one of the following ways:

If you have a Subscription and Support (S & S) contract, go to the Software Service Request Web site at:
http://www.ibm.com/support/servicerequest

If you have IBMLink, CATIA, Linux, S/390, iSeries, pSeries, zSeries, or another support agreement, go to the IBM Support Line Web site at:
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.

For IBM eServer software products (including, but not limited to, DB2 and WebSphere products that run in zSeries, pSeries, and iSeries environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eServer software products, go to the IBM Technical Support Advantage Web site at:
http://www.ibm.com/servers/eserver/techsupport.html

If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to the "Contacts" page of the IBM Software Support Handbook at:
http://techsupport.services.ibm.com/guides/contacts.html
and click the name of your geographic region for phone numbers of people who provide support for your location.

To contact IBM Software support, follow these steps:
  • Determine the business impact of your problem.
  • Describe your problem and gather background information.
  • Submit your problem to IBM Software Support.

Determine the business impact of your problem

When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem that you are reporting.
Use the following criteria:
    Severity 1
    The problem has a critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution.

    Severity 2
    This problem has a significant business impact: The program is usable, but it is severely limited.

    Severity 3
    The problem has some business impact: The program is usable, but less significant features (not critical to operations) are unavailable.

    Severity 4
    The problem has minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem was implemented.

Describe your problem and gather background information

When describing a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions:
  • What software versions were you running when the problem occurred?
  • Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information.
  • Can you re-create the problem? If so, what steps do you perform to re-create the problem?
  • Did you make any changes to the system? For example, did you make changes to the hardware, operating system, networking software, or other system components?
  • Are you currently using a workaround for the problem? If so, please be prepared to describe the workaround when you report the problem.

Submit your problem

You can submit your problem to IBM Software Support in one of two ways:

If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution.

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

TRADEMARKS

The following terms are trademarks of International Business
Machines Corporation in the United States, other countries,
or both:
AIX, AS/400, CICS, IBM, i5/OS, iSeries, OS/2, OS/400, SupportPac, WebSphere, z/OS, z/Series

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

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

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

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

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

Product Alias/Synonym

WebSphere MQ WMQ MQSeries

Document information

More support for: WebSphere MQ
Documentation

Software version: 6.0

Operating system(s): AIX, HP-UX, IBM i, Linux, Solaris, Windows

Reference #: 7006838

Modified date: 03 November 2005


Translate this page: