Readme for IBM WebSphere MQ for HP NonStop Server, Version 5.3.1

Content

DESCRIPTION
============

This file describes product limitations and known problems.
The latest version of this file can be found here:
https://ibm.biz/mqreadmes

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

UPDATE HISTORY
13 Oct 2017 - Updated the title and the platform attribute, and added the DESCRIPTION section.
31 Jan 2007 - Original version created.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


CONTENTS
========

- Introduction
- About this release
- Installation, migration, upgrade and configuration information
- Uninstallation information
- Known limitations, problems and workarounds
- Documentation updates
- Contacting IBM software support
- Notices and Trademarks


INTRODUCTION
============

Welcome to IBM WebSphere MQ for HP NonStop Server, Version 5.3.1.

This release notes file applies to the latest WebSphere MQ cross-platform
books (for Version 5.3), and to the WebSphere MQ for HP NonStop Server,
Version 5.3 specific books (WebSphere MQ for HP NonStop Server System
Administration Guide and WebSphere MQ for HP NonStop Server Quick
Beginnings).

The content of these release notes applies to the WebSphere MQ for HP
NonStop Server product unless otherwise stated.

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

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

For current information on known problems and available fixes,
SupportPacs(TM), product documentation and online versions of this and
other readme files see the Support page of the WebSphere MQ Web site at:

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


ABOUT THIS RELEASE
==================

New in this release
-------------------

This is the first refresh of IBM WebSphere MQ V5.3 for HP NonStop Server, and
is designated V5.3.1 (or V5.3.1.0).

The following items of new function are released with V5.3.1. This
completes the planned function for V5.3 releases. Several documentation
supplements are supplied with this release in directory opt/mqm/READMES/En_US
or in the root directory of the CD-ROM image. The documentation supplements
are identified in this section, where available, for each area of new
function. You will need to use an Adobe Acrobat reader application on a PC
workstation to review this documentation.

1) Full function upgmqm

This release of upgmqm replaces the version shipped at GA, and provides
function for creating a V5.3 queue manager using equivalent configuration
and object definitions as a V5.1 queue manager. Also provided is the
ability to migrate persistent messages to the V5.3 queue manager, and to
migrate from one system to another on the same EXPAND network. For
full details about upgmqm, review the documentation supplement named
Upgmqmreadme.pdf.

2) SNA (LU6.2) channels

This release includes support for channels using the HP SNAX and
ACI Communication Services for Advanced Networking (formally known as ICE)
SNA products as the transport. The configuration method for SNA attributes
in channels has changed from the previous release and these changes must be
made manually since no support is provided in upgmqm for migrating SNA
channels. A documentation supplement for SNA channels for HP NonStop
Server is provided called SNAchannels.pdf.

3) API exits

Support is enabled in this release for API exits for both OSS and
Guardian applications. API exits allow you to intercept calls to the MQI
made by your applications, examine and if necessary change, data passed in
or out of the MQI function. No application code changes are required in
order to use API exits. API exits are not supported for TNS applications,
but for all other types of applications, standard function is supported.
In order to support API exits, a change in the way that all user exits and
pluggable services code is configured for the PIC environment has been
made. For full details about the use, configuration and development of
user exits, and especially API exits, please review the WebSphere MQ V5.3
for HP NonStop Server System Administration Guide and the documentation
supplement for API exits for HP NonStop Server called Exits.pdf.

4) Java and JMS classes

This release includes the Java and JMS classes for WebSphere MQ V5.3. The
Java and JMS classes are supplied with the base product in this release,
rather than as SupportPac MA88, which was the case previously with V5.1.
The functional level supported is equivalent to the level supported with
WebSphere MQ V5.3 for "distributed" platforms at the CSD06 level. For full
details of the use and configuration of Java and JMS classes, review
the WebSphere MQ V5.3 Using Java document and the documentation supplement
for Java and JMS classes for HP NonStop Server provided in directory
opt/mqm/READMES/En_US, called Java.pdf.

5) Publish / Subscribe broker

This is the first release of the WebSphere MQ Publish / Subscribe broker
for the HP NonStop Server platform. The functionality of the broker is
equivalent to that released for WebSphere MQ V5.3 "distributed" platforms
at the CSD08 level. Before V5.3, the WebSphere MQ Publish / Subscribe
broker was released as SupportPac MA0D. The Publish / Subscribe broker
for WebSphere MQ V5.3 for HP NonStop Server is restricted to operation in
a single CPU in this initial release. For full details of the use and
configuration of Publish/Subscribe, please review the WebSphere MQ V6.0
Publish/Subscribe User Guide and the documentation supplement for
Publish/Subscribe on HP NonStop Server provided in directory
opt/mqm/READMES/En_US, called Pubsub.pdf.

6) Installation archive and backout

Instmqm has been enhanced to provide the ability to back-out an ungrade
installation, and the ability to archive and restore installations
individually. Before instmqm starts to make changes to a system, it will
automatically create an archive of the current installation (OSS opt tree
and Guardian installation subvolumes only)in the root directory containing
the opt tree in OSS. If a failure occurs during installation, and instmqm
has made changes, the user will be asked if they wish to restore the

installation to its original state using archive created before changes

were made. At the end of a successful installation, instmqm will now
automatically create a backup archive of the new installation.

Instmqm also supports two new command line options to support creating and
using backup archives independently from an installation:

-b create a backup archive of the installation
-x restore an installation from a backup archive

These options may not be combined with any other options. Both options
require the user to respond to questions at the terminal.

A backup archive file is an OSS pax file, created as follows:

- the Guardian PAK utility is used to create a backup of the three
Guardian subvolumes for the installation in a file named "WMQSAVED"
- the PAK backup file is copied to the OSS opt directory of the
installation that is being archived
- the entire OSS opt tree of the installation (which now includes WMQSAVED)is then archived by the OSS pax utility

Backup archive files are always created in the directory that holds the
OSS opt tree for the installation. Archive files created automatically
by instmqm are named "mqarchive-yymmdd-hhmmss" where "yymmdd" and "hhmmss"
are numeric strings of the date and time that the backup archive was
created - for example: "mqarchive-061005-143606".


Product fix history
-------------------

The following APAR fixes are released in V5.3.1:

APAR IC49282 - add diagnostic output for socket validation failures during
install (982)
APAR IC50198 - H06.06 T1248^AAX pthreads generates FDC for invalid sigwait
option setting (1010)
APAR IC50339 - MCA abend when MQEMSEVENTS is set with H06.06 T1248^AAX
pthreads (1033)
APAR IC50544 - qm.ini AdoptMCA settings abends Channel Server (1046)
APAR IC50685 - MQMTNS can be installed incorrectly for H06.06 or G06.29 or
later (1074)
APAR IC50729 - MQGET not returning 2024 under same conditions as MQPUT. Use
FDC to differentiate between TMF lock limit and Buffer size
error (1065)
APAR IC50761 - updated entropy daemon to be more efficient in generation of
random data to improve SSL channel startup time (1045)
APAR IC50808 - batchsize greater than 101 causes Channel Server to abend.
Batch size limited to 2000 now (1083)
APAR IC50821 - RESET QMGR TYPE(NSPROC) command doesn't function
APAR IC51117 - crtmqm fails when creating queue manager with a name longer than
16 characters (603)
APAR IC51349 - channel fails with 2232 with change of message size caused by
incorrect handling of large messages in MQGET without accept
truncated message option (1125)
APAR IC51382 - threaded MCA process hang, unexpected termination and listener
hang
APAR IC51418 - SIGHUP handling with runmqsc causes high CPU usage (1118)

The following APAR fixes originally made in V5.1 have been ported to V5.3.1:

APAR IC43901 - change to handle recovery from an I/O error after the main
q-file message record has been read and deleted. Caused a
stuck message (983)
APAR IC47685 - buffering corrections in QS
APAR IC48365 - feedback backup context errors to Primary and backout operation
properly

The following fixes discovered during IBM's development and testing
work are also released with V5.3.1:

635 - Beta PMR 19224. Guardian MQ TACL macros can't run processes nowait
671 - dltmqm fails with error code 20806038 if run immediately after a crtmqm
command
687 - FDC from dmpmqaut
808 - MQPUT of segmented messages and Queue Server segmentation is not working
properly to a transmission queue
830 - reject an attempt to close a permanent dynamic queue using the
MQCO_DELETE_PURGE option when the queue contains uncommitted messages
851 - MQINQ/MQSET not failing with MQRC_OBJECT_CHANGED if a change is made to
the object that invalidates the handle
853 - runmqlsr's -g and -u options are not listed in the usage display
858 - GroupID in MQMD not being returned to application on MQPUT to a
transmission queue
867 - when a channel rule specifies a process name, and an MCA is inactive and
running with that process name, the EC wasn't selecting it as available
for allocation. Same problem with Application Rules was also fixed
876 - attempts to create a channel using MQ Explorer abends Command Server
884 - build and ship the C++ samples
913 - signal handling not enabled by default in threaded environments. Set
the HP environment variable to enable it on the later versions of
pthreads libraries that provide support (SPR T1248H06^AAX or later on
H-Series and SPR T1248G07^AAY on G-Series)
916 - improved error handling for TMF errors
921 - MQPUT/MQOPEN memory leak
925 - message grouping does not work properly
926 - instmqm fails on production systems where c89 may not be installed
929 - MQDISC assertion caused by memory management defect
930 - endmqm -i does not end queue manager with sample application running
931 - EC tells threaded agents to die prematurely when pooling disabled
935 - rrxGetNextStatusEntry generating FDC on Channel Server takeover testing
936 - process executable file names truncated in trace files
940 - EC log entry for MCA process restart after cpu down has LQMA for the
process type - it should be MCA
944 - multiple instances of endmqlsr can hang and fail to end listeners
946 - if the master REPMAN is abended, it fails to restart
947 - error processing invalid (negative) context handle in PMO for MQPUT
950 - channel/application rules containing ProcessName are not handled
properly if the processname is in use when the EC receives a failure
starting the agent
954 - problem using channel rules for process name and process name root
955 - the STATUS field can show extra characters when refreshed on Monitoring
panels for channel status
956 - process name rule not always being obeyed by EC
958 - protect unthreaded MCA from being given another channel to run if it has
one active already
959 - the Channel Server could lock up waiting for reply from MCA
967 - support for ssl passphrases longer than 8 characters
969 - EC should checkpoint the qmproc.ini data rather than letting the backup
process re-read the qmproc.ini file when a new backup is created
970 - EC log messages 8813 and 8814 contain extraneous word
971 - under some circumstances the EC doesn't keep accurate record of process
names in use for a process name template
973 - if the Hometerm is not available and instmqm aborts, it leaves the
hometerm program in <GuardianSample>, which has to be removed manually
before a new instmqm can be performed
978 - if a process management rule in qmproc.ini contains a ProcessNameRoot
attribute, the process name template is not always used in creating an
agent or selecting an idle agent from the pool who's process name
matches the template name
979 - fix EC problem handling 3 cpu failure tests
985 - when an unthreaded Listener is used the EC will sometimes abend when a
new MCA is started to bring the unthreaded idle pool up to it's minimum
value
989 - defect in pathway COOL start code only shows up in optimized code
990 - strmqm can fail with "pathmon process name error" when PATHMON is using
a dynamic process name
991 - fix Queue Server memory leak when Touch file does not exist
994 - display application type "NSK" instead of "13" in RUNMQSC
DISPLAY PROCESS command
1000 - timing problem in strmqm between qmgrsvr and OAM server resulted in
FDCs during queue manager start
1001 - insufficient error handling in name mangling algorithm for choosing real
file names for objects
1007 - pool limit reached message not logged correctly by MCA. Added message
AMQ9720 to report this
1011 - sample program (amqsblst.c) throws unresolved Text Symbol "usleep" error
during runtime
1015 - correction to handling of long queue manager names
1016 - error in MQCONNX processing MQ_CONNECT_TYPE environment variable
1018 - added message AMQ8570 to report an error reading the qmproc.ini file
1020 - improve Queue Server handling of "disc down" file system error 60
1021 - improve API exit usability - exclude API exits from channel server
1027 - sample program amqsaxe0.c fails to compile
1035 - an incorrect or unrecognized entry in the Channels stanza of qm.ini
causes the Channel Server to abend repeatedly and queue manager to fail
to start
1043 - problems with memory management in local queue manager agent (LQMA)
1044 - corrections for installations that do not choose to install SSL
1052 - MQGMO_LOCK and MQGMO_UNLOCK options not working correctly in MQGET
1068 - all processes should open stdfiles at startup so standard file
descriptors are not used for other opens
1081 - channels do not get triggered when COA reports put to a transmission
queue
1084 - channel server uses incorrect checkpoint logic that may cause memory
overwrites in some circumstances
1095 - unnecessary FDC in kqiDeleteQPath causing MCA to terminate
1099 - add the OSS pin to AMQ8823 EC detected an unexpected process termination
message
1105 - the Queue Server abends when reloading NPM messages for queue with
NPMCLASS(HIGH)
1107 - improvements to the threaded agent pool processing logic
1109 - improve recovery of a no-syncpoint multi-ipc MQGET when the queue server
backup fails
1112 - EC doesn't update thread statistics when an MCA terminates unexpectedly
1113 - extraneous object free following qtype error in remote queue resolution
caused FDC
1114 - EC's threaded allocation algorithm can produce unexpected results
1115 - Channel Server abend in rare Stop Channel case
1118 - enable generic signal handling correctly in certain components
1119 - added support for new environment variable override of thread stacksize
1124 - environment (Env) in AllProcesses stanza of qmproc.ini is not being
propagated to all processes
1126 - svcmqm should not issue messages if there are no deliverable files in
the lib or gbin directories
1127 - svcmqm should not reset PROGID if it updates the 3 server executables in
the Guardian executables subvolume
1130 - dspmqcsv and endmqcsv can hang on G-Series systems and display incorrect
results on H-Series (Integrity) systems
1131 - MCA will end prematurely on fcntl O_NONBLOCK socket error
1133 - add process termination info to log message from EC reporting unexpected
process failure
1137 - corrections to the AdoptMCA mechanism
1139 - MQPUT returns 2019 instead of 2009 when queue manager is quiescing
or ending
1141 - Unnecessary FDCs can be generated when using endmqm -i and -p
1142 - removed incorrect free of memory which was causing FDCs
1153 - in the event of invalid connection handle, an additional check is
required to prevent use of the invalid handle
1154 - in the event of invalid object handle, the handle requires further
validation before being used
1155 - altering TriggerMsgPriority attribute of queue does not cause trigger
message to be generated if trigger conditions are met after the change
1157 - strmqm fails when an application program is running after an endmqm -p
1158 - agents were not terminating correctly when their use count is exceeded
1159 - a misalignment in checkpointing large MQPUT and MQGET messages in the
Queue Server caused backouts under some circumstances

The following changes were also made that do not have specific problem
identifiers:

- revised Guardian administration interface to improve support for TACL
RUN options. The originally released TACL "wrapper" scripts have been
replaced with executable programs that run the OSS control programs in
such a way that they can better support various RUN options and more
closely simulate a Guardian program
- support threaded SSL channels, and improve SSL channel startup time
- all Guardian programs except command line have SAVEABEND attribute set
to ON to improve the ability to collect important failure data
- corrections to processing of shared connection handles at MQI for
threaded applications
- increased the compiler optimization level for the Integrity NonStop
Server version from 0 to 1 for improved performance
- various updates to improve service diagnostics (trace, FDCs, logging,
process attributes)
- revised the SSL samples to make certificate handling for
intercommunication with other platforms easier

All fixes that were previously released in V5.3.0.0 are also included in
this release. These fixes are listed below:

originally released in V5.3.0.0 eFix1:
Beta PMR 18886 - Command Server abend
Beta PMR 18890 - RC2072 on MQPUT/MQGET

originally released in V5.3.0.0 eFix2:
Beta PMR 19284 - Message Grouping failure
Beta PMR 19292 - Error 2009 after large number of MQPuts

originally released in V5.3.0.0 eFix3:
Beta PMR 19085 - Queue Server checkpointing problem with messages on
queue and MQPUT/ MQGET returns MQRC_HOBJ_ERROR after
takeover (877)
Beta PMR 19286 - Channel status shows BINDING
APAR IC49232 - instmqm fails trying to check OSS socket availability
APAR IC49229 - Queue server repeatedly abends when stopping primary
Queue Server process while processing messages
APAR IC49243 - Channel status item LSTSEQNUM takes too long to
refresh and wrong LSTSEQNO and CURSEQNO after
restarting channel
APAR IC49233 - Repository Manager process on the same CPU as Execution
Controller is named by system when it is restarted
APAR IC49327 - Repository manager process on cpu 0 is never restarted
after abending repository manager on cpu 1 and 0.
APAR IC49255 - Execution Controller repeatedly restarts MCA and then
abends if using ChannelNameMatch in qmproc.ini after
restarting a channel
APAR IC49269 - Execution Controller, Channel Server and Queue Server
abend when cpu down occurs
- Channel Status problem with Local Repository Manager
Cluster Channel end abnormally (773)
- An FDC file is created by the repository manager (879)
- Queue Server fix MQGET for large messages (898)
- runmqlsr using same port number on different TCP/IP
processes fails (901)
- 6 character TCP/IP process name for runmqslr fails
(902)
- Start of a second and subsequent SVRCONN channel
stays in BINDING state (912)
- Execution Controller backup has a memory leak (924)
- Channel Server generating FDC on Channel Server
takeover (935)
- nspExport failures in rrxWriteSync are not correctly
being passed back to the client (939)
- Execution Controller log entry for MCA process restart
after CPU down event shows "LQMA" instead of "MCA"
(940)

originally released in V5.3.0.0 eFix4:
Beta PMR 19253 - FDC from backup Channel Server
Beta PMR 19266 - 8 character passphrase restriction for SSL
Beta PMR 19283 - Long running TMF transaction for idle NPMSPEED(FAST)
sender channels
APAR IC49306 - Sender channel recovery problem after CPU Down
APAR IC49425 - EC Abend after CPU Down
APAR IC49512 - Channel recovery and MCA process management rules
problems after CPU Down
APAR IC49570 - Channel recovery problems after two CPU Down
events
APAR IC49567 - FDC from Channel Server with PCF message
APAR IC49566 - Pathway OWNER attribute not node independent
APAR IC49653 - Backup Queue Server out of sync with Primary and Queue
Server abend on 2nd CPU down
APAR IC49694 - Message stuck in transmission queue when I/O error occurs
while getting a persistent message (CPU Down causes
primary disk process failure)
APAR IC49454 - TNS library unresolved references in certain
methods of binding
APAR IC49492 - TNS library reduce data size to closer to V5.1 level
- serviceability improvements
- add DSPMQFLS Guardian TACL macro
- EC process management rule fixes
- Queue Server support for more than 1000 objects each
process pair - change ported from V5.1 service stream
- handling of TMF error 76
- fix regression in dynamic queues for threaded agents

originally released in V5.3.0.0 eFix4 Patch1:
APAR IC49807 - TNS application abends after several calls of MQCONN,
MQOPEN, MQCLOSE, MQDISC API

originally released in V5.3.0.0 eFix4 Patch2:
APAR IC50459 - MCA and Channel Server memory leak and incorrect handling
of "out-of-memory" situation
APAR IC50072 - MCA reuse not working correctly, leading to an accumulation
of MCA processes and eventually failure to start channels

originally released in V5.3.0.0 eFix4 Patch3:
APAR IC50790 - memory leak in MQCLOSE and memory corruption problem
APAR IC50787 - memory leak in MQDISC for FASTPATH applications, affecting
channel restart operation

originally released in V5.3.0.0 eFix4 Patch4:
APAR IC50877 - Queue Server backup and primary abended while processing
simultaneous browse MQGET, destructive MQGET and MQPUT
operations on the same queue

originally released in V5.3.0.0 eFix4 Patch5:
(no APAR) - Full function release of upgmqm migration tool


Backward compatibility
----------------------

IBM WebSphere MQ V5.3.1 for HP NonStop Server is interoperable over channels
with IBM MQSeries(TM) V5.1 for Compaq NSK, as well as any other current or
earlier version of IBM MQSeries or IBM WebSphere MQ on any other platform.

Product compatibility
---------------------

IBM WebSphere MQ V5.3.1 for HP NonStop Server is not currently compatible
with IBM WebSphere MQ Integrator Broker for HP NonStop Server.
For other compatibility considerations, review the list of suitable
products in the WebSphere MQ for HP NonStop Server Quick Beginnings book.

IBM WebSphere MQ V5.3.1 for HP NonStop Server is compatible with any
currently supported level of IBM WebSphere MQ Client. IBM WebSphere MQ V5.3.1
for HP NonStop Server does not support connections from WebSphere MQ
Extended Transactional Client.


INSTALLATION, MIGRATION, UPGRADE AND CONFIGURATION INFORMATION
==============================================================

Hardware and Software Requirements
----------------------------------

For the HP NonStop Server hardware, you must install the following system
software:

- G06.25 or later
- SPR T8306G10^ABG or later
- SPR T8994G09^AAL or later
- SPR T8397G00^ABC or later
- SPR T1248G07^AAY or later
- it is recommended to install at least the following additional SPRs:
SPR T9050AQF

For the HP Integrity NonStop Server hardware, you must install the following
system software:

- H06.05.01 or later
- SPR T8306H01^ABJ or later
- SPR T8994H01^AAM or later
- SPR T8397H01^ABD or later
- SPR T1248H06^AAX or later (see below for an additional recommendation)
- it is recommended to install SPR T1248H06^ABF since this fixes a problem
with this product (pthreads) found while using WebSphere MQ
- it is recommended to install at least the following additional SPRs:
SPR T9050AQG
- it is recommended to install SPR T1265H01^ABJ since this fixes a problem
with this product (HP TCP/IP V6) found while using WebSphere MQ
Note:- At the time of release, T1265H01^ABJ is a restricted SPR, so you may
need to contact HP to obtain it.

For both hardware platforms, we recommend that you install the latest
available versions of HP OSS sockets and Transport Agent (products T8306,
T8994 and T8397).

If you use SNA channels with V5.3.1, we recommend the latest levels of the
HP SNAX or ACI Communication Services for Advanced Networking (ICE) be used
for the SNA transport. The following versions were verified by IBM with this
release of WMQ:

ACI Communication Services for Advanced Networking (ICE)
- v4r1 on both HP Integrity NonStop Server and S-Series systems

HP SNAX
- T9096H01 on HP Integrity NonStop Server (H-Series) systems
- T9096ADK on HP NonStop Server (G-Series) systems

If you use the WebSphere MQ V5.3 classes for Java and JMS for HP NonStop Server
you will need to install HP NonStop Server for Java Version 1.4.2 or later.


Upgrading from V5.3.0 to V5.3.1
-------------------------------

You may upgrade any service level of WebSphere MQ V5.3.0 for HP NonStop Server
to V5.3.1 level using this release. The installation tool, instmqm, will
upgrade existing installations to this level if necessary. Alternatively,
instmqm can be used to create new installations at the V5.3.1 level.

You must end all queue managers in an installation if you want to upgrade
that installation to V5.3.1.

You do not need to re-create any queue managers to upgrade to V5.3.1. Existing
V5.3.0 queue managers (at any service level) will work with V5.3.1 once an
installation has been properly upgraded.

You do not need to re-compile any applications to upgrade to V5.3.1.

If your non-native applications use a static linkage method for binding with
the MQI, you must use the HP BIND utility to re-link these applications for
use with V5.3.1.

If your applications bind to the MQI using the Shared Resource Library (SRL)
method, you may need to ensure that the User Library references in the
application programs are updated to refer to new libraries from V5.3.1 using
the HP nld utility. This step is only required if you have created a new
V5.3.1 installation and want to use the same copies of application programs
with it as were running previously with V5.3.0. If you upgrade an existing
V5.3.0 installation, the updated libraries will be in the same location and
so this step is not required.


Installation from Electronic Software Download
----------------------------------------------

These instructions apply to installing WebSphere MQ for HP NonStop Server,
Version 5.3.1 from an installation image downloaded from IBM.
Use it with the WebSphere MQ for HP NonStop Server Quick Beginnings book
for this release. A version of the WebSphere MQ for HP NonStop Server
Quick Beginnings book is available from the download site; it has a
description of 'WebSphere MQ for HP NonStop Server Quick Beginnings'
with order number GC34-6626-00. The installation image is provided as a
compressed (zip) file.

1. Locate the correct image for the hardware platform (HP NonStop Server
for G-Series and HP Integrity NonStop Server for H-Series) on the
download site.

2. Download the image to a computer running Microsoft(R) Windows(R).
Ensure that the method of downloading the image preserves all the data
in the image. For example, use the ftp transfer mode of "binary".

3. Use the standard features of the Microsoft Windows Explorer (or any
file compression utility that understands the .zip file format) to
extract all the files from the compressed image file to a new folder in
a convenient location on your workstation.

4. Double-click on the Setup.exe program in the root directory of the
extracted files to launch the HP IPSetup program and follow the
guidelines in the WebSphere MQ for HP NonStop Server Quick Beginnings
book to transfer the product files to your HP NonStop Server or HP
Integrity NonStop Server System, and then create and verify an
installation (see below).

Installation from CD-ROM
------------------------

Insert the CD-ROM for the platform you are installing on in the CD-ROM drive
of your Microsoft Windows workstation. The Setup application should launch
automatically. If this does not happen within a few minutes, open the root
directory of the CD-ROM and double-click on the Setup.exe application to
launch the HP IPSetup installation program. Follow the guidelines in the
WebSphere MQ for HP NonStop Server Quick Beginnings book to transfer the
product files to your HP NonStop Server or HP Integrity NonStop Server
System, and then create and verify an installation (see below).

Create and verify an installation
---------------------------------

Once you have placed the files on your NonStop Server system (follow the same
instructions as for V5.3.0.0) you can create an installation from these
placed files.

The installation method is described in the WebSphere MQ for HP NonStop
Server Quick Beginnings book, however there are some changes for V5.3.1
which are described here. Please read and understand all of these changes
before attempting to create an installation of V5.3.1.

1. Instmqm will upgrade an existing V5.3.0.0 installation to V5.3.1.0 level

Instmqm will create a complete V5.3.1.0 installation from scratch in a new
location, or it can upgrade an existing V5.3.0.0 installation (at any
service level) to the V5.3.1.0 level. Instmqm will detect the presence of
an existing installation in a location you supply, verify that the level of
the existing installation is suitable for upgrading, and ask for
confirmation that you want to upgrade the installation. When you confirm
that you want to upgrade the installation, instmqm will modify files in the
OSS opt tree and the three Guardian installation subvolumes to bring the
installation up to the V5.3.1.0 level. Existing queue managers will be
able to run using V5.3.1.0 without modification. All queue managers must
be ended before beginning the upgrade installation.

2. During an upgrade of a V5.3.0.0 installation, if an error occurs after
changes have been made, instmqm provides the option to restore the previous
installation from an archive it created before the changes were made

When you confirm that you want to upgrade an existing installation, before
any changes are made to the system, an archive is created of the existing
installation. The archive contains only directories and files in the OSS
opt tree, and the three Guardian subvolumes for the installation. No data
in the OSS var tree or queue manager's Guardian subvolumes are archived.

If an error occurs after changes are made, there is a danger that the
installation could be left in an inconsistent and/or inoperable state.
Instmqm will restore the installation to it's previous state by
restoring the backup archive that it created before changes were made.
Confirmation is required from the user before the backup archive is
restored.

3. Instmqm now automatically archives a successful installation

Upon successful completion of an installation (from scratch or upgrade)
instmqm will automatically create a backup archive of the installation.

4. Instmqm provides archive and restore function independent of installation

Instmqm can be used to create or restore a backup archive using the
new command line options -x and -b independently of installing or upgrading
an installation. Instmqm prompts the user to supply the name of the backup
archive file and the installation location in both cases.


UNINSTALLATION INFORMATION
==========================

In addition to the procedure documented in the WebSphere MQ for HP NonStop
Server Quick Beginnings book, please note that instmqm for V5.3.1.0 now
includes the ability to reverse an upgrade of an installation that has
failed.


KNOWN LIMITATIONS, PROBLEMS AND WORKAROUNDS
===========================================

This section details known limitation, problems, and workarounds for
WebSphere MQ for HP NonStop Server, Version 5.3.1.

Limitations
-----------

1. The current implementation of Publish / Subscribe is restricted to run
within a single CPU. The control program and all "worker" programs run in
the same CPU.

2. The current memory management implementation in the Queue Server limits
the total amount of non-persistent message data that can be stored on all
the queues hosted by a single Queue Server to less than 1Gb. The limit of
non-persistent message data on a single queue can not exceed approximately
1Gb therefore, even if a single Queue Server is dedicated to that queue.

3. The number of threads in threaded agent processes (LQMAs or MCAs) or in MQI
applications, is limited to a maximum of 1000 by the limit on open depth of
the HP TMF T-file.

4. API exits are not supported for non-native (TNS) applications. Any exit
code for non-native applications must be statically bound with the
application.

5. Cluster workload exits are only supported in "trusted" mode. This means
that a separate copy of each exit will run in each CPU and exit code in
one CPU cannot communicate with exit code in another CPU using the normal
methods provided for these exits.

6. Upgmqm will not migrate the following data from a V5.1 queue manager:

- messages stored in Message Overflow files (typically persistent messages
over 200,000 bytes in size) will not be migrated. If the option to
migrate message data was selected, the upgrade will fail. if the option
to migrate message data was not selected, the upgrade will not be
affected by the presence of message overflow files.
- clustering configuration data - all cluster related attributes of objects
will be reset to default values in the new V5.3 queue manager.
- SNA channel configuration - channels will be migrated, but several of the
attributes values will need to be changed manually after the upgrade.
- channel exit data - attributes in channels that relate to channel exit
configuration will be reset to default values in the new V5.3 queue
manager.

In all cases where upgmqm cannot migrate data completely, a warning message
is generated on the terminal output as well as in the log file. These can
be reviewed carefully after the upgrade completes for further actions that
may be necessary.

7. Java and JMS limitations

The Java and JMS Classes do not support client connections. WebSphere MQ
for HP NonStop Server does not support XA transaction management, so the
JMS XA classes are not available. For more detail, please refer to the
Java and JMS documentation supplement, Java.pdf.


Known problems and workarounds
------------------------------

1. Some SSL ciphers don't work with WebSphere MQ for Windows

The following three ciphers do not work between WebSphere MQ for HP NonStop
Server V5.3.1 and WebSphere MQ for Windows V5.3:

DES_SHA_EXPORT
RC2_MD5_EXPORT
TRIPLE_DES_SHA_US

The workaround is to use a different cipher for secure communication
between these two platforms.

2. APAR IC51627 - the default qmproc.ini causes incorrect behavior when used
on a 16 CPU system

The default qmproc.ini file does not contain a list of CPUs for the EC to
use in distributing MCAs and LQMAs across the available CPUs. This default
means that the EC should use all CPUs for work for this queue manager. On
a 16 CPU system, because the EC interprets this default incorrectly, the
EC creates all MCAs and LQMAs in the same CPU - the CPU in which the
primary EC is running. On systems that have less than 16 CPUs, the default
is interpreted and used correctly.

A second and related problem also exists. If a CPU list is configured in
qmproc.ini and contains CPU 15, the EC will loop after the queue manager is
started, and the queue manager will be unusable.

The workaround (only required on systems with 16 CPUs) is:
- do not use the default qmproc.ini
- specify a CPU list in the AllProcesses stanza that includes any or all
CPUs other than CPU 15

For example, adding the following lines to proc.ini and any existing
qmproc.ini files for your installation:

AllProcesses:
CPUs=0,1,2,3,4,5,6,7,8,9,10,11,12,13,14

will ensure that this problem is not experienced and the intended default
is used by the EC, with the exception that CPU 15 cannot be used.

3. If channels are running when a queue manager is ended, unnecessary FDCs can
be generated, referencing function rriChannelTerminate() with
Probe ID: RM487001 and messages in the queue manager log file that report
a communications error

These symptoms are harmless, but can cause confusion and unnecessary
difficulty in problem diagnosis. The cause is under investigation.

To work around this problem, add the PARAM MQCHL_NO_TERM_FFST to the
Channel Server Pathway SERVERCLASS definition. For example, the command:
alter mqs-channelsvr, param MQCHL_NO_TERM_FFST
can be used in PATHCOM to change the definition. Review and follow the
procedures documented in the System Administration Guide for configuring
Pathway attributes of WMQ servers.

The log messages you see when this occurs will be similar to:

01/23/07 12:27:36
AMQ9213: A communications error for accept occurred.

EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the accept
(/home/user/wmq/var/mqm/tmp/MQSeries.285868255) call was 4009 (X'FA9').
Record these values and tell the systems administrator.

01/23/07 12:27:42
AMQ9604: Channel 'QM1.SDR.QM2' terminated unexpectedly

EXPLANATION:
The process or thread executing channel 'QM1.SDR.QM2' is no longer
running. The check process system call returned 545284357 for process
167969655.
ACTION:
No immediate action is required because the channel entry has been
removed from the list of running channels. Inform the system
administrator who should examine the operating system procedures to
determine why the channel processhas terminated.

It is not possible to supress these log messages.

4. Control commands in Guardian (TACL) environment don't obey all RUN options

In this release, the Guardian environment versions of the control commands
will correctly process most of the RUN options, but there are some known
exceptions to this:

- A Virtual Hometerm Services (VHS) server cannot be specified for the
IN, OUT and HOMETERM options
- the INV and OUTV options do not work
- the NAME option does not work as expected, since although the Guardian
program is named as requested by the NAME option, the OSS process that
runs the actual control program from OSS cannot be started with the
same process name

The workaround for the IN, OUT and HOMETERM options is to use either a disk
file, or a terminal device. There is no workaround for the INV, OUTV or
NAME option behavior.



DOCUMENTATION UPDATES
=====================

WebSphere MQ for HP NonStop Server Quick Beginnings (GC34-6626-00)
------------------------------------------------------------------

Chapter 1 - Planning to install WebSphere MQ for HP NonStop Server

- Page 1: the baseline release level for V5.3.1 on the HP Integrity NonStop
Server is now H06.05.01
- Pages 2 & 3: please review the section "Hardware and Software
Requirements" in these release notes for the details of all other updated
requirements

Chapter 3 - Installing WebSphere MQ for HP NonStop Server

- Page 12: Product Selection dialog. The names of the products have been
updated to "WebSphere MQ V5.3.1" and "WebSphere MQ V5.3.1 Integrity".
- Page 14: instmqm now includes the function of creating an automatic
backup archive of a successful installation. Please review the
description of this function in these release notes
- Page 15: instmqm has new command line options as described in these
release notes for creating and restoring backup archives
- Page 28: in addition to the manual methods for cleaning up after a failed
installation, instmqm will offer the option to restore the previous
installation from a backup archive in the event of a failure while
upgrading a V5.3 installation to V5.3.1 level. These release notes
describe the additional function.

Chapter 5 - Creating a Version 5.3 queue manager from an existing Version 5.1
queue manager

- Pages 37 & 38: this section is completely replaced by the documentation
supplement Upgmqmreadme.pdf supplied with this release.

Chapter 7 - Applying maintenance to WebSphere MQ for HP NonStop Server

- Pages 44 & 45: the tool for applying maintenance is named "svcmqm" and
not "installCSDxx".
- Page 44: in step 3 of "Transferring and preparing the PTF for
installation", the top level directory of the PTF is opt, and is not
named differently for each PTF. Therefore it is important to manually
create a directory specific to each PTF, download the PTF to that new
directory and then expand the archive within the new directory.
- Page 44: in step 2 of "Running the installation script for a PTF", the
svcmqm tool has a different command line from that documented for
"installCSDxx". svcmqm takes two parameters:
svcmqm [-i installationtree] -s servicepackage

where "installationtree" is the full path to the location of the opt/mqm
directory of the installation to be updated
"servicepackage" is the full path to the location of the opt/mqm
directory of the maintenance to be installed
For example:
svcmqm -i /home/me/wmq/opt/mqm -s /home/me/wmqfiles/opt/mqm
which will update the installation in /home/me/wmq/opt/mqm from the
maintenance package in directory tree /home/me/wmqfiles/opt/mqm.

If the "-i installationtree" parameter is omitted, svcmqm will use the
current setting of the environment variable WMQNSKOPTPATH.


WebSphere MQ for HP NonStop Server System Administration Guide (SC34-6625-00)
-----------------------------------------------------------------------------

Chapter 4 - Administering local WebSphere MQ objects

- Page 48: when creating a Process definition, the default value for
the APPLTYPE attribute is "NSK" (indicating a Guardian program)

Chapter 9 - Configuring WebSphere MQ

- Page 130: the MQSC command to reload the process management rules is
REFRESH QMGR TYPE(NSPROC) and not RESET QMGR TYPE(NSPROC)

Chapter 14 - Process Management

- Page 197: the MQSC command to reload the process management rules is
REFRESH QMGR TYPE(NSPROC) and not RESET QMGR TYPE(NSPROC)
- Page 200 and 204: the default value for the maximum number of unthreaded
agents is now 200. The default value for the maximum number of threaded
agents is now 20. the default value for the maximum re-use count for
threaded agents is now 100.

Chapter 19 - The control commands

- Page 243: the control commands for the Publish / Subscribe broker are
not referenced here. Refer to the WebSphere MQ V6.0 Publish/Subscribe
User Guide and the documentation supplement for Publish/Subscribe on
HP NonStop Server - Pubsub.pdf.
- Page 255: if the OSS environment variable or Guardian PARAM MQPATHSEC
is defined and set to one of the standard NonStop OS security attributes
(A, N, C, G, O, or U) when crtmqm is run, the default PATHWAY SECURITY
atribute value of "N" will be overriden by the value of the environment
variable / PARAM. This can be used to restrict access to the queue
manager's Pathway environment. The current Pathway attributes can be
displayed in PATHCOM using the INFO PATHWAY command.

Chapter 23 - API exits

- Pages 373-375: please review the updates to this section in the
documentation supplement for API exits for HP NonStop Server called
Exits.pdf

Appendix B - Directory structure

- Pages 430 and 431: there is a new G symbolic link to the Guardian
subvolume containing the product executables in
.../var/mqm/qmgrs/@SYSTEM

Appendix F - Environment variables

- Page 446: there are two environment variables that are used by the
Guardian sample build scripts to locate the header files and the
libraries. These are MQV53INCSC and MQV53LIBSV respectively.

Appendix J - User exits

- refer to the documentation supplement Exits.pdf for updated information
about configuring and building user exits
- the -export_all option is required for building exits.
The c89 examples require the ld option '-export_all'

e.g., c89 –Wshared –WIEEE_float –Wsystype=oss –IMQNSKOPTPATH/inc
-Wld=”-e MQStart -export_all” –LMQNSKOPTPATH/lib –lmqm
exit.c –o exitname


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-1.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 "Submit your problem" to IBM Software Support, ensure
that your company has an active IBM software maintenance contract, and
that you are authorized to submit problems to IBM. The type of software
maintenance contract that you need depends on the type of product you
have:

For IBM distributed software products (including, but not limited to,
Tivoli(R), Lotus(R), and Rational(R) products, as well as DB2(R) and
WebSphere products that run on Windows or UNIX(R) operating systems),
enroll in Passport Advantage(R) in one of the following ways:
Online: Go to the Passport Advantage Web site at
http://www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Home,
and click "How to Enroll".
By phone: For the phone number to call in your country, 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 customers with Subscription and Support (S & S) contracts, go to the
Software Service Request Web site at
https://techsupport.services.ibm.com/ssr/ssr.slprob.
For customers with IBMLink(TM), CATIA, Linux(R), S/390(R), iSeries(TM),
pSeries(R), zSeries(R), and other support agreements, go to the IBM Support
Line Web site at
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.
For IBM eServer(TM)) software products (including, but not limited to,
DB2(R) 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. "Determine the business impact of your problem"
2. "Describe your problem and gather background information"
3. "Submit your problem"

Determine the business impact of your problem

When you report a problem to IBM, you are asked to supply a severity
level. Therefore, you need to understand and assess the business impact
of the problem that you are reporting. Use the following criteria:


+---------------------------------+----------------------------------+
| Severity 1 | The problem has a critical |
| | business impact: You are unable |
| | to use the program, resulting in |
| | a critical impact on operations. |
| | This condition requires an |
| | immediate solution. |
+---------------------------------+----------------------------------+
| Severity 2 | This problem has a significant |
| | business impact: The program is |
| | usable, but it is severely |
| | limited. |
+---------------------------------+----------------------------------+
| Severity 3 | The problem has some business |
| | impact: The program is usable, |
| | but less significant features |
| | (not critical to operations) are |
| | unavailable. |
+---------------------------------+----------------------------------+
| Severity 4 | The problem has minimal business |
| | impact: The problem causes |
| | little impact on operations, or |
| | a reasonable circumvention to |
| | the problem was implemented. |
+---------------------------------+----------------------------------+

Describe your problem and gather background information

When describing a problem to IBM, be as specific as possible. Include
all relevant background information so that IBM Software Support
specialists can help you solve the problem efficiently. See the
MustGather Web page
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg21229861 for
details of the documentation required. To save time, know the answers to
these questions:

What software versions were you running when the problem occurred?
Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
Can you re-create the problem? If so, what steps do you perform to
re-create the problem? Did you make any changes to the system? For example,
did you make changes to the hardware, operating system, networking software,
or other system components? Are you currently using a workaround for the
problem? If so, please be prepared to describe the workaround when you
report the problem.

Submit your problem

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

Online: Go to the Submit and track problems tab on the IBM Software Support
site at http://www.ibm.com/software/support/probsub.html. Type your
information into the appropriate problem submission tool.
By phone: For the phone number to call in your country, 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.

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.


NOTICES AND TRADEMARKS
======================

IBM may not offer the products, services, or features discussed in this
document in all countries. Consult your local IBM representative for
information on the products and services currently available in your
area. Any reference to an IBM product, program, or service is not
intended to state or imply that only that IBM product, program, or
service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate
and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document does
not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact
the IBM Intellectual Property Department in your country/region or send
inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any
other country/region where such provisions are inconsistent with local
law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in
certain transactions; therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of
those Web sites. The materials at those Web sites are not part of the
materials for this IBM product, and use of those Web sites is at your
own risk.

IBM may use or distribute any of the information you supply in any way
it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one)
and (ii) the mutual use of the information that has been exchanged,
should contact:
IBM Canada Limited
Office of the Lab Director
8200 Warden Avenue
Markham, Ontario
L6G 1C7
CANADA

Such information may be available, subject to appropriate terms and
conditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed
material available for it are provided by IBM under terms of the IBM
Customer Agreement, IBM International Program License Agreement, or any
equivalent agreement between us.

Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating
environments may vary significantly. Some measurements may have been
made on development-level systems, and there is no guarantee that these
measurements will be the same on generally available systems.
Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should
verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers
of those products, their published announcements, or other publicly
available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility, or any other claims related
to non-IBM products. Questions on the capabilities of non-IBM products
should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to
change or withdrawal without notice, and represent goals and objectives
only.

This information may contain examples of data and reports used in daily
business operations. To illustrate them as completely as possible, the
examples include the names of individuals, companies, brands, and
products. All of these names are fictitious, and any similarity to the
names and addresses used by an actual business enterprise is entirely
coincidental.

This information may contain sample application programs, in source
language, which illustrate programming techniques on various operating
platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM for the purposes of developing, using,
marketing, or distributing application programs conforming to the
application programming interface for the operating platform for which
the sample programs are written. These examples have not been thoroughly
tested under all conditions. IBM, therefore, cannot guarantee or imply
reliability, serviceability, or function of these programs.


Trademarks

The following terms are trademarks of International Business
Machines Corporation in the United States, other countries,
or both: DB2, eServer, IBM IBMLink, iSeries, Lotus, MQSeries, pSeries,
Passport Advantage, Rational, s/390, SupportPac, Tivoli, WebSphere, zSeries.

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

Microsoft Windows is a trademark or registered trademark of Microsoft
Corporation in the United States, other countries, or both.

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

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

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