IBM Support

Product readme for V6.0.1.0

Product Readmes


Abstract

This document contains the WebSphere MQ readme for product version 6.0.1.0 and applies to products shipped at version 6.0.0.0 which have refresh pack 6.0.1.0 installed as well as those shipped at version 6.0.1.0.

Content

Note that latest changes are shown in italic . The Change History is located at the bottom of the page and shows links to changes since the release of the release notes with version 6.0.1.0.

WebSphere MQ Version 6.0.1 Release Notes

1.0 IBM WebSphere MQ, Version 6.0.1 Release Notes

Welcome to the IBM WebSphere MQ V6.0.1 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.

1.1 Contents

  • 1.2, "Description"
    • 1.2.1, "Web documentation updates"
  • 1.3, "About this release"
    • 1.3.1, "Update history"
  • 1.4, "Getting started"
    • 1.4.1, "Getting started on all WebSphere MQ distributed platforms"
    • 1.4.2, "Getting started on WebSphere MQ for AIX"
    • 1.4.3, "Getting started on WebSphere MQ for HP-UX"
    • 1.4.4, "Getting started on WebSphere MQ for iSeries"
    • 1.4.5, "Getting started on WebSphere MQ for Linux"
    • 1.4.6, "Getting started on WebSphere MQ for Windows"
  • 1.5, "Updates, limitations, and known problems"
    • 1.5.1, "Updates, limitations, and known problems that apply to all distributed platforms"
    • 1.5.2, "Updates, limitations, and known problems that apply to the AIX platform only"
    • 1.5.3, "Updates, limitations, and known problems that apply to the HP-UX platform only"
    • 1.5.4, "Updates, limitations, and known problems that apply to the iSeries platform only"
    • 1.5.5, "Updates, limitations, and known problems that apply to JMS only"
    • 1.5.6, "Updates, limitations, and known problems that apply to the Linux platform only"
    • 1.5.7, "Updates, limitations, and known problems that apply to the Solaris platform only"
    • 1.5.8, "Updates, limitations, and known problems that apply to the Windows platform only"
  • 1.6, "Documentation updates"
    • 1.6.1, "GC34-6476 - WebSphere MQ for Windows Quick Beginnings"
    • 1.6.2, "GC34-6477 - WebSphere MQ for Solaris Quick Beginnings"
    • 1.6.3, "GC34-6479 - WebSphere MQ for HP-UX Quick Beginnings"
    • 1.6.4, "GC34-6480 - WebSphere MQ for Linux Quick Beginnings
    • 1.6.5, "SC34-6584 - WebSphere MQ System Administration Guide"
    • 1.6.6, "SC34-6590 - WebSphere MQ Clients"
    • 1.6.7, "SC34-6597 - WebSphere MQ Script (MQSC) Command Reference"
    • 1.6.8, "SC34-6598 - WebSphere Programmable Command Formats and Administration Interface"
    • 1.6.9, "SC34-6595 - WebSphere MQ Application Programming Guide"
    • 1.6.10, "GC34-6601 - WebSphere MQ Messages"
    • 1.6.11, "SC34-6651 - WebSphere MQ Transport for SOAP"
    • 1.6.12, "SC34-6591 - Using Java™"
  • 1.7, "Contacting IBM Software Support"
    • 1.7.1, "Determine the business impact of your problem"
    • 1.7.2, "Describe your problem and gather background information"
    • 1.7.3, "Submit your problem"

1.2 Description

For the latest README additions (including the additions in this file) access the online version of the readme file at:

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


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, 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.ibm.com/support/docview.wss?&uid=swg27007205

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

http://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_MQ

1.2.1 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/

1.3 About this release

WebSphere MQ continues to evolve with this version. Enhancements include:
  • Usability, including the Eclipse-based tooling for remote administration and configuration of the entire MQ network
  • Manageability: easier problem determination and avoidance, and the ability to monitor the MQ network, gather statistics, and raise alerts
  • Integrated Java Message Service (JMS) V1.1 support, including publish and subscribe messaging
  • IBM POWER platform support (Linux for iSeries and Linux for pSeries)
  • Performance, capacity, and scalability
  • IBM Message Service Client for C/C++ (available as SupportPac IA94)
  • Additional new function

WebSphere MQ provides the foundation for an enterprise service bus (ESB).

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

1.3.1 Update history

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

25 May 2005 - Material from readadd file incorporated, with further
additions.

15 Sep 2005 - Second edition. US English version of this file sent to
translation. Some material is now in "Quick Beginnings" books or
WebSphere MQ Migration Information and removed from this document. Some
additions have been made.

31 Oct 2005 - Changes from the 6.0.1.0 version of the readadd file are
incorporated: The text for these additions are changes are shown in italic.

8th November - removed section no longer applicable.

18th November - add 32-64 bit migration warning, more SSL/TLS restrictions and minor
documentation changes.

1.4 Getting started

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

1.4.1 Getting started on all WebSphere MQ distributed platforms

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

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

1.4.1.3 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 AIX
  • Eracom Orange on Windows
  • IBM 4960 on Linux (x86) and Linux (zSeries)
  • PCICA on Linux (zSeries)

Note: The only support WebSphere MQ offers using the interface BHAPI plug-in under BSAFE 4.0 is for the nCipher nFast 300 card on Solaris 2.8.

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

1.4.1.4.1 WebSphere MQ V6.0 SOAP interoperability with CICS

You cannot connect to a CICS SOAP client or a CICS SOAP service using WebSphere MQ V6.0 SOAP functionality. If you attempt to do so, you will receive a RFH2 format error exception.

You must apply CICS APAR PK04615 and WebSphere MQ APAR IC46192 for CICS and WebSphere MQ SOAP to interoperate successfully.

1.4.2 Getting started on WebSphere MQ for AIX

1.4.2.1 Installing the WebSphere MQ for AIX client without SSL

This information was not available in time for 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

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

1.4.3 Getting started on WebSphere MQ for HP-UX

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

1.4.4 Getting started on WebSphere MQ for iSeries

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

If you are running SSL/TLS 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) or later to ensure interoperability.

1.4.4.2 Using QLPACAGR to perform an unattended install of WebSphere MQ for iSeries

You can use QLPACAGR to perform an unattended install of WebSphere MQ on i5/OS V5R3M0 or later and pre-agree to the license terms and conditions that are typically displayed when you issue the RSTLICPGM command.

For further details on how to do this, see:
http://as400bks.rochester.ibm.com/iseries/v5r2/ic2924/info/apis/sw1.pdf
or
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/qlpacagr.htm

1.4.5 Getting started on WebSphere MQ for Linux

1.4.5.1 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

1.4.5.2 Installing the WebSphere MQ for Linux client without SSL

This information was not available in time for 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.18.i386.rpm (32-bit and 64-bit installations)
  • gsk7bas64-7.0-3.18.x86-64.rpm (64-bit only)
  • MQSeriesKeyMan-6.0.1-0.i386.rpm (32-bit only)
  • MQSeriesKeyMan-6.0.1-0.x86-64.rpm (64-bit only)

Linux(zSeries platform)
  • gsk7bas-7.0-3.18.s390.rpm (32-bit and 64-bit installations)
  • gsk7bas64-7.0-3.18.s390x.rpm (64-bit only)
  • MQSeriesKeyMan-6.0.1-0.s390.rpm (32-bit only)
  • MQSeriesKeyMan-6.0.1-0.s390x.rpm (64-bit only)

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

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

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

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

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

Alternatively, you can download a version of the WebSphere MQ Quick Tour that requires less system resource from:
http://www.ibm.com/software/integration/websphere/library/demos/

1.4.5.7 Running the JMS Postcard sample

Because of a defect in the JDK provided with WebSphere MQ, the JMS Postcard sample application is not always able to detect the name of the machine on which it is running. This can result in queue managers created by the Postcard sample's default configuration wizard being named QM_ and the Postcard Sample being unable to send messages between machines. If you experience this behavior, you can resolve it by editing your machine's /etc/hosts file as follows:
  1. Find the loopback address entry; this should start with the IP address 127.0.0.1.
  2. Remove any reference to the name of the machine from the loopback entry. This line should now read:

    127.0.0.1 localhost.localdomain localhost

    Other entries in the /etc/hosts file that reference the name of the machine do not need to be changed.
  3. Save the file and retry the Postcard sample

1.4.6 Getting started on WebSphere MQ for Windows

1.4.6.1 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

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

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

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

Alternatively, you can download a version of the WebSphere MQ Quick Tour that requires less system resource from:
http://www.ibm.com/software/integration/websphere/library/demos/

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

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

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

1.4.6.8 Viewing and installing the WebSphere MQ Information Center on Windows

Documentation for WebSphere MQ Version 6.0 is supplied as an Information Center based on the Eclipse framework. You can install the Information Center on any Windows system supported by the WebSphere MQ V.6.0 product.

You can view or install the Information Center from the WebSphere MQ for Windows Documentation CD.

1.4.6.8.1 Viewing the Information Center

Insert the Documentation CD and click the View button on the View or Install Information Center window. The Information Center will launch after a few moments in a browser window.

1.4.6.8.2 Installing the Information Center
  1. Insert the Documentation CD and click the Install button on the View or Install Information Center window.
  2. Accept the license agreement terms and work through the panels in the WebSphere MQ Information Center V6.0 Setup wizard.
  3. You can select which languages to install from the Features panel. By default, the Information Center for your language is installed. You can also choose to install PDFs from this panel. Left click on the PDFs and any additional languages to view the installation options.

1.4.6.8.3 Stopping the Information Center

Click the Stop button on the View Information Center window.

1.4.6.8.4 Uninstalling the Information Center

Uninstall the Information Center using "Add or Remove Programs".

Select "WebSphere MQ Information Center 6.0" and click the Remove
button.

1.4.6.9 Accessing the PDFs

The documentation is also supplied in PDF format. You can choose to install the PDFs at the same time as you install the Information Center.

After you have installed the PDFs, you can find the files in the directory in which you installed the Information Center: <Information Center install directory>\docs\pdf\<language directory>.

All of the PDFs are supplied in US English and selected PDFs have been translated.

1.4.6.10 Infopops in the WebSphere MQ Explorer

Infopops are provided in the WebSphere MQ Explorer for Windows and Linux. They provide context-sensitive help from any part of the GUI. On Windows, you can:
  • click a folder
  • click a properties page
  • click a view
  • highlight a menu item

then press F1. A small yellow box appears and displays some help information that typically contains one or more links to more detailed information.

1.4.6.11 Viewing the IBM WebSphere Information Center during the installation of WebSphere MQ

If you have installed the WebSphere MQ Information Center and are viewing the documentation while installing the WebSphere MQ product, the Information Center will be automatically restarted when WebSphere MQ has installed. During this restart, the WebSphere MQ Information Center will stop responding for a short period. The Information Center will then reset and return you to the Welcome page. You should navigate to the topic you were viewing reviously and continue using the Information Center as before.

If you are running the WebSphere MQ Information Center from the CD or from a network drive using the "View" option, you might find that the WebSphere MQ server or client product setup.exe fails to start or autostart. In this situation, click the "Stop" button on the "View Information Center" window to close the Information Center and run the WebSphere MQ product setup.exe again.

If you are running the WebSphere MQ Information Center from the CD or from a network drive, using the "View" option and installing the WebSphere MQ product simultaneously, the installation might stop responding at the end of the install process. In this situation, click the "Stop" button on the "View Information Center" window and close the Information Center. The WebSphere MQ product installation will then continue and finish successfully. Restart the Information Center after the WebSphere MQ is successfully installed.

1.4.6.12 GC34-6476 - WebSphere MQ for Windows Quick Beginnings

This information about prerequisite and optional software was not available before the book was sent to translation.

1.4.6.12.1 Chapter 2 "Installing the WebSphere MQ Server"

Section "Preparing for server installation"
"Prerequisite server software"
"Connectivity"

Replace the entire existing section with:
WebSphere MQ requires one of the following for SNA connectivity:
  • IBM Communications Server for Windows, Version 6.1.2
  • IBM Personal Communications, Version 5.7 (part of IBM Host Access Client Package [HACP], Version 4.0)
  • Microsoft Host Integration Server 2004
  • Microsoft Host Integration Server 2000
  • Attachmate myEXTRA! Presentation Services, Version 7.11
  • Attachmate EXTRA! Enterprise 2000
  • Attachmate EXTRA! Personal Client, Version 6.7
  • CP/IP (provided by the operating system; IP, Version 6 feature provided on Windows XP with SP1 or later, and on Windows Server 2003 or later)
  • NetBIOS (provided by the operating system)
  • Sequenced Package Exchange (SPX) (provided by the operating system)"

Section "Preparing for server installation"
"Optional server software"

Replace:
"The following are options, not prerequisites. Minimum supported
levels are shown,

External transaction processing monitors
  • IBM WebSphere Application Server (WAS) V5.1"

with:
"The following are options, not prerequisites. Minimum supported
levels are shown,

External transaction processing monitors
  • IBM WebSphere Application Server V5.1
  • IBM WebSphere Application Server, Version 6.0.1"

Replace:
"Databases
  • Sybase Adaptive Server Enterprise (ASE) 12.5.1"

with:
"Databases
  • Sybase ASE, Version 12.5.3 with ESD, Version 1
  • Sybase SDK, Version 12.5.1 with ESD, Version 7"

1.5 Updates, limitations, and known problems

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

1.5.1 Updates, limitations, and known problems that apply to all distributed platforms

The following restrictions apply to all distributed platforms:

1.5.1.1 REFRESH SECURITY TYPE(SSL) command

When you issue the REFRESH SECURITY TYPE(SSL) MQSC command (or its PCF
equivalent), all running SSL/TLS 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:
  • The queue manager has many SSL/TLS channels running simultaneously when the refresh command is invoked
  • 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.

1.5.1.2 MQCD_DEFAULT structure in applications

When you use the MQCD_DEFAULT structure in applications, the version number must be set explicitly. Any application that does not explicitly set the version number in an MQCD structure might see a difference in behavior if that application is recompiled using V6.0 header files, because the value of the version number in the default structure has changed from version 7 to version 6. The constant MQCD_CURRENT_VERSION contains the most recent version number or you can explicitly set the minimum version required in the application.

1.5.1.3 Using WebSphere Application Server V6.0 with WebSphere MQ V6.0

WebSphere Application Server V6.0 comes with its own versions of com.ibm.mq.jar and com.ibm.mqjms.jar. These are for WebSphere MQ V5.3, but not for WebSphere MQ V6.0.

WebSphere Application Server links to WebSphere MQ libraries using two WebSphere Variables, which are different from system environment variables.

The first WebSphere Variable called MQ_INSTALL_ROOT is:
"${WAS_INSTALL_ROOT}/lib/WMQ"

This maps to: C:\Program Files\IBM\WebSphere\AppServer\lib\wmq\

The second WebSphere Variable called MQJMS_LIB_ROOT is:
${MQ_INSTALL_ROOT}/Java/lib

This maps to: C:\Program Files\IBM\WebSphere\AppServer\lib\wmq\java\lib This is where WebSphere Application Server V6's own jars for WebSphere MQ are stored.

Change MQ_INSTALL_ROOT to the actual install root. For example, by default: C:/Program Files/IBM/Websphere MQ

Save and restart WebSphere Application Server.

1.5.1.4 WebSphere MQ being coordinated by an external syncpoint coordinator

WebSphere MQ can act as an XA Resource Manager (RM), coordinated by an XA Transaction Manager (TM) such as BEA Tuxedo. To support this, it provides a generic library containing the XA switch structure for all TMs called 'mqmxa' for WebSphere MQ server-connected TMs and 'mqcxa' for Extended Transactional Client (ETC)-connected TMs. BEA Tuxedo and some other Transaction Managers do not work with these libraries in 64-bit mode. WebSphere MQ now provides alternative 64-bit libraries which will be required by some TMs when they are 64-bit. These libraries are called 'mqmxa64' for server-connected TMs and 'mqcxa64' for ETC-connected TMs.

1.5.2 Updates, limitations, and known problems that apply to the AIX platform only

The following restriction applies to the AIX platform only:

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

1.5.2.2 Use of IPv6 with 64-bit AIX

The IBM 64-bit Java(TM) SDK for AIX v1.4 uses the IPv6 extensions to the TCP/IP protocol by default.

On AIX v5.2, if your application uses multicast sockets or explicitly uses IPv6 format addresses, you must enable the network interfaces on your machine to handle IPv6 addresses. The network interfaces can be configured for IPv6 with smitty or by using the autoconf6 or ifconfig commands. Alternatively, if you do not want to use IPv6 protocols, you can set the property java.net.preferIPv4Stack to force the use of IPv4 protocols, using the following command:

java -Djava.net.preferIPv4Stack=true <classname>

where <classname> is the name of your .class file.

1.5.3 Updates, limitations, and known problems that apply to the HP-UX platform only

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

1.5.3.1 JAVA_HOME environment variable on HP-UX

On HP-UX, if you want to run SSL key/certificate management tools, you must set the JAVA_HOME environment variable to:

export JAVA_HOME=/opt/mqm/ssl/jre

1.5.3.2 HP-UX 32-bit WMQ clients: SSL not FIPS-certified

Note if you are using SSL/TLS 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/TLS support for such clients, is not FIPS-certified. If you attempt to start an SSL/TLS 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.

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

1.5.3.4 Building applications on IA64 (IPF)

The following section contains examples of the commands used to build
programs in various environments on IA64 (IPF).

C client application, 32-bit, non-threaded

c89 -Wl,+b,: +e -D_HPUX_SOURCE -o amqsputc_32 amqsput0.c -I/opt/mqm/inc
-L/opt/mqm/lib -L/usr/lib/hpux32 -lmqic


C client application, 32-bit, threaded

c89 -Wl,+b,: +e -D_HPUX_SOURCE -o amqsputc_32_r amqsput0.c -I/opt/mqm/inc
-L/opt/mqm/lib -L/usr/lib/hpux32 -lmqic_r -lpthread


C client application, 64-bit, non-threaded

c89 +DD64 +e -Wl,+noenvvar -D_HPUX_SOURCE -o amqsputc_64 amqsput0.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -L/usr/lib/hpux64 -lmqic


C client application, 64-bit, threaded

c89 +DD64 +e -Wl,+noenvvar -D_HPUX_SOURCE -o amqsputc_64_r amqsput0.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -L/usr/lib/hpux64 -lmqic_r -lpthread


C server application, 32-bit, non-threaded

c89 -Wl,+b,: +e -D_HPUX_SOURCE -o amqsput_32 amqsput0.c -I/opt/mqm/inc
-L/opt/mqm/lib -L/usr/lib/hpux32 -lmqm


C server application, 32-bit, threaded

c89 -Wl,+b,: +e -D_HPUX_SOURCE -o amqsput_32_r amqsput0.c -I/opt/mqm/inc
-L/opt/mqm/lib -L/usr/lib/hpux32 -lmqm_r -lpthread


C server application, 64-bit, non-threaded

c89 +DD64 +e -Wl,+noenvvar -D_HPUX_SOURCE -o amqsput_64 amqsput0.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -L/usr/lib/hpux64 -lmqm


C server application, 64-bit, threaded

c89 +DD64 +e -Wl,+noenvvar -D_HPUX_SOURCE -o amqsput_64_r amqsput0.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -L/usr/lib/hpux64 -lmqm_r -lpthread


C++ client application, 32-bit, non-threaded

aCC -Wl,+b,: +e -D_HPUX_SOURCE -o imqsputc_32 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -L/usr/lib/hpux32 -limqi23ah -lmqic


C++ client application, 32-bit, threaded

aCC -Wl,+b,: +e -D_HPUX_SOURCE -o imqsputc_32_r imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -L/usr/lib/hpux32 -limqi23ah_r -lmqic_r -lpthread


C++ client application, 64-bit, non-threaded

aCC +DD64 +e -Wl,+noenvvar -D_HPUX_SOURCE -o imqsputc_64 imqsput.cpp
-I/opt/mqm/inc -L/opt/mqm/lib64 -L/usr/lib/hpux64 -limqi23ah -lmqic


C++ client application, 64-bit, threaded

aCC +DD64 +e -Wl,+noenvvar -D_HPUX_SOURCE -o imqsputc_64_r imqsput.cpp
-I/opt/mqm/inc -L/opt/mqm/lib64 -L/usr/lib/hpux64 -limqi23ah_r -lmqic_r
-lpthread


C++ server application, 32-bit, threaded

aCC -Wl,+b,: +e -D_HPUX_SOURCE -o imqsput_32 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -L/usr/lib/hpux32 -limqi23ah -lmqm


C++ server application, 32-bit, threaded

aCC -Wl,+b,: +e -D_HPUX_SOURCE -o imqsput_32_r imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -L/usr/lib/hpux32 -limqi23ah_r -lmqm_r -lpthread


C++ server application, 64-bit, non-threaded

aCC +DD64 +e -Wl,+noenvvar -D_HPUX_SOURCE -o imqsput_64 imqsput.cpp
-I/opt/mqm/inc -L/opt/mqm/lib64 -L/usr/lib/hpux64 -limqi23ah -lmqm


C++ server application, 64-bit, threaded

aCC +DD64 +e -Wl,+noenvvar -D_HPUX_SOURCE -o imqsput_64_r imqsput.cpp
-I/opt/mqm/inc -L/opt/mqm/lib64 -L/usr/lib/hpux64 -limqi23ah_r -lmqm_r
-lpthread


C client exit, 32-bit, non-threaded

c89 +e +z -c -D_HPUX_SOURCE -o cliexit.o cliexit.c -I/opt/mqm/inc
ld +b: -b cliexit.o +ee MQStart -o /var/mqm/exits/cliexit_32 -L/opt/mqm/lib
-L/usr/lib/hpux32 -lmqic


C client exit, 32-bit, threaded

c89 +e +z -c -D_HPUX_SOURCE -o cliexit.o cliexit.c -I/opt/mqm/inc
ld +b: -b cliexit.o +ee MQStart -o /var/mqm/exits/cliexit_32_r
-L/opt/mqm/lib -L/usr/lib/hpux32 -lmqic_r -lpthread


C client exit, 64-bit, non-threaded

c89 +DD64 +e +z -c -D_HPUX_SOURCE -o cliexit.o cliexit.c -I/opt/mqm/inc
ld -b +noenvvar cliexit.o +ee MQStart -o /var/mqm/exits64/cliexit_64
-L/opt/mqm/lib64 -L/usr/lib/hpux64 -lmqic


C client exit, 64-bit, threaded

c89 +DD64 +e +z -c -D_HPUX_SOURCE -o cliexit.o cliexit.c -I/opt/mqm/inc
ld -b +noenvvar cliexit.o +ee MQStart -o /var/mqm/exits64/cliexit_64_r
-L/opt/mqm/lib64 -L/usr/lib/hpux64 -lmqic_r -lpthread


C server exit, 32-bit, non-threaded

c89 +e +z -c -D_HPUX_SOURCE -o srvexit.o srvexit.c -I/opt/mqm/inc
ld +b: -b srvexit.o +ee MQStart -o /var/mqm/exits/srvexit_32 -L/opt/mqm/lib
-L/usr/lib/hpux32 -lmqm


C server exit, 32-bit, threaded

c89 +e +z -c -D_HPUX_SOURCE -o srvexit.o srvexit.c -I/opt/mqm/inc
ld +b: -b srvexit.o +ee MQStart -o /var/mqm/exits/srvexit_32_r
-L/opt/mqm/lib -L/usr/lib/hpux32 -lmqm_r -lpthread


C server exit, 64-bit, non-threaded

c89 +DD64 +e +z -c -D_HPUX_SOURCE -o srvexit.o srvexit.c -I/opt/mqm/inc
ld -b +noenvvar srvexit.o +ee MQStart -o /var/mqm/exits64/srvexit_64
-L/opt/mqm/lib64 -L/usr/lib/hpux64 -lmqm


C server exit, 64-bit, threaded

c89 +DD64 +e +z -c -D_HPUX_SOURCE -o srvexit.o srvexit.c -I/opt/mqm/inc
ld -b +noenvvar srvexit.o +ee MQStart -o /var/mqm/exits64/srvexit_64_r
-L/opt/mqm/lib64 -L/usr/lib/hpux64 -lmqm_r -lpthread

1.5.3.5 Address Space models supported by WebSphere MQ for HP-UX on IA64 (IPF)

HP-UX supports multiple Address Space models. The MPAS model is new on
the HP-UX IA64 platform.
  • MGAS - Mostly Global Address space (this is the default and is used by WebSphere MQ)
  • MPAS - Mostly Private Address space

For many types of application the Address Space model used has little apparent effect, however there are implications for applications which use System V Shared Memory. In particular, applications using the MPAS model cannot attach System V Shared Memory created by an application which is configured to use the MGAS model when the shared memory is marked as being available to 32-bit applications.

WebSphere MQ is built using the MGAS Address Space model which means that :
  • Applications built using the MGAS model can connect to WebSphere MQ.
  • Applications built using the MPAS model cannot connect to WebSphere MQ if they connect using the server libraries (libmqm etc.).
  • Applications built using the MPAS model can connect to WebSphere MQ if they connect using the client libraries (libmqic etc.), however facilities such as WebSphere MQ trace are, by default, not available.

If you have an application that is built as MPAS you can change it to use the MGAS model using the following command: chatr +as default program-name. If you have a requirement to use MPAS applications with WebSphere MQ, you can configure MQ to allow both MGAS and MPAS applications to connect by setting the variable AMQ_64BIT_SUBPOOL_ONLY; issue the command export AMQ_64BIT_SUBPOOL_ONLY=1 in the environment before starting the queue manager. This allows MPAS applications to connect to the queue manager but it prevents 32-bit applications connecting to the queue manager using the server libraries.

By default COBOL applications built using Micro Focus Sever Express are built using the MPAS model. In order to use Micro Focus COBOL applications and WebSphere MQ on the HP/IPF platform you must change the addressing model of your compiled COBOL applications to MGAS or set the AMQ_64BIT_SUBPOOL_ONLY environment variable as described above. More details on the MGAS and MPAS address space models can be found in the HP-UX documentation.

1.5.3.6 Using Micro Focus Server Express with WebSphere MQ on the HP/IPF platform

See 1.4.3.2, "Address Space models supported by WebSphere MQ for HP-UX on IA64 (IPF)" for details on using Micro Focus Server Express in conjunction with WebSphere MQ on the HP/IPF platform.

1.5.3.7 HP-UX on the IA64 (IPF) platform: SSL not FIPS-certified

The SSL/TLS software on the HP-UX for IA64 (IPF) platform is not FIPS-certified.

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

1.5.4.1 Channel exits on WebSphere MQ V6.0 for iSeries

User Data for channel exits on iSeries is not supported.

1.5.4.2 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

1.5.4.3 Connecting the WebSphere MQ V6.0 Explorer to a WebSphere MQ for
iSeries V5.3 queue manager causes the connection to be broken
when the namelists folder is selected.

This has been fixed in APAR SE19457, which is included in Fix Pack 11 (CSD11) and later for WebSphere MQ for iSeries. Fix pack 11 or later should be installed on WebSphere MQ V5.3 to resolve the problem.

1.5.5 Updates, limitations, and known problems that apply to JMS only

The following restrictions apply to JMS only:

1.5.5.1 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

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

1.5.5.3 SSLKeyReset does not work in conjunction with FIPS compliance assurance using IBM JDK 1.4.2

SSLKeyReset does not work with Sun JDKs.

1.5.5.4 SSL key reset does not work on WebSphere MQ for iSeries

The connection between the JMS/Java client and the server will fail if SSL key reset is set.

1.5.5.5 JMS receive and heartbeats

When using JMS receive, JMS currently calls an MQGET with wait but with a timeout value of 5 seconds. No heartbeats will be received by the client if the channel's heartbeat interval is set to 5 seconds or more. This will prevent functionality like reset on heartbeats working because of the lack of heartbeats from the server. However, additional key reset function has been implemented to ensure that the level of security is maintained.

1.5.5.6 FIPS compliance support

CipherSuite SSL_RSA_WITH_DES_CBC_SHA is no longer FIPS compliant when using JDK 1.4.2 SR1a and above.

1.5.5.7 FIPS compliance support and SOAP function

There is no FIPS compliance support or SOAP function on 64-bit Solaris Opteron because the 64-bit IBM JDK is not shipped on this platform.

1.5.5.8 JDBC/XA switch libraries dependencies

THE JDBC/XA switch libraries no longer have a dependency 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 dependency 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.

1.5.5.9 New Platforms

Classpath settings, installed libraries and directory structures for Solaris x86-64 are the same as for Solaris Sparc; those for Linux on zSeries and for Linux x86-64 are the same as for Linux POWER platform.

Those for HP-UX 11iV2 are the same as for HP-UX 11iV1, with the exception that shared libraries on the IA64 (IPF) platform now have the file extension .so instead of .sl.

1.5.5.10 PGM support

WebSphere MQ 6.0 includes support for subscribing to multicast-enabled topics using a direct connection to a broker where the multicast protocol defined on the broker is set to PGM/IP or UDP-encapsulated PGM. When PGM/IP is used, the client requires a native library to be present on the system path.

This library is available on the following platforms and is installed into the directory specified by MQ_JAVA_LIB_PATH:
  • AIX - libPgmIpLayer.so (32-bit only)
  • HP-UX on PA-RISC - libPgmIpLayer.sl (32-bit support)
  • Linux (x86 platform) - libPgmIpLayer.so (32-bit only)
  • Linux (zSeries platform) - libPgmIpLayer.so (32-bit only)
  • Solaris SPARC - libPgmIpLayer.so (32-bit only)
  • Windows - PgmIpLayer.dll
  • z/OS - libPgmIpLayer.so

PGM/IP cannot be used on other platforms. An error message, MQJMS_DIR_PGM_LIB_NOT_FOUND, will be thrown if the library is not present or could not be found. No configuration of the client beyond that described in WebSphere MQ Using Java is required to subscribe to PGM/IP or UDP-encapsulated PGM topics.

1.5.5.11 MQConnectionFactory property SUBSTORE support on z/OS

The JMS property SUBSTORE on MQConnectionFactory and MQTopicConnectionFactory objects can now be set to BROKER when connecting to a WebSphere MQ V.6.0 queue manager running on z/OS. Because the BROKER setting is now supported, this also means that the default setting of MIGRATE will use the BROKER style behavior and will attempt to migrate any existing durable subscriptions unless the SUBSTORE property is explicitly set to QUEUE. See WebSphere MQ Using Java for further details.

1.5.5.12 Using WebSphere MQ as external messaging provider with WebSphere Application Server

To use WebSphere MQ V6.0 or WebSphere MQ V5.3 Fix Pack 10 (CSD10) as an external messaging provider with WebSphere Application Server, IBM recommends that you use WebSphere Application Server V6.0.2 or later.

1.5.5.13 Connection user ID on connection creation

If no user ID is specified when you create a connection in client transport mode, the application process ID will now be passed to the server. Therefore, ensure this process ID has the relevant
authorizations on the server machine.

1.5.5.14 Channel exits
  • In WebSphere MQ for iSeries, user data for channel exits is not supported.
  • In WebSphere MQ for Windows, native exits might not previously have been loaded correctly if the system path did not include the exits directory of the queue manager installation. This has been rectified.
  • The location of native exits for UNIX platforms is /var/mqm/exits or /var/mqm/exits64.
  • Modification of the size of the agent buffer passed to the exit is not supported.
  • The context of the information passed to native exits is solely within the domain of native exits. For example, if a Java exit and a C exit are chained, then the C exit will not be passed any information that will suggest that there is a Java exit. It will assume that it is on its own.
  • When running the WebSphere MQ Explorer it is possible to connect to a remote queue manager by using Channel Definition Tables. Setting exits for remote queue managers is also supported, but the following restrictions apply:
    • Java exits can not be loaded from a JAR or ZIP file: they must be uncompressed in the appropriate directory structure.
    • Native exits can be loaded, but the WebSphere MQ JMS/Java Client must be installed as well as the Explorer. If the JMS/Java Client is not installed, it will prevent the native exit from loading. The reason for this prerequisite is that a native utility library is required from the JMS/Java client to load the native exit.

1.5.5.15 Limitation on Linux x86-64

To run the WebSphere MQ Classes for Java or JMS in 64 bit mode, using the JDK included with the product, set the following environment variable:

TR_noLookahead=1

1.5.5.16 JMSException thrown at compile time

The com.ibm.mq.jms.MQQueueConnectionFactory and
com.ibm.mq.jms.MQTopicConnectionFactory APIs have changed in WebSphere
MQ Version 6.0: some methods in these classes can now throw exceptions of type JMSException. JMS applications that were compiled against earlier versions of the WebSphere MQ classes for JMS will continue to run successfully but if they are recompiled against the version 6.0 classes compilation errors might result. These errors contain text
similar to the following: "unreported exception javax.jms.JMSException; must be caught or declared to be thrown" and also reference the connection factory methods in question. To fix this, you must modify your applications to handle these exceptions.

1.5.6 Updates, limitations, and known problems that apply to the Linux platform only

The following restrictions apply to the Linux platform only:

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

1.5.6.2 File Transfer Application Help System

The Help option in the GUI is unavailable. You can find the html help files in /opt/mq/eclipse/plugins/com.ibm.mq.fta.doc_6.0.0/doc

1.5.6.3 Building applications on s390x

The following section contains examples of the commands used to build programs in various environments on s390x.

C client application, 32-bit, non-threaded

gcc -m31 -o amqsputc_32 amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl, -rpath=/usr/lib -lmqic


C client application, 32-bit, threaded

gcc -m31 -o amqsputc_32_r amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl, -rpath=/usr/lib -lmqic_r -lpthread


C client application, 64-bit, non-threaded

gcc -m64 -o amqsputc_64 amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl, -rpath=/usr/lib64 -lmqic


C client application, 64-bit, threaded

gcc -m64 -o amqsputc_64_r amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl, -rpath=/usr/lib64 -lmqic_r -lpthread


C server application, 32-bit, non-threaded

gcc -m31 -o amqsput_32 amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl, -rpath=/usr/lib -lmqm


C server application, 32-bit, threaded

gcc -m31 -o amqsput_32_r amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl, -rpath=/usr/lib -lmqm_r -lpthread


C server application, 64-bit, non-threaded

gcc -m64 -o amqsput_64 amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl, -rpath=/usr/lib64 -lmqm


C server application, 64-bit, threaded

gcc -m64 -o amqsput_64_r amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl, -rpath=/usr/lib64 -lmqm_r -lpthread


C++ client application, 32-bit, non-threaded

g++ -m31 -fsigned-char -o imqsputc_32 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -limqc23gl -limqb23gl -lmqic


C++ client application, 32-bit, threaded

g++ -m31 -fsigned-char -o imqsputc_32_r imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -limqc23gl_r -limqb23gl_r -lmqic_r
-lpthread


C++ client application, 64-bit, non-threaded

g++ -m64 -fsigned-char -o imqsputc_64 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -limqc23gl -limqb23gl -lmqic


C++ client application, 64-bit, threaded

g++ -m64 -fsigned-char -o imqsputc_64_r imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib64 -Wl, -rpath=/opt/mqm/lib64 -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl, -rpath=/usr/lib64 -limqc23gl_r -limqb23gl_r
-lmqic_r -lpthread


C++ server application, 32-bit, non-threaded

g++ -m31 -fsigned-char -o imqsput_32 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -Wl, -rpath=/opt/mqm/lib -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -limqs23gl -limqb23gl -lmqm


C++ server application, 32-bit, threaded

g++ -m31 -fsigned-char -o imqsput_32_r imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -limqs23gl_r -limqb23gl_r -lmqm_r
-lpthread


C++ server application, 64-bit, non-threaded

g++ -m64 -fsigned-char -o imqsput_64 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -limqs23gl -limqb23gl -lmqm


C++ server application, 64-bit, threaded

g++ -m64 -fsigned-char -o imqsput_64_r imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -limqs23gl_r -limqb23gl_r
-lmqm_r -lpthread


C client exit, 32-bit, non-threaded

gcc -m31 -shared -fPIC -o /var/mqm/exits/cliexit_32 cliexit.c
-I/opt/mqm/inc -L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib
-lmqic


C client exit, 32-bit, threaded

gcc -m31 -shared -fPIC -o /var/mqm/exits/cliexit_32_r cliexit.c
-I/opt/mqm/inc -L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib
-lmqic_r -lpthread


C client exit, 64-bit, non-threaded

gcc -m64 -shared -fPIC -o /var/mqm/exits64/cliexit_64 cliexit.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -Wl,
-rpath=/usr/lib64 -lmqic


C client exit, 64-bit, threaded

gcc -m64 -shared -fPIC -o /var/mqm/exits64/cliexit_64_r cliexit.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -Wl,
-rpath=/usr/lib64 -lmqic_r -lpthread


C server exit, 32-bit, non-threaded

gcc -m31 -shared -fPIC -o /var/mqm/exits/srvexit_32 srvexit.c
-I/opt/mqm/inc -L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib
-lmqm


C server exit, 32-bit, threaded

gcc -m31 -shared -fPIC -o /var/mqm/exits/srvexit_32_r srvexit.c
-I/opt/mqm/inc -L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib
-lmqm_r -lpthread


C server exit, 64-bit, non-threaded

gcc -m64 -shared -fPIC -o /var/mqm/exits64/srvexit_64 srvexit.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -Wl,
-rpath=/usr/lib64 -lmqm


C server exit, 64-bit, threaded

gcc -m64 -shared -fPIC -o /var/mqm/exits64/srvexit_64_r srvexit.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -Wl,
-rpath=/usr/lib64 -lmqm_r -lpthread

1.5.6.4 Building applications on x86-64

The following section contains examples of the commands used to build
programs in various environments on x86-64.

C client application, 32-bit, non-threaded

gcc -m32 -o amqsputc_32 amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -lmqic


C client application, 32-bit, threaded

gcc -m32 -o amqsputc_32_r amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -lmqic_r -lpthread


C client application, 64-bit, non-threaded

gcc -m64 -o amqsputc_64 amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -lmqic


C client application, 64-bit, threaded

gcc -m64 -o amqsputc_64_r amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -lmqic_r -lpthread


C server application, 32-bit, non-threaded

gcc -m32 -o amqsput_32 amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -lmqm


C server application, 32-bit, threaded

gcc -m32 -o amqsput_32_r amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -lmqm_r -lpthread


C server application, 64-bit, non-threaded

gcc -m64 -o amqsput_64 amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -lmqm


C server application, 64-bit, threaded

gcc -m64 -o amqsput_64_r amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,
-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -lmqm_r -lpthread


C++ client application, 32-bit, non-threaded

g++ -m32 -fsigned-char -o imqsputc_32 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -Wl, -rpath=/opt/mqm/lib -L/opt/mqm/lib -Wl,
-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -limqc23gl -limqb23gl -lmqic


C++ client application, 32-bit, threaded

g++ -m32 -fsigned-char -o imqsputc_32_r imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -L/opt/mqm/lib
-Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -limqc23gl_r -limqb23gl_r
-lmqic_r -lpthread


C++ client application, 64-bit, non-threaded

g++ -m64 -fsigned-char -o imqsputc_64 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -L/opt/mqm/lib64
-Wl,-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -limqc23gl -limqb23gl
-lmqic


C++ client application, 64-bit, threaded

g++ -m64 -fsigned-char -o imqsputc_64_r imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -L/opt/mqm/lib64
-Wl,-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -limqc23gl_r -limqb23gl_r
-lmqic_r -lpthread


C++ server application, 32-bit, non-threaded

g++ -m32 -fsigned-char -o imqsput_32 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -L/opt/mqm/lib
-Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -limqs23gl -limqb23gl -lmqm


C++ server application, 32-bit, threaded

g++ -m32 -fsigned-char -o imqsput_32_r imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -L/opt/mqm/lib
-Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -limqs23gl_r -limqb23gl_r
-lmqm_r -lpthread


C++ server application, 64-bit, non-threaded

g++ -m64 -fsigned-char -o imqsput_64 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -L/opt/mqm/lib64
-Wl,-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -limqs23gl -limqb23gl -lmqm


C++ server application, 64-bit, threaded

g++ -m64 -fsigned-char -o imqsput_64_r imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -L/opt/mqm/lib64
-Wl,-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -limqs23gl_r -limqb23gl_r
-lmqm_r -lpthread


C client exit, 32-bit, non-threaded

gcc -m32 -shared -fPIC -o /var/mqm/exits/cliexit_32 cliexit.c
-I/opt/mqm/inc -L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib
-lmqic


C client exit, 32-bit, threaded

gcc -m32 -shared -fPIC -o /var/mqm/exits/cliexit_32_r cliexit.c
-I/opt/mqm/inc -L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib
-lmqic_r -lpthread


C client exit, 64-bit, non-threaded

gcc -m64 -shared -fPIC -o /var/mqm/exits64/cliexit_64 cliexit.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64
-Wl,-rpath=/usr/lib64 -lmqic


C client exit, 64-bit, threaded

gcc -m64 -shared -fPIC -o /var/mqm/exits64/cliexit_64_r cliexit.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64
-Wl,-rpath=/usr/lib64 -lmqic_r -lpthread


C server exit, 32-bit, non-threaded

gcc -m32 -shared -fPIC -o /var/mqm/exits/srvexit_32 srvexit.c -I/opt/mqm/inc
-L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib -lmqm


C server exit, 32-bit, threaded

gcc -m32 -shared -fPIC -o /var/mqm/exits/srvexit_32_r srvexit.c
I/opt/mqm/inc -L/opt/mqm/lib -Wl,-rpath=/opt/mqm/lib -Wl,-rpath=/usr/lib
lmqm_r -lpthread


C server exit, 64-bit, non-threaded

gcc -m64 -shared -fPIC -o /var/mqm/exits64/srvexit_64 srvexit.c
I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64
Wl,-rpath=/usr/lib64 -lmqm


C server exit, 64-bit, threaded

gcc -m64 -shared -fPIC -o /var/mqm/exits64/srvexit_64_r srvexit.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64
Wl,-rpath=/usr/lib64 lmqm_r -lpthread

1.5.6.5 Migrating from V6 32bit to V6 64bit products is not supported.

On 64-bit platforms where WebSphere MQ provides both a 32-bit and a 64-bit product (Linux x86 and Linux zSeries), there is NO migration path from V6 32-bit Queue Managers to V6 64-bit Queue Managers. Customers are strongly advised to install WebSphere MQ 64-bit products on 64-bit platforms as there is a migration path from V5 32-bit products to V6 64-bit products.

1.5.6.6 Red Hat Linux V4.0 on x86-64 platform: SSL not FIPS-certified

The SSL/TLS software on the Red Hat Linux V4.0 on x86-64 platform
is not FIPS-certified.

1.5.6.7 SuSE Linux Enterprise Server (SLES) V9 on x86-64 platform: SSL not FIPS-certified

The SSL/TLS software on the SuSE Linux Enterprise Server (SLES) V9 on x86-64 platform is not FIPS-certified.

1.5.7 Updates, limitations, and known problems that apply to the Solaris platform only

The following restrictions apply to the Solaris platform only:

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

1.5.7.2 Building applications on x86-64

The following section contains examples of the commands used to build
programs in various environments on x86-64.

C client application, 32-bit

cc -xarch=386 -mt -o amqsputc_32 amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib
-R/opt/mqm/lib -R/usr/lib/32 -lmqic -lmqmcs -lmqmzse -lsocket -lnsl -ldl


C client application, 64-bit

cc -xarch=amd64 -mt -o amqsputc_64 amqsput0.c -I/opt/mqm/inc
-L/opt/mqm/lib64 -R/opt/mqm/lib64 -R/usr/lib/64 -lmqic -lmqmcs
-lmqmzse -lsocket -lnsl -ldl


C server application, 32-bit

cc -xarch=386 -mt -o amqsput_32 amqsput0.c -I/opt/mqm/inc -L/opt/mqm/lib
-R/opt/mqm/lib -R/usr/lib/32 -lmqm -lmqmcs -lmqmzse -lsocket -lnsl -ldl


C server application, 64-bit

cc -xarch=amd64 -mt -o amqsput_64 amqsput0.c -I/opt/mqm/inc
-L/opt/mqm/lib64 -R/opt/mqm/lib64 -R/usr/lib/64 -lmqm -lmqmcs -lmqmzse
-lsocket -lnsl -ldl


C++ client application, 32-bit

CC -xarch=386 -mt -o imqsputc_32 imqsput.cpp -I/opt/mqm/inc -L/opt/mqm/lib
-R/opt/mqm/lib -R/usr/lib/32 -limqc23as -limqb23as -lmqic -lmqmcs -lmqmzse
-lsocket -lnsl -ldl


C++ client application, 64-bit

CC -xarch=amd64 -mt -o imqsputc_64 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib64 -R/opt/mqm/lib64 -R/usr/lib/64 -limqc23as -limqb23as
-lmqic -lmqmcs -lmqmzse -lsocket -lnsl -ldl


C++ server application, 32-bit

CC -xarch=386 -mt -o imqsput_32 imqsput.cpp -I/opt/mqm/inc -L/opt/mqm/lib
-R/opt/mqm/lib -R/usr/lib/32 -limqs23as -limqb23as -lmqm -lmqmcs -lmqmzse
-lsocket -lnsl -ldl


C++ server application, 64-bit

CC -xarch=amd64 -mt -o imqsput_64 imqsput.cpp -I/opt/mqm/inc
-L/opt/mqm/lib64 -R/opt/mqm/lib64 -R/usr/lib/64 -limqs23as -limqb23as -lmqm
-lmqmcs -lmqmzse -lsocket -lnsl -ldl


C client exit, 32-bit

cc -xarch=386 -mt -G -KPIC -o /var/mqm/exits/cliexit_32 cliexit.c
-I/opt/mqm/inc -L/opt/mqm/lib -R/opt/mqm/lib -R/usr/lib/32 -lmqic -lmqmcs
-lmqmzse -lsocket -lnsl -ldl


C client exit, 64-bit

cc -xarch=amd64 -mt -G -KPIC -o /var/mqm/exits64/cliexit_64 cliexit.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -R/opt/mqm/lib64 -R/usr/lib/64 -lmqic
-lmqmcs -lmqmzse -lsocket -lnsl -ldl


C server exit, 32-bit

cc -xarch=386 -mt -G -KPIC -o /var/mqm/exits/srvexit_32 srvexit.c
-I/opt/mqm/inc -L/opt/mqm/lib -R/opt/mqm/lib -R/usr/lib/32 -lmqm -lmqmcs
-lmqmzse -lsocket -lnsl -ldl


C server exit, 64-bit

cc -xarch=amd64 -mt -G -KPIC -o /var/mqm/exits64/srvexit_64 srvexit.c
-I/opt/mqm/inc -L/opt/mqm/lib64 -R/opt/mqm/lib64 -R/usr/lib/64 -lmqm
-lmqmcs -lmqmzse -lsocket -lnsl -ldl


1.5.7.3 Solaris x86-64: SSL not FIPS-certified

Note that if you are using SSL/TLS on Solaris X86-64, the cryptography included in GSkit, which is used to provide the SSL/TLS support, is not FIPS-certified. If you attempt to start an SSL/TLS channel in a queue manager environment on Solaris X86-64 with the SLFIPS/SSLFipsRequired queue manager attribute set to YES/MQSSL_FIPS_YES, the attempt will fail with error message AMQ9620. Similarly, if you attempt to start an SSL/TLS channel in a WMQ client environment on Solaris X86-64 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.


1.5.8 Updates, limitations, and known problems that apply to the Windows platform only

The following restrictions apply to the Windows platform only:

1.5.8.1 SSL secret key reset

SSL secret key reset cannot be used on an SSL/TLS 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.

1.5.8.2 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:
  1. Bring up the Local Security Policy tool, click on Security Settings ->Local Policies->User Right Assignments, click on "Debug Programs".
  2. 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.

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

When you run the .NET SOAP/WebSphere MQ listener amqwSOAPNETListener, the -d option is ignored if the option -x twoPhase is specified.

1.5.8.4 Using a WebSphere MQ for Windows Version 5.3 Explorer with a WebSphere MQ for Windows Version 6.0 queue manager

If you intend to use a WebSphere MQ for Windows Version 5.3 Explorer to administer a Version 6 queue manager, you should install Fix Pack 9 (CSD9) or later on your WebSphere MQ for Windows V5.3 queue manager.

(1.5.8.5) Section deleted: problem fixed in version 6.0.1.0

1.5.8.6 Shutdown Information Centre before uninstalling

If you have the Information Center installed and intend to remove it before installing the Client or Server you must carry out an additional step to ensure the Eclipse framework has been shutdown completely.

Before uninstalling the Information Centre issue the following command:

Information_Center_install_directory\bin\ strmqinf /shutdown

If you omit this step you might experience difficulty with the subsequent product installation.

1.5.8.7 Shutdown Information Centre before changing language

If you are running the Information Center in one language and wish to change languages, you must shut down the Eclipse framework completely by issuing the following command:

Information_Center_install_directory\bin\ strmqinf /shutdown

If you simply close the Information Center and reopen it in the new language, it will still see be displayed in the original language because the configuration information has been cached.

1.6 Documentation updates

1.6.1 GC34-6476 - WebSphere MQ for Windows Quick Beginnings

This information about prerequisite and optional software was not available before the book was sent to translation.

1.6.1.1 Chapter 2 "Installing the WebSphere MQ Server"

Section "Preparing for server installation"
"Prerequisite server software"
"Connectivity"

Replace the entire existing section with:
WebSphere MQ requires one of the following for SNA connectivity:
  • IBM Communications Server for Windows, Version 6.1.2
  • IBM Personal Communications, Version 5.7 (part of IBM Host Access Client Package [HACP], Version 4.0)
  • Microsoft Host Integration Server 2004
  • Microsoft Host Integration Server 2000
  • Attachmate myEXTRA! Presentation Services, Version 7.11
  • Attachmate EXTRA! Enterprise 2000
  • Attachmate EXTRA! Personal Client, Version 6.7
  • CP/IP (provided by the operating system; IP, Version 6 feature provided on Windows XP with SP1 or later, and on Windows Server 2003 or later)
  • NetBIOS (provided by the operating system)
  • Sequenced Package Exchange (SPX) (provided by the operating system)"

Section "Preparing for server installation"
"Optional server software"

Replace:
"The following are options, not prerequisites. Minimum supported
levels are shown,

External transaction processing monitors
  • IBM WebSphere Application Server (WAS) V5.1"

with:
"The following are options, not prerequisites. Minimum supported
levels are shown,

External transaction processing monitors
  • IBM WebSphere Application Server (WAS) V5.1
  • IBM WebSphere Application Server, Version 6.0.1"

Replace:
"Databases
  • Sybase Adaptive Server Enterprise (ASE) 12.5.1"

with:
"Databases
  • Sybase ASE, Version 12.5.3 with ESD, Version 1
  • Sybase SDK, Version 12.5.1 with ESD, Version 7"

1.6.2 GC34-6477 - WebSphere MQ for Solaris Quick Beginnings

Throughout this book, the term "GSKit" refers to IBM Global Security Kit V7.

1.6.2.1 Chapter 2 "Installing a WebSphere MQ Server"

Section: Preparing for installation
Checking prerequisite hardware and software
Checking the operating environment - x86-64 platform
Hardware

Replace the word "Opteron" with "AMD64".

Section: Preparing for installation
Checking prerequisite hardware and software
Checking optional software - x86-64 platform
Compilers

Replace "Sun ONE Studio 10, Enterprise Edition for Solaris" with "Sun
Studio 10 for Solaris Platforms".

Remove "Micro Focus Server Express V4.0".

Section: Installation procedure
Kernel configuration

The information on checking and setting kernel configuration parameters, before the System Resource Limits section, applies only to Solaris 8 and 9. Add the following information for Solaris 10:

Before installation, review the machine's configuration. To do this type the following command as root, where project-name is the default project of the user who will start the queue manager:

prctl -i project project-name

where project-name is the default project of the user who will start the queue manager.

Compare the output with the values below

project.max-shm-memory
privileged 4.00GB - deny -
project.max-sem-ids
privileged 1024 - deny -

For information on setting up the system, see the System Administration
Guide: Solaris Containers-Resource Management and Solaris Zones for your
release of Solaris.

Section: Installation procedure
Kernel configuration
File descriptors

The command "set rlim_fd_max=10000" applies only to Solaris 8.

1.6.2.2 Chapter 3 "Installing a WebSphere MQ Client"

Section: Preparing to install
Checking hardware and software requirements
Checking the operating environment - x86-64 platform
Hardware

Replace the word "Opteron" with "AMD64".

Section: Preparing to install
Checking hardware and software requirements
Checking optional software - x86-64 platform
Compilers

Replace "Sun ONE Studio 10, Enterprise Edition for Solaris" with "Sun
Studio 10 for Solaris Platforms".

Remove "Micro Focus Server Express V4.0".

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

1.6.3.1 Chapter 2 "Installing a WebSphere MQ Server"

Section: Preparing for installation
Checking prerequisite hardware and software
Checking the operating environment - IA64 (IPF) platform
Table 4. Storage requirements for a WebSphere MQ
server

As there is no support for 32-bit SSL, the row for "IBM Global Security
Kit V7 (32-bit)" should be removed.

1.6.3.2 Chapter 3 "Installing a WebSphere MQ Client"

Section: Preparing to install
Checking hardware and software requirements
Checking the operating environment - IA64 (IPF) platform
Table 8. Storage requirements for a WebSphere MQ
client

As there is no support for 32-bit SSL, the row for "IBM Global Security Kit V7 (32-bit)" should be removed.

1.6.4 GC34-6480 - WebSphere MQ for Linux Quick Beginnings

1.6.4.1 Chapter 2 "Installing a WebSphere MQ Server"

Section: Preparing for installation
Checking prerequisite hardware and software
Checking the operating environment
Operating System, WebSphere MQ for Linux,
Version 6.0 (x86-64 platform)

Replace "Red Hat Linux V4.0" with "Red Hat Enterprise Linux V4.0"

Section: Preparing for installation
Checking prerequisite hardware and software
Checking the operating environment
Operating System, WebSphere MQ for Linux,
Version 6.0 (zSeries platform)
Connectivity requirements

Add the following communications server to the list in this section:
  • IBM Communications Server for Linux, Version 6.2 (SNA)

Section: Preparing for installation
Checking prerequisite hardware and software
Checking the operating environment
Operating System, WebSphere MQ for Linux,
Version 6.0 (zSeries s390x platform)
Connectivity requirements

Add the following communications server to the list in this section:
  • IBM Communications Server for Linux, Version 6.2 (SNA)

Section: Preparing for installation
Checking prerequisite hardware and software
Checking optional software - x86-64 platform
Java Messaging and SOAP transport

Both 32-bit and 64-bit JDKs are available on this platform.

Section: Preparing for installation
Checking prerequisite hardware and software
Checking optional software - POWER platform
Transaction monitors

Add this line to the list of transaction monitors:
  • WebSphere Application Server V5.1 (SUSE LINUX Enterprise Server (SLES) 9 only)

Section: Preparing for installation
Checking prerequisite hardware and software
Checking optional software - x86-64 platform
Databases

Remove the line
  • Sybase Adaptive Server Enterprise (ASE) 12.5.3 with ESD Version 1

This database is not supported.

Replace the line
  • Informix Dynamic Server (IDS) V10

with
  • Informix Dynamic Server (IDS) V10 plus Client SDK V2.90

1.6.4.2 Chapter 3 "Installing a WebSphere MQ Client"

Section: Preparing to install
Checking hardware and software requirements
Checking the operating environment
Operating System, WebSphere MQ for Linux,
Version 6.0 (x86-64 platform)

Replace "Red Hat Linux V4.0" with "Red Hat Enterprise Linux V4.0"

Section: Preparing to install
Checking hardware and software requirements
Checking optional software - POWER platform

Add a new section "Transaction monitors"

1.6.4.2.1 Transaction Monitors

  • BEA WebLogic Server, Version 8.1 (for RHEL, Version 3.0)
  • WebSphere Application Server, Version 6.0.2
  • WebSphere Application Server (WAS) V5.1 (SUSE LINUX Enterprise Server (SLES) 9 only)

WebSphere MQ for Linux, Version 6.0 supports WebSphere Application Server as an XA coordinator. For more information about the WebSphere MQ application adaptor, see the WebSphere Application Server Enterprise Edition WebSphere MQ Application Adaptor Development Guide, SC09-4444.

1.6.5 SC34-6584 - WebSphere MQ System Administration Guide

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

1.6.5.2 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

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

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

1.6.5.5 Chapter 11 "Transactional support"

Section: "Scenario 2: Other software provides the coordination"
"External syncpoint coordination"
"The WebSphere MQ XA switch structure"
"Table 14"

The filenames given for HP-UX, with the extension .sl, apply to WebSphere MQ for HP-UX running on the PA-RISC platform. On the IA64 (IPF) platform, the extension is .so.

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

1.6.5.7 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"

1.6.5.8 Appendix D "Stopping and removing queue managers manually"



Section: "Stopping a queue manager manually"

The name of the OAM process is given as AMQFUMA for Windows and amqfuma for UNIX systems. It should be AMQZFUMA and amqzfuma respectively.

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

1.6.6 SC34-6590 - WebSphere MQ Clients

1.6.6.1 Chapter 5 "Configuring an extended transactional client"

Section "XA compliant transaction managers"
"The xa_open string"
"How an extended transactional client uses an xa_open
string"
"Table 14"

The filenames given for HP-UX, with the extension .sl, apply to WebSphere MQ for HP-UX running on the PA-RISC platform. On the IA64 (IPF) platform, the extension is .so.

1.6.6.2 Chapter 12 "Building applications for WebSphere MQ clients"

Section "Linking C applications with the WebSphere MQ client code"

The filenames given for HP-UX, with the extension .sl, apply to WebSphere MQ for HP-UX running on the PA-RISC platform. On the IA64 (IPF) platform, the extension is .so.

Section "Linking COBOL applications with the WebSphere MQ client code"

The filename given for HP-UX, with the extension .sl, applies to WebSphere MQ for HP-UX running on the PA-RISC platform. On the IA64 (IPF) platform, the extension is .so.

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

1.6.7.1 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 then 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."


1.6.7.2 Chapter 2 "The MQSC commands"
Section "ALTER QMGR" command.
Parameter description: SSLCRYP
In section
"To access symmetric cipher operations through GSKit, specify the symmetric
cipher setting parameter on the PKCS11 string. The value of this parameter
is either:
SYMMETRIC_CIPHER_OFF Do not access symmetric cipher operations.
SYMMETRIC_CIPHER_ON Access symmetric cipher operations.
The maximum length of the string is 256 characters. The default value is blank."

Replace the final sentence "The default value is blank." by "If the parameter is not
specified, this has the same effect as specifying SYMMETRIC_CIPHER_OFF.

The maximum length of the SSLCRYP string is 256 characters. The default value is blank.".

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

1.6.8.1 Chapter 3 "Definitions of Programmable Command Formats"

Section "Delete Authority Record"
"Required parameters"

The required parameters are listed in the incorrect order.

Replace this list with the following:
"ProfileName(MQCFST)
ObjectType(MQCFIN)"

You must follow this updated list in order for the Delete Authority Record command to work.

Section "Inquire Entity Authority"
"Required parameters"

The required parameters are listed in the incorrect order.

Replace this list with the following:
"Options(MQCFIN)
ObjectType(MQCFIN)
EntityType(MQCFIN)
EntityName(MQCFST)
ObjectName (MQCFST)"

You must follow this updated list in order for the Inquire Entity Authority command to work.

1.6.8.2 Chapter 3 "Definitions of Programmable Command Formats"

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

1.6.8.3 Chapter 3 "Definitions of Programmable Command Formats"

Section "Change Queue Manager" command.
Optional Parameters:SSLCryptoHardware
In section
"To access symmetric cipher operations through GSKit, specify the symmetric
cipher setting parameter on the PKCS11 string. The value of this parameter
is either:
SYMMETRIC_CIPHER_OFF Do not access symmetric cipher operations.
SYMMETRIC_CIPHER_ON Access symmetric cipher operations.
The maximum length of the string is 256 characters. The default value is blank."

Replace the final sentence "The default value is blank." by "If the parameter is not
specified, this has the same effect as specifying SYMMETRIC_CIPHER_OFF.

The maximum length of the SSLCrytoHardware string is 256 characters. The default value is blank. ".


1.6.9 SC34-6595 - WebSphere MQ Application Programming Guide

1.6.9.1 Chapter 6 "Introducing the Message Queue Interface"

Section: "What is in the MQI?"
"WebSphere MQ stub programs and library files"
"WebSphere MQ for HP-UX"

The filenames given, with the extension .sl, apply to WebSphere MQ for HP-UX running on the PA-RISC platform. On the IA64 (IPF) platform, the extension is .so.

1.6.9.2 Chapter 21"Building your application on HP-UX"

Section: "Preparing C programs"
"Linking libraries"

The filenames given, with the extension .sl, apply to WebSphere MQ for HP-UX running on the PA-RISC platform. On the IA64 (IPF) platform, the extension is .so.

Section: "Preparing COBOL programs"

The filenames given, with the extension .sl, apply to WebSphere MQ for HP-UX running on the PA-RISC platform. On the IA64 (IPF) platform, the extension is .so.

1.6.9.3 Chapter 22 "Building your application on Linux"

New section: "Preparing COBOL programs"

Follow the instructions for preparing COBOL programs in Chapter 21 "Building your application on HP-UX" but exclude the paragraph "Programs to run in the Websphere MQ client environment".

1.6.9.4 Chapter 24 "Building your application on Solaris"

The instructions published in this chapter are incorrect for COBOL programs. Replace the paragraphs starting 'Before preparing your COBOL programs, check with your system administrator' to the end of the section with:
Compile the programs using Micro Focus compiler. The copy files
that declare the structures are in /opt/mqm/inc:
$ export LIB=/opt/mqm/lib:$LIB
$ export COBCPY="<COBCPY>"

Compiling 32 bit programs: $ cob32 -xv amqs0put0.cbl -L
/opt/mqm/lib -lmqmcb

Server for COBOL

$ cob32 -xv amqs0put0.cbl -L /opt/mqm/lib -lmqicb

Client for COBOL

$ cob32 -xtv amqs0put0.cbl -L /opt/mqm/lib -lmqmcb_r

Threaded Server for COBOL

$ cob32 -xtv amqs0put0.cbl -L /opt/mqm/lib -lmqicb_r

Threaded Client for COBOL

Compiling 64-bit programs: $ cob64 -xv amqs0put0.cbl -L
/opt/mqm/lib64 -lmqmcb

Server for COBOL

$ cob64 -xv amqs0put0.cbl -L /opt/mqm/lib64 -lmqicb

Client for COBOL

$ cob64 -xtv amqs0put0.cbl -L /opt/mqm/lib64 -lmqmcb_r

Threaded Server for COBOL

$ cob64 -xtv amqs0put0.cbl -L /opt/mqm/lib64 -lmqicb_r

Threaded Client for COBOL

where amqs0put0.cbl is a sample program. You need to link your program with one of the following:
libmqmcb.sl

Server for COBOL

libmqicb.sl

Client for COBOL

libmqmcb_r.sl

Threaded Server applications

libmqicb_r.sl

Threaded Client applications

1.6.10 GC34-6601 - WebSphere MQ Messages

1.6.10.1 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, AS/400, Sun Solaris.

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

1.6.11 SC34-6651 - WebSphere MQ Transport for SOAP

1.6.11.1 Chapter 8 "Senders and listeners"

Section "Listeners"
".NET SOAP/WebSphere MQ listener"

This is new information:

"When you run the .NET SOAP/WebSphere MQ listener amqwSOAPNETListener, the -d option is ignored if the option -x twoPhase is specified."

1.6.12 SC34-6591 - Using Java

1.6.12.1 Appendix D. SSL CipherSpecs and CipherSuites

Table 34

The row for CipherSpec TLS_RSA_WITH_DES_CBC_SHA currently has the value "No" in the column headed "Connection possible if SFIPS is set to NO?" and "Yes" in the column headed "Connection possible if SFIPS is set to YES?". If you are using JDK 1.4.2 SR1a or above, both columns should read "No". This is because the CipherSuite SSL_RSA_WITH_DES_CBC_SHA is no longer a valid FIPS compliant CipherSuite.

1.7 Contacting IBM Software Support

IBM Software Support provides assistance with product defects. You might be able to solve you own problem without having to contact IBM Software Support. The WebSphere MQ Support Web page (http://www.ibm.com/software/integration/wmq/support/) contains links to a variety of self-help information and technical flashes. The MustGather Web page (http://www.ibm.com/support/docview.wss?rs=171&uid=swg21229861) contains diagnostic hints and tips that will aid in diagnosing and solving problems, as well of details of the documentation required by the WebSphere MQ support teams to diagnose problems.

Before you 1.7.3, "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 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:
  1. 1.7.1, "Determine the business impact of your problem"
  2. 1.7.2, "Describe your problem and gather background information"
  3. 1.7.3, "Submit your problem"

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

1.7.2 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. See the MustGather Web page: http://www.ibm.com/support/docview.wss?rs=171&uid=swg21229861 for details of the documentation required. To save time, know the answers to these questions:
  1. What software versions were you running when the problem occurred?
  2. Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information.
  3. Can you re-create the problem? If so, what steps do you perform to re-create the problem?
  4. 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?
  5. Are you currently using a workaround for the problem? If so, please be prepared to describe the workaround when you report the problem.

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




Change History
31 Oct 2005 - Changes from the 6.0.1.0 version of the readadd file are
incorporated:
8th November 2005 - Update since version 6.0.1.0 shipped
18th November 2005 - Further updates
1st December 2005 - Further updates

[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Documentation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF012","label":"IBM i"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

WMQ MQ

Document Information

Modified date:
17 June 2018

UID

swg27006845