Readme for IBM WebSphere MQ for HP NonStop Server, Version 5.3.1, Fix Pack 4

Content

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

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


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, Fix Pack 4.

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/products/en/ibm-mq

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/support/entry/portal/Software/WebSphere/WebSphere_MQ


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

Nomenclature
------------
The terms "WMQ V5.3.1" and "WMQ V5.3.1.0" both refer to the same WMQ Refresh
Pack without subsequent service installed. Throughout this readme, references
to "WMQ V5.3.1.x" refer to WMQ 5.3.1 with or without subsequent service
installed.

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

This is the fourth FixPack for IBM WebSphere MQ V5.3.1 for HP NonStop Server,
and is designated V5.3.1.4, PTF IP22981, with associated APAR IC57894.

This fix pack introduces support for the HP Integrity NonStop BladeSystem
platform, NB50000c. Use the H-Series (Integrity) package of WebSphere MQ
for execution on the BladeSystem. Please refer to the Hardware and Software
Requirements section for details about the levels of the J-Series software
required.

No new function is released with V5.3.1.4. This release contains fixes
only, and is cumulative for all service and internal defect correction
performed since WMQ 5.3.1 was released.

Some changes have been made to the recommended levels of HP NonStop system
software. The new recommended levels (SPRs) are NOT REQUIRED by any of the
fixes made in V5.3.1.4, but reflect releases made by HP fixing problems
discovered in environments that run WebSphere MQ which could impact your
operations. IBM have successfully tested with these levels of
HP NonStop system software.

All object and executable files distributed with this fixpack have the
following version procedure strings:

T0085G06_29SEP2008_V53_1_4 (for G-Series systems)
T0085H06_29SEP2008_V53_1_4 (for H-Series systems)

Important note about SSL channels for when upgrading from V5.3.1
----------------------------------------------------------------
The following SSL information applies if you are upgrading from
WMQ V5.3.1 and are using SSL channels. The following procedure is
not required if you have already installed WMQ V5.3.1.1

Several of the fixes in this fixpack that relate to SSL channels, change to the
way that SSL certificates are configured with WebSphere MQ. If you use
SSL channels you will need to review the new documentation supplement
SSLupdate.pdf for information about this change and make configuration changes
to the certificate store after installing V5.3.1.4, but before running
channels. Please also see the Post-installation section below for a
summary of the required changes.

Important note about instmqm for V5.3.1
---------------------------------------

A modified WebSphere MQ product installation script, instmqm, for any level of
V5.3.1, is provided with V5.3.1.4 that includes a workaround for the OS problem
introduced in G06.29/H06.06 where the OSS 'cp' command creates Guardian files
in Format-2 form during an installation rather than Format-1. This change
caused problems binding and compiling non-native and native COBOL applications,
as well as wasting a lot of disk space because of the very large default
extents settings for the Format-2 files created by OSS cp.

Instmqm has been modified to work around this change in OSS cp by forcing
all Guardian files in an installation to be created as Format-1. The use of
the new installation script is recommended for all new V5.3.1 installations.

Existing installations that are not affected by the application relink or
rebind problems can remain as they are.

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

The following APAR fixes are released in V5.3.1.4:

APAR IC57020 - runmqtrm does not function correctly and produces errors in some
cases.
When a triggered application is a guardian script file
(ie filecode 101). runmqtrm produces an "illegal program
file format" error. Triggering also does not work correctly
for COBOL or TAL applications.
APAR IC57231 - The execution controller starts repository processes at the
same priority as itself in some cases, and does not take
account of the values set in the qmproc.ini file.
APAR IC57420 - Repository manager restart following failure causes cluster
cache corruption in some circumstances.
If a repository manager abends while a queue manager is under a
heavy load of cluster-intensive operations, in some
circumstances the repository manager that is restarted can
damage the cluster cache in the CPU in which it
is running. This can prevent further cluster operations in that
CPU and cause WMQ processes to loop indefinitely. This release
changes the repository startup to prevent this from happening.
APAR IC57432 - OSS applications that attempt to perform MQI operations from
forked processes encounter errors.
If an oss WMQ application forks a child process, that child
process will encounter errors if it attempts to perform MQI
operations. Some operations may succeed, but will result
in the generation of FDC files.
APAR IC57488 - MQMC channel menu display display error after channel is
deleted.
If a channel is deleted while the channel menu in MQMC
is displayed, refreshing the channel menu produces the
error: "Unknown error received from server. Error number
returned is 1" and will not correctly display the channel
list without restarting MQMC.
APAR IC57501 - unthreaded sender channels to remote destinations with
significant network latency may fail to start with timeout
errors.
APAR IC57524 - Applications launched locally from remote nodes cannot access
some of the queue manager shared memory files due to default
security on those files.
APAR IC57627 - Handling of TMF outages to improve operational predictability.
If TMF disables the ability to begin new transactions
(BEGINTRANS DISABLED), WMQ does not always react in a
predictable or easily diagnosed manner, and applications can
suffer a variety of different symptoms. If TMF is stopped
abruptly (STOP TMF, ABRUPT) queue managers can become unstable
and require significant manual intervention to stop and restart.
Refer to item 18 in "Known Limitations, Problems and
Workarounds" later in this README for more information.
APAR IC57712 - altmqfls --qsize with more than 100 messages on queue fails.
When a altmqfls --qsize is performed with more the 100 MQ
messages in the queue the processing fails.
APAR IC57719 - FDC's from MQOPEN when an error exists in alias queue manager
resolution path. If a queue resolution path includes a queue
manager alias, and the target of the alias does not exist,
this will produce an FDC, rather than just failing the
MQOPEN as would be expected.
APAR IC57744 - CPU goes busy when stopping a threaded SSL receiver channel
using MODE(TERMINATE).
If a stop channel mode(terminate) is used to stop an SSL
receiver channel that is running in a threaded MCA, the CPU
where the MCA is running in begin using large amounts of CPU
time (95% range). This is due to a problem in the threads
library.
APAR IC57876 - Very infrequently, messages put via threaded LQMAs can in some
circumstances contain erroneous CCSID information. This has
been observed to cause conversion errors if the message is
destined for a channel that has the CONVERT(YES) set.
Unthreaded LQMAs do not suffer from this problem.

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

993 - Due to the way that default file security was used, file security for
certain shared memory files used by the queue manager (SZ***) may
inadvertently change in a way that prevents applications not in
the mqm group from issuing MQCONN. File permissions were rationalised
in this release to reflect those used for other shared memory files.
1458 - Resolve Channel command generates FFST's.
When resolving In-Doubt channels, FFST's were generated by the Channel
Server and the MCA. Although the channels were successfully resolved,
the In-Doubt status in a DIS CHS(*) query was not correctly updated.
When resolving In-Doubt channels using the COMMIT option the following
error message was displayed "AMQ8101: WebSphere MQ error (7E0) has
occurred."
1493 - The validation of the qmproc.ini file does not report the error case
where multiple ChannelsNameMatch entries are specified ChlRule1.
1498 - Instmqm does not support installation of the product on
Integrity NonStop BladeSystem platforms.
1507 - Some Execution controller messages were missing "Action" descriptions
when reported in the error log.
1517 - In the qmproc.ini file, the AppRule4-SubvolMatch argument was not
working
1522 - Communications Component Function ids and probes are incorrect. This
resulted in misleading or missing information in trace files generated
for support purposes.
1546 - MQBACK operation incorrectly reports error during broker operations
1549 - Channel Server doesn't shutdown after takeover.
If the Primary Channel Server process is prematurely ended, for
example by a CPU crash, the Backup Channel Server process becomes the
new Primary process. Subsequent attempts to use endmqm will hang
because the new Primary Channel Server process will not end.

The following documentation APARs are addressed by the V5.3.1.4 readme:

APAR IC55404 - REFRESH QMGR PCF command is not documented in the Programmable
command formats manual.

Also - please check the "Limitations" and "Known Problems and Workarounds"
sections later on in this readme for updates.

The following APAR fixes were released in V5.3.1.3:

APAR IC54305 - The HP TNS (non-native) C compiler generates Warning 86 when
compiling MQI applications
APAR IC55501 - The altmqfls command does not return the correct completion
status; it always returns success
APAR IC55719 - Non-native MQINQ binding does not deal with some null pointer
parameters correctly
APAR IC55977 - Channel retry does not obey SHORTTMR interval accurately enough
APAR IC55990 - Trigger data changes not being acted upon if they were made
while the queue was open, leading to incorrect triggering
behavior
APAR IC56277 - Command Server can loop with INQUIRE QS command with a single
parameter
APAR IC56278 - A remote RUNMQSC DIS QS (*) command always times out
APAR IC56309 - MCAs do not disconnect from some shared memory when ending,
which causes a slow memory leak, and under some conditions an
abend
APAR IC56458 - Channel Server loops after installing V5.3.1.2 due to corrupt
data on SYSTEM.CHANNEL.SYNCQ
APAR IC56493 - Cannot use "qualified" hometerm device names with V5.3.1.2
APAR IC56503 - Channel Server and MCA can deadlock after repeated STOP CHANNEL
MODE(FORCE) or MODE(TERMINATE) commands
APAR IC56536 - Unthreaded responder channels don't de-register from the EC when
an error occurs during or before channel negotiation. For
example, bad initial data will cause this. Unthreaded MCAs
build up and eventually reach the maximum which prevents further
channel starts
APAR IC56681 - C++ unthreaded Tandem-Float SRLs have undefined references
APAR IC56834 - endmqm -p can sometimes leave MCA processes running

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

663 - Guardian command line utility return status is not the same as the OSS
utilities return status
1402 - Add additional tracing when testing for inconsistencies in processing
a channel start in the Channel Server
1416 - Ensure that the Channel Server can support the maximum BATCHSZ of 2000
1446 - Pub / Sub command line utilities do not behave well if no broker has run
since the queue manager was created
1470 - EC abends attempting to start a non-executable REPMAN
1474 - Pub / Sub broker process handling corrections for the EC
1476 - The EC checkpoints the number of threads running in agents incorrectly
1477 - Enhancement to ecasvc utility: the creation date/time of LQMAs, MCAs,
and REPMEN are now displayed
1487 - Enhancement to ecasvc utility: changed the display of Agent attributes
to use the "real" qmproc.ini attribute names. Added a new option,
that displays information about all connected applications
1494 - A small memory leak occurs for the delete channel operation
1508 - Multiple qmproc.ini environment variables don't get propagated to
agents or repmen
1509 - The EC failed to stop an MCA that was hung when a preemptive shutdown
was initiated

The following documentation APARs were addressed by the V5.3.1.3 readme:

APAR IC55380 - Transport provider supplied during install is not propagated to
Pathway configuration by crtmqm. Please see the documentation
update below made for Page 17 of the "Quick Beginnings" book.

The following APAR fixes were released in V5.3.1.2:

APAR IC52123 - LQMA abend handling rollback of a TMF transaction in MQSET
APAR IC52963 - The PATHMON process is not using configured home terminal for
MQV5.3 on HP Nonstop Server
APAR IC53205 - FDC from Pathway runmqlsr when STOP MQS-TCPLIS00
APAR IC53891 - There is a memory leak in the Channel Server when processing
the DIS CHS command
APAR IC53996 - C++ PIC Guardian DLLs missing.
APAR IC54027 - MQRC_CONTEXT_HANDLE_ERROR RC2097 when loading messages using
MO71
APAR IC54133 - Multi-threaded LQMA should not try to execute Unthreaded
functions if qmproc.ini LQMA stanza sets MaximumThreads=1
APAR IC54195 - runmqtrm data for Trigger of Guardian application not
reinitialized
APAR IC54266 - MinThreadedAgents greater than PreferedThreadedAgents causes
MQRC 2009 error
APAR IC54488 - MCA's abend after MQCONN/MQDISC 64 times.
APAR IC54512 - OSS runmqsc loops if Guardian runmqsc is TACL stopped
APAR IC54517 - upgmqm does not handle CPUs attribute for PROCESS specifiction
in a SERVERCLASS
APAR IC54583 - SSL channel agent can loop if an SSL write results in a socket
I/O error
APAR IC54594 - EC abends with non-MQM user running application from non-MQM
directory
APAR IC54657 - Channel stuck in BINDING state following failed channel start
due to unsupported CCSID.
APAR IC54666 - Queue Server deadlock in presence of system aborted
transactions.
APAR IC54798 - upgmqm fails with Pathway error on 3 or more status servers that
require migration from V5.1 queue manager.
APAR IC54841 - When a temporary dynamic queue is open during "endmqm -i"
processing an FDC is generated
APAR IC55008 - Added processing that will cause Channel Sync data to be
Hardened at Batch End
APAR IC55073 - altmqfls --qsoptions NONE is not working as specified
APAR IC55176 - Abend in MQCONN from app that is not authorized to connect (2035)
or with invalid Guardian Subvolume file permissions
APAR IC55500 - QS Deadlock with Subtype 30 application using MQGMO_SET_SIGNAL
APAR IC55726 - Channel stuck in BINDING state following failed channel start
due to older FAP level
APAR IC55865 - Abend on file-system error writing to EMS collector

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

1122 - Invalid/incomplete FFST generated during MQCONN when Guardian
subvolume cannot be written to.
1392 - Add support for Danish CCSID 65024
1397 - Command Server fails to start and EC reports failure to initialize
a CPU - error 12 purging shared memory files.
1409 - Guardian WMQ command fails when invoked using Guardian system() API
1413 - MCA looping after SSL socket operation fails
1419 - altmqfls --volume attempted using a open object causes FDCs
1439 - On non-retryable channel, runmqsc abends while executing RESOLVE CHANNEL
command

The following documentation APARs were addressed by V5.3.1.2:

APAR IC53996 - C++ PIC Guardian DLLs missing.


originally released in V5.3.1.1 Patch 1:
APAR IC53891 - There is a memory leak in the Channel Server when
processing the DIS CHS command

originally released in V5.3.1.1 Patch 2:
APAR IC54583 - SSL channel agent loops

originally released in V5.3.1.1 Patch 3:
APAR IC54666 - Queue Server deadlock in presence of system aborted
transactions.

originally released in V5.3.1.1 Patch 4:
APAR IC54512 - OSS runmqsc loops if Guardian runmqsc is TACL stopped

The following APAR fixes were released in V5.3.1.1:

APAR IC52737 - When in SSL server mode and the sender is on zOS a list of CAs
that the server will accept must be sent to the zOS sender
during the SSL handshake
APAR IC52789 - upgmqm support for upgrading V5.1 queue managers that do not use
OAM (created with MQSNOAUT defined). Also add diagnostics as to
reasons and preventative actions for failure to create a PATHMON
process
APAR IC52919 - Problems in synchronization of starting a queue manager when
multiple Queue Servers are defined
APAR IC52942 - Trigger Monitor holds Dead Letter Queue open all the time
APAR IC53240 - Correct sample API exit to build for PIC and SRL/Static
APAR IC53243 - Start of many applications simultaneously causes LQMA FDC
APAR IC53248 - Kernel not informing repository cache manager of updates to
cluster object attributes
APAR IC53250 - Flood of FDCs when trace is enabled before qmgr start
APAR IC53254 - Browse cursor mis-management left locked message on queue.
In addition, browse cursor management was not correct in the
event that a syncpoint MQGET rolls back
APAR IC53288 - Cluster Sender channel is not ending until the HBINT expired
APAR IC53383 - upgmqm was losing the MCAUSER attribute on channels
APAR IC53492 - TNS applications fail in MQPUT with more than 106920 bytes of
data
APAR IC53524 - SVRCONN channels are not ending after STOP CHANNEL if client
application is in a waited MQGET
APAR IC53552 - OAM uses getgrent() unnecessarily, causing slow queue manager
startup
APAR IC53652 - Guardian administration commands don't work with VHS or other
processes as standard input or output streams
APAR IC53728 - ECONNRESET error when Primary TCP/IP process switched should
not cause listener to end
APAR IC53835 - Assert in xtrInitialize trying to access trace shared memory

The following documentation APARs were addressed by V5.3.1.1:

APAR IC51425 - Improve documentation of crtmqm options
APAR IC52602 - Document ClientIdle option
APAR IC52886 - Document RDF setup ALLSYMLINKS
APAR IC53341 - Document OpenTMF RMOPENPERCPU / BRANCHESPERRM calculation

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

634 - Correct function of altmqfls option to reset measure counter
822 - Message segmentation with attempted rollback operation failed
862 - PCF command for Start Listener fails
903 - Channel status update problems during shutdown after Repman has ended
922 - Channel status incorrect when attempting to start a channel and the
process management rules prevent the MCA thread or process from starting
929 - Incorrect response records when putting to distribution list
1012 - Two of the sample cobol programs give compilation error
1059 - C-language samples use _TANDEM_SOURCE rather than __TANDEM
1064 - errors checkpointing large syncpoint MQPUT and MQGET operations
when transactions abort
1069 - Not able to delete CLNTCONN channels
1108 - Error logged when MCA exits because maximum reuse count is reached
1152 - strmqm -c option gives unexpected error if executed after strmqm
1176 - Sample cluster workload exit not functioning correctly
1177 - QS backup abend on takeover with local TMF transactions
1180 - Segmentation of messages on transmission queues by the queue manager
was incorrect.
1182 - Replace fault tolerant process pair FDCs with log messages for better
operator information when a takeover occurs
1185 - Opens left in all three NonStop Server processes after divering CPUs
1208 - Trace info is incorrect for zslHPNSS functions. FFSTs show incorrect
component and incorrect stack trace info
1210 - FFSTs generated by criAccessStatusEntry when starting channel with
same name from another queue manager
1213 - Pathway listener generates FDCs on open of standard files
1229 - Permanent dynamic queues being marked as logically deleted on last close
1240 - Channel Server needs to update status for unexpected thread close
1244 - Speed up instmqm
1246 - implement workaround for the regression in the OSS cp command introduced
in G06.29/H06.06 where a Format 2 file is created by default when
copying to Guardian
1247 - Fixes to SSL CRL processing, added CRL reason to message amq9633
1253 - SSL samples required updating to reflect enhanced certificate file
organization - cert.pem and trust.pem
1254 - Fix an MQDISC internal housekeeping problem
1256 - MCA does not exit after re-use count if an error occurs during early
initialization
1260 - Speed up strmqm when performed on very busy systems with large number
of CPUs by minimizing calls to HP FILE_GETOPENINFO_ API
1264 - Correct the handling of the option to make Message Overflow files
audited in QS
1266 - Improve diagnostic information of FFST text for semaphore problem
1271 - After sequence of 2 CPU downs, EC, QS and CS still have openers
1272 - Improve protection in svcmqm when files in the installation are open
1273 - Memory leak in the command server caused by unreleased object lists
1277 - Don't FFST if initialization fails because the mqs.ini file doesn't
exist
1281 - LQMA thread doesn't end when CPU containing application goes down
1288 - Channels not retrying after CPU failure that also causes takeover of CS
1290 - MQDISC when connection broken doesn't tidy up transaction
1291 - Correct the syncpoint usage when amqsblst is used as a server. Enhance
amqsblst for fault tolerant behavior - makes amqsblst attempt to
reconnect and reopen objects on 2009 errors so it can be used during
fault tolerant testing
1294 - Application process management rules don't always work correctly
1297 - Correct file permission of trace directory and files - changed
permission of trace directory to 777
1301 - No queue manager start or stop events generated
1302 - instmqm function get_Guardian_version should look for string
"Software release ID"
1306 - instmqm validation fails when Java is not installed - issue a warning
if the java directory doesn't exist and continue the installation
1310 - OSS Serverclasses not restarting in Pathway if they end prematurely
1313 - EC process management can exceed maximum number of threads for LQMA
1317 - REFRESH CLUSTER command with REPOS(yes) fails
1319 - MQPUT and MQPUT1 modifying PMO.Options when creating a new MsgId
1324 - MQPUT returned MQRC_BACKED_OUT when putting message that required
segmentation to local queue
1325 - Trace state doesn't change in servers unless process is restarted
1340 - QS error handling MQPUT checkpoint. Also can lead to zombie messages on
queue requiring queue manager restart to clear
1341 - MQGET not searching correctly in LOGICAL_ORDER for mid-group messages
1346 - EC initial memory use too high. Initial allocation was approximately
18 megabytes
1351 - Upgrade logging format to V6.x style
1353 - MQGET of 210kbyte NPM from queue with checkpointing disabled caused
message data corruption at offset 106,906
1355 - xcsExecProgram sets current working directory to /tmp - changed to
installation errors directory
1357 - instmqm fails to create an OSS symbolic link after a cancelled install
1362 - MsgFlags showing segmentation status should still be returned in
MQGET even if applications specifies MQGMO_COMPLETE_MSG
1364 - endmqlsr sometimes hangs
1366 - Correct trace, FDC and mqver versioning information for V5.3.1.1


All fixes that were previously released in V5.3.0 and V5.3.1 are also included
in this release. For information on fixes prior to V5.3.1.1, please refer to
the readme for V5.3.1.3 or earlier.


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

Fix Pack V5.3.1.4 introduces support for the HP Integrity NonStop BladeSystem
and the J-Series operating system, using the same WMQ software package as
is used for the Integrity NonStop Server H-Series platform. See below for the
details.

We have made the following updates to the list of recommended SPR levels
for H-Series in this V5.3.1.4 release, for the following reasons:

- T9053 (DP2) to replace the TCD/TCF previously specified (ATJ) with a fully
QA'd SPR (ATS) that fixes a number of OSS file system issues
- T1265 (TCP/IP IPv6) to replace the TCD/TCF previously specified (AAX) with
a fully QA'd SPR (ACB) containing HP SOLN# 10-080521-3332

For the HP Integrity NonStop BladeSystem J-Series systems, the following
system software versions are the minimum mandatory level for V5.3.1.4:

- J06.03.00 or later

The following levels are RECOMMENDED by IBM for the HP Integrity NonStop
BladeSystem J-Series systems to address a TCP IPV6 performance problem
encountered during recent tests and customer deployments:

- SPR T0694H01^AAC (this is currently a TCD, and may not be available from
scout)

The list of mandatory HP operating system and SPR levels has not changed
since the V5.3.1.1 release. Please read the following information carefully,
and if you have any questions, please contact IBM.

For the HP NonStop Server G-Series systems, the following system software
versions are the minimum mandatory level for V5.3.1.4 (unchanged):

- G06.25 or later
- SPR T8306G10^ABG or later
- SPR T8994G09^AAL or later
- SPR T8397G00^ABC or later
- SPR T1248G07^AAY or later

The following levels are RECOMMENDED by IBM for the HP NonStop Server
G-Series systems to avoid some significant problems encountered
during recent tests and customer deployments:

- SPR T8994G09^AAN (OSS Local Sockets)
- SPR T8397 "latest available" (OSS Socket Transport Agent)
- SPR T8306G10^ABL (OSS sockets) for G06.25/26/27
T8306G11^ABM for G06.28
T8306G12 base for G06.29 and later
- SPR T8620G10^ACJ (OSS file system) for G06.25/26
T8620G13^ACL for G06.29 and later
- SPR T9053G11^ATT (DP2)
- SPR T9050G09^AQF (NonStop Kernel)
- SPR T8607G08^AGS (TMF main)

For the HP Integrity NonStop Server H-Series systems, the following system
software versions are the minimum mandatory level for V5.3.1.4 (unchanged):

- 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

The following levels are RECOMMENDED by IBM for the HP Integrity NonStop
Server H-Series systems to avoid some significant problems encountered
during recent tests and customer deployments:

- Base release H06.06
- SPR T1248H06^ABF (pthreads)
- SPR T8994H01^AAP (OSS Local Sockets)
- SPR T8397 "latest available" (OSS Socket Transport Agent)
- SPR T8306H02 base (OSS sockets) for H06.06/07/08
T8306H04 base for H06.09/10/11/12
T8306H04^ABS for H06.13 and later
- SPR T8620H03^ACM (OSS file system) for H06.06/07
T8620H04^ACN for H06.08 and later
- SPR T9053H02^ATS (DP2)
- SPR T9050H02^AQW (NonStop Kernel) for H06.06
T9050H02^ARF for H06.07 and H06.01.01
T9050H02^ASJ for H06.08
T9050H02^ASK for H06.09
T9050H02^ARS for H06.10
T9050H02^ARV for H06.11
T9050H02^ASC for H06.12
T9050H02^ASD for H06.13
T9050H02^ASE for H06.14 and later
- SPR T8607H01^AGV (TMF main)
- SPR T1265ACB (TCP/IP IPv6)

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 to V5.3.1.4
---------------------

You may upgrade any prior service level of WebSphere MQ V5.3.1.x
for HP NonStop Server to V5.3.1.4 level using this release.
The installation tool, svcmqm, is used to upgrade existing installations
to this level. Additionally, the placed files for any prior level of V5.3.1
can be overlaid with the new files from V5.3.1.4 and then instmqm can be used
to create new installations at the updated V5.3.1.4 level.

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

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

If you use SSL channels, and are upgrading from WMQ V5.3.1, you must perform
a small reconfiguration of the Certificate store before running any SSL
channels after you have upgraded. The steps that are required are described
below in the Post-Installation section. If you do not perform this
reconfiguration, SSL channels in the upgraded V5.3.1.4 installation will
fail with the log messages similar to the following:

For sender channels:

09/29/07 08:52:43 Process(0,483 $Z8206) User(MQM.ABAKASH) Program(amqrmppa)
AMQ9621: Error on call to SSL function ignored on channel
'ALICE_BOB_SDRC_0000'.

EXPLANATION:
An error indicating a software problem was returned from a function which is
used to provide SSL support. The error code returned was '0xB084002'. The error
was reported by openssl module: SSL_CTX_load_verify_locations, with reason:
system lib. The channel is 'ALICE_BOB_SDRC_0000'; in some cases its name cannot
be determined and so is shown as '????'. This error occurred during channel
shutdown and may not be sufficiently serious as to interrupt future channel
operation; Check the condition of the channel.
ACTION:
If it is determined that Channel operation has been impacted, collect the items
listed in the 'Problem determination' section of the System Administration
manual and contact your IBM support center.
----- amqccisx.c : 1411 -------------------------------------------------------
09/29/07 08:52:44 Process(0,483 $Z8206) User(MQM.ABAKASH) Program(amqrmppa)
AMQ9001: Channel 'ALICE_BOB_SDRC_0000' ended normally.

EXPLANATION:
Channel 'ALICE_BOB_SDRC_0000' ended normally.
ACTION:
None.

For client or receiver channels:

-------------------------------------------------------------------------------
09/29/07 08:05:28 Process(1,802 3 $X0545) User(MQM.HEMA) Program(amqrmppa_r)
AMQ9620: Internal error on call to SSL function on channel '????'.

EXPLANATION:
An error indicating a software problem was returned from an function which is
used to provide SSL support. The error code returned was '0x0'. The error was
reported by openssl module: SSL_load_client_CA_file, with reason: CAlist not
found. The channel is '????'; in some cases its name cannot be determined and
so is shown as '????'. The channel did not start.
ACTION:
Collect the items listed in the 'Problem determination' section of the System
Administration manual and contact your IBM support center.
----- amqccisx.c : 1347 -------------------------------------------------------
09/29/07 08:05:28 Process(1,802 3 $X0545) User(MQM.HEMA) Program(amqrmppa_r)
AMQ9228: The TCP/IP responder program could not be started.

EXPLANATION:
An attempt was made to start an instance of the responder program, but the
program was rejected.
ACTION:
The failure could be because either the subsystem has not been started (in this
case you should start the subsystem), or there are too many programs waiting
(in this case you should try to start the responder program later). The reason
code was 0.

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

If upgrading from V5.3.1:

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

If the application is not re-bound/linked to the V5.3.1.4 MQI, MQCONN
API calls will fail with a MQRC 2059 and the WMQ EC process will output
a FDC when the MQI incompatibility is detected, as follows:

Probe Id :- EC075003
Component :- ecaIsECup
Comment1 :- Application MQ API not compatible, relink application
Comment2 :- <process cpu,pid process name>
Comment3 :- <application executable name>

If upgrading from V5.3.1.1, V5.3.1.2 or V5.3.1.3:

If your non-native or native applications use a static linkage method for
binding with the MQI, IBM recommend that you use the HP BIND or NLD utility
to re-bind/link these applications for use with V5.3.1.4. If you choose to not
re-link or re-bind your applications, then you will not benefit from fixes for
the following problems (listed above as fixed in fixpacks 5.3.1.3 and 5.3.1.4):

APAR IC55719 - Non-native MQINQ binding does not deal with some null
pointer parameters correctly

APAR IC54305 - The HP TNS (non-native) C compiler generates Warning 86 when
compiling MQI applications

OR 993 - Due to the way that default file security was used, file
security for certain shared memory files used by the
queue manager (SZ***) may inadvertently change in a way that
prevents applications not in the mqm group from issuing
MQCONN.

If your applications link 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.4 using
the HP nld utility. This step is only required if you have created a new
V5.3.1.4 installation and want to use the same copies of application programs
with it as were running previously with V5.3.1. If you upgrade an existing
V5.3.1 installation, the updated libraries will be in the same location and
so this step is not required.

Installation from Electronic Software Download on G or H Series based systems
-----------------------------------------------------------------------------

These instructions apply to installing WebSphere MQ for HP NonStop Server,
Version 5.3.1.4 from the package downloaded from IBM.

Use svcmqm to update an existing installation from the V5.3.1.4 placed files.

1. Unzip the fixpack distribution package - wmq53.1.4.tar.zip.
The fixpack distribution package contains the following files:

readme_wmq_5.3.1.4 This README
wmq53.1.4_G06.tar.Z G-Series G06 Package
wmq53.1.4_H06.tar.Z H-Series H06 Package

2. Identify the correct fixpack package to install:

For G-Series systems (G06) use: wmq53.1.4_G06.tar.Z
For H-Series systems (H06) use: wmq53.1.4_H06.tar.Z

3. Upload the compressed fixpack archive to the OSS file system in binary mode.
You may wish to store the compressed archive, and the expanded contents
in a location where you archive software distributions from IBM.
If you do this, you should store the compressed archive in a directory
that identifies the version of the software it contains,
for example, "V5314".

mkdir -p /usr/ibm/wmq/V5314
upload (in binary mode) the correct compressed tarfile to this directory

4. Extract the fixpack compressed tarfile using commands similar to:

cd /usr/ibm/wmq/V5314
uncompress wmq53.1.4_H06.tar.Z
tar xvof wmq53.1.4_H06.tar

5. Locate your WMQ V5.3.1.x installation(s). The service installation procedure
requires the full OSS path names of the opt/mqm and var/mqm directories for
each WMQ installation to which the fixpack will be installed.

6. Logon to OSS using the WMQ installation owner's userid

7. End all Queue Managers defined in the WMQ Installation.
endmqm <qmgr name>

Ensure all Queue Managers defined in the WMQ installation
are ended.
dspmq

Ensure that the WMQ installation is at any suitable V5.3.1 level.
mqver -V

8. End any non-Pathway listeners for Queue Managers defined in the
WQM installation:
endmqlsr -m <qmgr name>

9. Verify that no files in the Guardian subvolumes of the installation to
be updated are open. The installation cannot proceed safely unless all
files in these subvolumes are closed. Use the TACL command 'FUP LISTOPENS'
for the files in all three subvolumes - an absence of output indicates
that no files are open. If files are shown to be open, use the output
from the command to identify processes that are holding files open.

10. Backup your WMQ Installation; the fixpack cannot be uninstalled.
instmqm -b can be used to back up an installation. Please refer
to the readme file included with release WMQ V5.3.1.

11. Install the fixpack by running the supplied service tool (svcmqm).
Svcmqm requires the location of the OSS var tree as well
as the OSS opt tree. These locations can be supplied automatically by
running svcmqm in an OSS shell where the environment variables for the
WMQ installation being updated have been established (typically by
sourcing "wmqprofile"). If this is the case, svcmqm does not require the
-i and -v parameters. If the environment variables for the WMQ
installation are not established in the environment of svcmqm, the
locations of the OSS opt and var trees must be supplied explicitly using
the svcmqm command line parameters -i and -v.

For example:

cd /usr/ibm/wmq/V5314
opt/mqm/bin/svcmqm -s /usr/ibm/wmq/V5314/opt/mqm
-i /wmq1/opt/mqm
-v /wmq1/var/mqm

svcmqm will prompt to confirm the location of the OSS opt tree for the
installation to be updated.
Type "yes" to proceed.

Svcmqm will then update the installation. The current WMQCSTM file for
the installation will be renamed to BWMQCSTM as a backup copy, before it
is regenerated. Note that any changes to the WMQCSTM file you have made
will not be copied to the new WMQCSTM file, however they will be preserved
in the backup copy made before the WMQCSTM file was regenerated.

12. Repeat Steps 5-11 for any other WMQ installations that you want to update
with this fixpack.

13. You can install this fixpack in the WMQ placed installation files so that
any future WMQ product installations will include the fixpack updates.

To do this, locate your WMQ placed installation filetree containing the
opt directory, make this your current working directory (use 'cd') and
then unpack the contents of the tar archive for this fixpack over the placed
file tree. For example, if the placed files are located in the default
location /usr/ibm/wmq/V5314, for a H-Series system:

cd /usr/ibm/wmq/V5314
tar xvof /usr/ibm/wmq/V5314/wmq53.1.4_H06.tar

Substitute G06 in the above command suggestions if you are installing
on an G-Series system.


Installation on a NonStop BladeSystem
-------------------------------------

These instructions apply to installing WebSphere MQ for HP NonStop Server on
a NonStop BladeSystem using the original installation media, in conjunction
with the 5.3.1.4 package downloaded from IBM. NonStop BladeSystem platforms
are not supported prior to V5.3.1.4, and installation requires that V5.3.1.4
files to be overlaid on a set of placed files from the base product media
prior to performing the installation.

1. Place the files for the Refresh Pack 1 (5.3.1.0) version of WebSphere MQ
for HP NonStop Server on the target system. Refer to the "File Placement"
section in Chapter 3 of the "WebSphere MQ for NonStop Server Quick
Beginnings" guide. Pages 11-13 describes how to place the files.
Do not attempt to install the placed files using the instmqm script
that was provided with V5.3.1.0 at this time. The V5.3.1.0 version of
instmqm does not support installation on NonStop BladeSystem.

2. Unzip the 5.3.1.4 fixpack distribution package - wmq53.1.4.tar.zip.
The fixpack distribution package contains the following files:

readme_wmq_5.3.1.4 This README
wmq53.1.4_G06.tar.Z G-Series G06 Package
wmq53.1.4_H06.tar.Z H-Series H06 Package

3. This installation requires the wmq53.1.4_H06.tar.Z package.
Locate the WMQ placed installation filetree containing the opt directory
prepared in step 1 above, and upload the wmq53.1.4_H06.tar.Z fixpack
archive to this location in binary mode.

4. Extract the fixpack compressed tarfile using commands similar to:

cd /usr/ibm/wmq/V5314
uncompress wmq53.1.4_H06.tar.Z

5. Unpack the contents of the extracted tar archive for this fixpack over the
placed file tree. For example, if the placed files are located in the default
location /usr/ibm/wmq:

cd /usr/ibm/wmq
tar xvof /usr/ibm/wmq/V5314/wmq53.1.4_H06.tar

6. Install the product from the updated installation file tree using the
instructions in Chapter 3 of "WebSphere MQ for NonStop Server Quick
Beginnings" guide, pages 13-29. Before beginning, review the list of
changes to Chapter 3 detailed in the "Documentation Updates" section
at the end of this README file. Note also that the list of installed
files displayed will differ from those shown in the examples in the manual.


Post-Installation
-----------------
If upgrading from WMQ V5.3.1, read the following post-installation instructions:

Non-Native TNS Applications:

Re-BIND/NLD any non-native (TNS) or native static applications.
See "Upgrading to V5.3.1.4" above for more information.

Re-binding non-native (TNS) or native static applications is REQUIRED if
upgrading from WMQ V5.3.1 but is RECOMMENDED if upgrading from any more
recent fixpack.

For G-Series, ensure that applications that use one of the WMQ SRL User
Libraries (i.e. MQMSRL, MQMRSRL, MQMFSRL or MQMFRSRL) have the
correct User Library specified for the upgraded installation.

If you use SSL channels and have not already installed V5.3.1.1:

Edit the SSL certificate store, cert.pem and move all the CA certificates
to a new file, trust.pem, stored in the same directory as cert.pem. The
only items that should remain in cert.pem are the queue manager's personal
certificate, and the queue manager's private key. These two items should
be located at the start of the cert.pem file. All other certificates
(intermediate and root CAs) must be moved to trust.pem. The trust.pem file
must be in the same directory as cert.pem, as configured in the queue
manager's SSLKEYR attribute.

Update the copy of the entropy daemon program that you run for SSL channels
on the system with the new version (...opt/mqm/ssl/amqjkdm0).

Enable new support for Danish CCSID 65024:

Customers who wish to enable the new support for Danish CCSID 65024
should do the following to install the revised ccsid.tbl file:

Issue the following commands on OSS:

1. Logon to OSS using the WMQ installation owner's userid
2. End all Queue Managers defined in the WMQ Installation.
endmqm <qmgr name>
3. Source in the installation's wmqprofile
. $MQNSKVARPATH/wmqprofile
4. cp -p $MQNSKOPTPATH/samp/ccsid.tbl $MQNSKVARPATH/conv/table/
5. Start queue managers

Guardian C++ DLLs:

Ensure that the WMQ Guardian C++ DLLs are 'executable' by using
"FUP ALTER" to set their FILECODE to either 700 (for G-Series)
or 800 (for H-Series). Use commands similar to the following:

1. Logon to TACL using the WMQ installation owner's userid
2. OBEY your WMQ Installation's WMQCSTM file
3. VOLUME [#param MQNSKOPTPATH^LIB^G]
4. FUP ALTER IMQI2,CODE 800
5. FUP ALTER IMQI2T,CODE 800
6. FUP ALTER IMQI3,CODE 800
7. FUP ALTER IMQI3T,CODE 800
8. Logoff

For G-Series systems, use CODE 700.

Guardian Subvolume File Permissions

The WMQ Guardian Installation Subvolume and all WMQ Guardian Queue
Manager Subvolumes must accessible to both MQM group members
and to users that run WMQ application programs.

Ensure that:

All members of the MQM security group have read, write, execute
and purge permission to these subvolumes.

All users that run WMQ application programs, have read, write
and execute permission to these subvolumes

Restart Queue Managers:

Restart the queue managers for the installation you have
updated with this fixpack.


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

This fixpack cannot be automatically uninstalled if a problem occurs
during the update of an installation using svcmqm.

You should use the instmqm -b option to create a backup of an
installation before applying the service. If a problem occurs
or you need to reverse the upgrade at a later date, use the
instmqm -x option to restore a backup of the installation at the
prior service level.


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

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

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 CPU that was used to run the 'strmqbrk' command.
The Publish/Subscribe broker does not automatically recover in the event
of CPU failures.

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

8. Control commands in Guardian (TACL) environment don't obey the RUN option
"NAME" as expected

A Guardian control command starts an OSS process to run the actual
control command - and waits for it to complete. When the NAME option is
used, the Guardian control command process uses the requested name, but
the OSS process cannot and is instead named by NonStop OS.

If the Guardian control command is prematurely stopped by the operator
(using the TACL STOP command for example) the OSS process running the
actual control command may continue to run. The OSS process may need to be
stopped separately and in addition to the Guardian process.

9. Trace doesn't end automatically after a queue manager restart
(APAR IC53352) and trace changes do not take effect immediately

If trace is active and a queue manager is restarted, the trace settings
should be reset to not trace any more. Instead, the queue manager
continues tracing using the same options as before it was restarted.
The workaround is to disable trace using endmqtrc before ending, or while
the queue manager is ended.

Also, changes to trace settings do not always take effect immediately
after the command is issued. For example, it could be several MQI calls
later that the change takes effect. The maximum delay between making a
trace settings change and the change taking effect would be until the end
of the queue manager connection, or the ending of a channel.

10. Some EMS events generated to default collector despite an alternate
collector being configured (APAR IC53005)

An EMS event message "FFST record created" is generated using the OSS
syslog() facility whenever an FDC is raised by a queue manager. This
EMS event cannot be disabled, and goes to the default collector $0. For
OSS processes, an alternate collector process can be specified by
including an environment variable in the context of these processes
as in the following example:

export EMS_COLLECTOR=\$ALT

Guardian processes always use the default collector because HP do not
provide the ability to modify the collector in the Guardian environment.
HP is investigating if a change is possible. No fix for this problem
has yet been identified.

11. The use of SMF (virtual) disks with WMQ is not supported because of
restrictions imposed by the OSS file system. For more details, please
refer to the HP NonStop Storage Management Foundation User's Guide
Page 2-12.

12. The maximum channel batch size that can be configured (BATCHSZ attribute)
is 2000. If you need to run channels with batch sizes greater than 680
you must increase the maximum message length attribute of the
SYSTEM.CHANNEL.SYNCQ to 60000.

e.g. from RUNMQSC - ALTER QL (SYSTEM.CHANNEL.SYNCQ) MAXMSGL (60000)

13. The SYSTEM.CHANNEL.SYNCQ is a critical system queue for operation of
the queue manager and should not be altered to disable MQGET or MQPUT
operations, or to reduce the maximum message size or maximum depth
attributes from their defaults.

14. Currently, the cluster transmission queue (SYSTEM.CLUSTER.TRANSMIT.QUEUE)
cannot be moved to an alternative Queue Server because it is constantly
open by several internal components. The following procedure (which
requires a "quiet" queue manager, and a queue manager restart) can be
used to achieve this reconfiguration. Do not use this procedure on a
queue manager that is running in production. Read and understand the
procedure carefully first since it includes actions that cause
internal errors to be generated in the queue manager.

1. Find the Guardian name of the OSS repository executable file amqrrmfa
gname <MQInstall>/opt/mqm/bin/amqrrmfa
/amqrrmfa -->\ZAPHOD.$DATA03.ZYQ0000G.Z0000LCH
2. Rename the OSS repository executable (opt/mqm/bin directory)
mv amqrrmfa amqrrmfax
3. On Guardian stop the repository processes using the gname output
STATUS *, PROG <Guardian file name> , STOP
e.g., STATUS *, PROG \ZAPHOD.$DATA03.ZYQ0000G.Z0000LCH , STOP
At this point the EC will start continuously generating FDCs and
log messages as it attempts to, and fails, to restart the repository
servers that were stopped. Perform the remaining steps in this
procedure without delay to avoid problems with excessive logging
such as disk full conditions.
4. Verify processes are stopped, note the STOP option is not used
STATUS *, PROG <Guardian file name>
e.g., STATUS *, PROG \ZAPHOD.$DATA03.ZYQ0000G.Z0000LCH
5. Issue the altmqfls --server command to move the cluster transmission
queue to an alternate queue server
6. Issue dspmqfls to verify the alternate server assignment
7. Rename the OSS repository executable back to the expected name
mv amqrrmfax amqrrmfa
8. End the queue manager using preemptive shutdown. The EC will generate
FDCs ending because of the earlier attempts to start a repository
manager while the executable was renamed. There will be FDCs and
EC Primary process failover

Component :- xcsExecProgram
Probe Description :- AMQ6025: Program not found
Comment1 :- No such file or directory
Comment2 :- /opt/mqm/bin/amqrrmfa
...
AMQ8846: MQ NonStop Server takeover initiated
AMQ8813: EC has started takeover processing
AMQ8814: EC has completed takeover processing
...
The EC may have to be manually TACL stop if quiesce or immediate
end is used thus the need for the preemptive shutdown
endmqm -p <qmgr name>
9. Restart the queue manager
strmqm <qmgr name>

15. In Guardian/TACL environments, support for some WMQ command-line programs
has been deprecated for WMQ Fixpack 5.3.1.3 and later.

The affected command-line programs are:

amqoamd
amqrdbgm
amqrfdm
crtmqcvx
endmqlsr
runmqchi
runmqchl
runmqdlq
runmqlsr
runmqtrm

These programs will continue to function for now, however their use in
Guardian/TACL environments is discouraged. Support for these programs
in Guardian/TACL environments may be withdrawn completely in a future
WMQ 5.3 release/fixpack.

IBM recommends that customers use the OSS version of these programs instead.

Customers who want to route output from WMQ OSS tools to VHS or other Guardian
collectors should use the OSSTTY utility. OSSTTY is a standard utility
provided by OSS and is described in the HP publication "Open System Services
Management and Operations Guide".

Note: See Item 3. in "Known problems and workarounds" for a description of
restrictions when using the MQ Broker administration commands in the
Guardian/TACL environment.

16. Do not use WebSphere MQ with a $CMON process that alters attributes of WMQ
processes (for example the processor, priority, process name or program
file name) when they are started. This is not a supported environment since
there are components in WMQ that rely on these attributes being set as
specified by WMQ for their correct operation.

17. Support for forked processes

MQI Support from forked processes in OSS is subject to the following
restrictions:
1. If forking is used, MQI operations can be performed only from child
processes. Using MQI verbs from a parent process that forks child
processes is not supported and will result in unpredictable
behavior.

2. Use of the MQI from forked processes where the parent or child is
threaded is not supported.

18. TMF Outage handling

TMF outage handling has been improved with V5.3.1.4, however there are
still two limitations to be aware of:

1. When TMF disables the starting of new transactions (either automatically
if the audit trail reaches 90% full, or when an operator issuing the
STOP TMF or DISABLE BEGINTRANS commands in TMFCOM) the operating system
does not correctly notify the Channel Server. This is a consequence
of a known defect in HP TMF MAIN T8607, described by the following:
- HP Genesis solution #10-080805-5015
- HP Web Support KBNS article gcsc30975
- Hotstuff bulletin HS02990.

The defect causes the Channel Server to experience one or more of the
following symptoms once BEGINTRANS has been re-enabled by TMF:
- A sequence number mismatch errors during channel start attempts
- Channel server generates FDCs that report file system error 723
from TMF_EXPORT_

If these conditions occur, the only known recovery is to stop the
primary Channel Server process allowing the backup to take over, or
to restart the queue manager.

2. If a STOP TMF, ABRUPT command is issued, TMF marks all open audited
files as corrupt and the queue manager cannot perform further
processing until this condition is rectified by restarting TMF.
In this state, the queue manager will freeze further operation, and log
the condition in the queue manager log file every 10 seconds for a
maximum of 50 attempts. Whether or not TMF is restored within this
timeframe, the WMQ queue manager should be restarted to reduce the risk
of any undetected damage persisting.

19. Triggering HP NSS non-C Guardian applications

The MQ default Trigger Monitor process, runmqtrm, at present cannot
directly trigger the following application types:
- Guardian TACL scripts or macro file
- COBOL application
- TAL application

An OSS script file (wmqtrig) provides indirect support for these
files types. To use this script, the PROCESS definition APPLTYPE should
be set to UNIX, and the APPLICID should refer to the script as in
the following examples:

For a TACL script called "trigmacf":
APPLICID('/opt/mqm/bin/wmqtrig -c \$data06.fp4psamp.trigmacf')
APPLTYPE(UNIX)

For a COBOL or TAL application called "mqsecha":
APPLICID('/opt/mqm/bin/wmqtrig -p /G/data06/fp4psamp/mqsecha')
APPLTYPE(UNIX)

Notes:
1. TACL scripts use the wmqtrig script with a "–c" option.
The –c option should use the Guardian representation for file name
of the TACL script file, with the special character ($) escaped,
for example:

\$data06.fp4psamp.trigmacf

2. COBOL and TAL applications use the wmqtrig script with a "–p" option.
The –p option must use the OSS representation for the file name of
the application, for example:

/G/data06/fp4psamp/mqsecha

3. C applications can be triggered directly by specifying
APPLICID('$DATA06.FP4PSAMP.MQSECHA')
APPLTYPE(NSK)

To trigger a PIC application using the WMQ Pathway MQS-TRIGMON00
serverclass, a DEFINE is required:

=_RLD_LIB_PATH,CLASS SEARCH,SUBVOL0 <Guardian MQ binary Volume.Subvolume>

For example:
ALTER MQS-TRIGMON00,
DEFINE =_RLD_LIB_PATH,CLASS SEARCH,SUBVOL0 $DATA06.FP4PBIN


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

1. FDCs from Component xcsDisplayMessage reporting xecF_E_UNEXPECTED_SYSTEM_RC

On RVUs G06.29 and later, or H06.06 and later:

These FDCs occur frequently on queue manager shutdown, and at times during
queue manager start, from processes that write to the queue manager log
files at these times, typically the cluster repository cache manager
(amqrrmfa) and the EC (MQECSVR). No functional problem is caused by these
FDCs, except that the queue manager log file misses some log messages
during queue manager shutdown. The FDCs report an unexpected return code
from the HP lseek() function. An example of an FDC demonstrating this
problem follows:

Probe Id :- XC022011
Component :- xcsDisplayMessage
Program Name :- $DATA06.RP1PBIN.MQECSVR
Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC

MQM Function Stack
nspPrimary
eclShutdownOK
xcsDisplayMessageForSubpool
xcsDisplayMessage
xcsFFST

6fffe660 000011FA ....
6fffe670 2F686F6D 652F726F 622F4D51 /home/test/MQ
6fffe680 352E332F 5250312F 50726F64 2F776D71 5.3/RP1/Prod/wmq
6fffe690 2F766172 2F6D716D 2F716D67 72732F51 /var/mqm/qmgrs/Q
6fffe6a0 4D312F65 72726F72 732F414D 51455252 M1/errors/AMQERR
6fffe6b0 30312E4C 4F47 01.LOG

This problem is fixed by the following HP SPR's

T8620ACL (OSSFS) for G06 HP OS
T8620ACM (OSSFS) for H06 HP OS

2. APAR IC54594 - EC abends with non-MQM user running application from non-MQM
directory.

Statically-bound TNS or native applications, that are not relinked after
installing Fixpack 5.3.1.4 have additional considerations. For these
applications, qmproc.ini Application Rules 2 and 4 will not work if the
application is located in a non-MQM directory.

3. The Guardian control commands for the Publish / Subscribe broker
(strmqbrk, endmqbrk, dspmqbrk ... etc) will not work correctly unless they
are run in the same CPU as the broker is running in, or was last running in.

Please use the equivalent OSS commands instead of the Guardian versions, or
ensure that the Guardian Publish / Subscribe broker commands run in the same
CPU as the broker was or is running in.


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

Please note that several supplements to the documentation have been provided
with fixpacks since V5.3 was originally released. These supplements have
been released in Adobe Acrobat format and can found in the
opt/mqm/READMES/en_US directory of any installation as well as the original
software distribution tree (placed files). The following supplements have
been released to date (the name of the file describes the content):
- Exits.pdf
- Java.pdf
- Pubsub.pdf
- SNAChannels.pdf
- SSLUpdate.pdf
- Upgmqmreadme.pdf

Also please note that the current published versions of the cross-platform
("family") books contain references to the IBM MQSeries V5.1 for Compaq NSK
product which is the previous major version of WebSphere MQ for HP NonStop
Server. Consequently, these references may not be accurate with respect to
the functional support provided by V5.3.1.

Websphere MQ Programmable Command Formats and Administration Interface
(SC34-6060-03)
-----------------------------------------------------------------------

Chapter 3 - PCF Commands and Responses in Groups

Page 19: Add "Refresh Queue manager" as a supported command

Chapter 4 - Definitions of Programmable Command Formats

Page 173: Add the following new command:

Refresh Qmgr

The Refresh Qmgr (MQCMD_REFRESH_Q_MGR) command refreshes the
Execution Controller (EC) process management rules.

This PCF is supported only on WebSphere MQ V5.3 HP NonStop Server.

Required parameters:
None

Optional parameters:
None

Error codes

This command might return the following in the response format
header, in addition to the values shown on page 18.

Reason (MQLONG)

The value can be:
MQRCCF_PARM_COUNT_TOO_BIG

Parameter count too big.


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

- Page 1: the typical approximate storage requirements are as follows:
+ OSS files placed before installation:
H-Series: 160Mb
G-Series: 120Mb
+ For each installation:
H-Series: Guardian 220Mb, OSS 350Mb, Total 570Mb
G-Series: Guardian 122Mb, OSS 276Mb, Total 400Mb
+ For each queue manager:
G/H-Series: Guardian 9.5Mb, OSS 0.2Mb, Total 10Mb

- 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, as follows:

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

- Page 15: instmqm has new command line options as described in these
release notes for creating and restoring backup archives

- Page 17: the SnaProviderName and TcpProviderName fields of the
QmgrDefaults stanza in the instmqm response file are used to populate
the proc.ini file to provide installation wide defaults for channels.
Please note that these fields do not get used for the default listener
configuration either on the command line (runmqlsr) or in the queue
manager's Pathway environment. Users must manually configure the
transport names for all listeners.

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

- If an installation was initially created without SSL (selection of the
installation type "CORE" for instmqm), the following procedure can be
used to update the installation to include SSL components. In the
instructions below, <MQInstall> refers to the location of the
installation that needs to be updated and <PlacedInstall> means the
location of the complete set of placed files for the level of WMQ that
corresponds to the installation being updated. All queue managers
must be ended before attempting this procedure.

1. mkdir <MQInstall>/opt/mqm/ssl
2. chmod 775 <MQInstall>/opt/mqm/ssl
3. cp <PlacedInstall>/opt/mqm/ssl/* <MQInstall>/opt/mqm/ssl
4. chmod 775 <MQInstall>/opt/mqm/ssl/amq*"...
5. cp <MQInstall>/opt/mqm/ssl/openssl <MQInstall>/opt/mqm/bin
6. chmod 664 <MQInstall>/opt/mqm/ssl/openssl
7. chmod 774 <MQInstall>/opt/mqm/bin/openssl
8. cp <MQInstall>/opt/mqm/ssl/amqjkdm0 <MQInstall>/opt/mqm/bin
9. chmod 775 <MQInstall>/opt/mqm/bin/amqjkdm0
10. mv <MQInstall>/opt/mqm/lib/amqcctca
<MQInstall>/opt/mqm/lib/amqcctca_nossl
11. mv <MQInstall>/opt/mqm/lib/amqcctca_r
<MQInstall>/opt/mqm/lib/amqcctca_r_nossl
12. cp <MQInstall>/opt/mqm/ssl/amqccssl <MQInstall>/opt/mqm/lib/amqcctca
13. cp <MQInstall>/opt/mqm/ssl/amqccssl_r
<MQInstall>/opt/mqm/lib/amqcctca_r
14. chmod 775 <MQInstall>/opt/mqm/lib/amqcctca*
15. The <MQInstall>/var/mqm/qmgrs/<qmgr name> directory should have an
ssl directory which is where you will store the certificate related
files (cert.pem, trust.pem etc.)
16. The <MQInstall>/opt/mqm/samp/ssl should exist already with the ssl
samples
17. If the entropy daemon is not configured on the system this will need
to be performed. Refer to the WMQ V53 HP NonStop System
Administration Chapter 11 page 165-167
18. Install the certificates per the updated instructions, SSLupdate.pdf
found in <MQInstall>/opt/mqm/READMES/en_US

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 three parameters:
svcmqm [-i installationtree] [-v vartree] -s servicepackage

where "installationtree" is the full path to the location of the opt/mqm
directory of the installation to be updated
"vartree" is the full path to the location of the var/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 -v /home/me/wmq/var/mqm
-s /home/me/wmqfiles/opt/mqm

which will update the installation in /home/me/wmq/opt/mqm and
/home/me/wmq/var/mqm from the maintenance package in directory tree
/home/me/wmqfiles/opt/mqm.

If either or both the "-i installationtree" and "-v vartree" parameters
are omitted, svcmqm will use the current setting of the appropriate
environment variable - either WMQNSKOPTPATH or WMQNSKVARPATH.


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

Chapter 2 - An introduction to WebSphere MQ administration

- Page 16: before running any control commands on OSS or NonStop OS it is
necessary to establish the environment variables for the session. When
an installation is created a file called wmqprofile is also created in
the var/mqm directory that will establish the environment for an OSS
shell. Likewise, a file is also created in the NonStop OS subvolume
containing the WMQ NonStop OS samples called WMQCSTM that can be used
to set up the appropriate environment variables for a NonStop OS TACL
session.

To establish the WMQ environment for an OSS shell session:

. wmqprofile

To establish the WMQ environment for a NonStop OS TACL session:

obey WMQCSTM

The same steps are required before running any applications in the
OSS or NonStop OS environment.

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 7 - WebSphere MQ for HP NonStop Server architecture

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

Chapter 8 - Managing scalability, performance, availability and data
integrity

- Page 104: the last paragraph of the OpenTMF section should be reworded
as follows:

No special administrative actions are required for this use of TMF.
WebSphere MQ uses and manages it automatically. You must ensure that
the RMOPENPERCPU and BRANCHESPERRM configuration parameters of TMF are
set to appropriate values for your configuration. Please see Chapter 12
- Transactional Support - Configuring TMF for WebSphere MQ for
information on how to calculate the correct values. The HP TMF Planning
and Configuration Guide describes the subject of resource managers and
heterogeneous transaction processing.

Chapter 9 - Configuring WebSphere MQ

- Page 119: the CPUS section should state that the default can be
overridden using the crtmqm -nu parameter. See Chapter 18 - The control
commands for a description of how to use this parameter with crtmqm.

- Page 120: the section describing the ARGLIST attribute of a TCP/IP
Listener should also mention the use of the optional -u parameter to
configure channels started by the listener as unthreaded processes.
The default is to run incoming channels as threads in an MCA process.

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

- Page 133: Figure 23 remove :
# OAM Manager stanza #
OamManager:

- Page 136: the Exit properties section should state that the only
supported way of configuring and running a Cluster Workload (CLWL) Exit
for HP NonStop Server is in FAST mode. The CLWLMode setting in qm.ini
is required to be set to FAST, which is the default for WebSphere MQ
on this platform.

- Page 139: the MQIBindType attribute of the Channels stanza is set by
crtmqm to FASTPATH. This should not be changed, except under the
direction of IBM Service.

- Page 140: the AdoptNewMCA=FASTPATH option is always required for
this platform in order for the adoption of MCAs to be effective. The
"Attention!" box after the description of the FASTPATH option should
be ignored.

- Page 140: add the following description of the ClientIdle attribute:

ClientIdle=seconds

ClientIdle specifies the number of seconds of inactivity to permit
between client application MQI calls before WebSphere MQ terminates
the client connection. The default is to not terminate client
connections however long they remain inactive. When a client connection
is terminated because of idle activity, the client application receives
a connection broken result (2009) on its next MQI call.

Chapter 11 - Working with the WebSphere MQ Secure Sockets Layer (SSL) support

A documentation supplement has been written to replace the sections on
Page 170 (Preparing the queue manager's SSL files) to Page 176 (Building
and verifying the sample configuration) because of changes to the files
that WebSphere MQ uses to hold certificates. The documentation supplement
is called SSLupdate.pdf, and can be found in the opt/mqm/READMES/en_US
directory of an installation.

Chapter 12 - Transactional Support

- Page 185: The descriptions of the TMF attribute RMOPENPERCPU in the
Resource manager configuration section is modified as follows:

RMOPENPERCPU

Each WebSphere MQ thread or process that handles transactions has
an open of a Volatile Resource Manager in the CPU it runs in. In
addition, each application thread or process using the MQI also has
an open. The minimum requirement for this configuration parameter
is therefore the sum of:
+ all Queue Server processes in that CPU
+ all LQMA and MCA threads running in that CPU
+ all MQI application threads running in that CPU
+ 10 (to account for miscellaneous queue manager processes that
could be running in that CPU)
You should calculate the peak values of these numbers across all CPUs
and add a safety margin to arrive at the correct value for your system.
The HP default value of 128 for this parameter is often suitable for
small configurations, but unsuitable for medium or large ones.

- Page 186: add the following paragraph to the Troubleshooting section
for Configuring TMF:

If the RMOPENPERCPU value is not configured to allow sufficient opens
of resource managers in a CPU, WebSphere MQ connections will fail with
an unexpected return code, and FDCs will be generated reporting an
error with the TMF_VOL_RM_OPEN_. The workaround is to distribute
applications and queue manager processes in the CPU that exceeds
the limit to other CPUs. The correct remedy is to schedule an outage
and modify the TMF configuration.

- Page 186: add the following paragraph to the Troubleshooting section
for configuring TMF:

If TMF is stopped, or new transactions are disabled, and WMQ requires
an internal "unit of work" (TMF transaction) to perform an update to
a protected resource requested by an MQI call, that call will fail
and the reason code returned will be MQRC_UOW_NOT_AVAILABLE (2255).

Note that in some cases, updates to protected resources may be
required by MQI operations do not directly perform messaging
operations - for example, MQOPEN of a model queue that creates a
permanent dynamic queue. If MQI calls return MQRC_UOW_NOT_AVAILABLE,
check the status of the TMF subsystem to determine the likely cause.


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 use count for
threaded agents is now 100.

- Page 204: the "valid attribute values" for the attribute "ExecutableName"
should be stated as "File name part only of the program to run for the
LQMA or MCA process".

- Pages 203 - 205, Table 20: Process Management: Keyword definition Summary

There are a number of errors in the Process Management Keyword
definition table:

1. Environment variables:
ENVxx should be Envxx

2. Executable Name to Match:
ExecNameMatch should be ExeNameMatch

3. Fail if CPU unavailable:
FailOnCPUunavail should be FailOnCPUUnavail

4. Preferred number of Threaded Agents:
PreferedThreadedAgents should be PreferredThreadedAgents

Default values:

5. MaxThreadedAgents: change from 10 to 20

6. MaxUnthreadedAgents: change from 20 to 200

7. MaxThreadedAgentUse: change from 10 to 100

Pages 199 - 201, Table 16. Process management: agent attributes

The same default value changes are required:

1. Maximum number of unthreaded agents: 200
2. Maximum number of threaded agents: 20
3. Maximum reuse count for threaded agents: 100


Chapter 15 - Recovery and restart

- Page 216: Configuring WebSphere MQ, NonStop RDF, and AutoSYNC to support
disaster recovery
To configure RDF to work with a existing WMQ V53 queue manager:
- End the WMQ V53 queue manager.
- Using the HP BACKUP or PAK utility specifying the AUDITED option
Backup the primary site Guardian WMQ queue manager subvolume.
- Using the HP RESTORE or UNPAK utility specifying the AUDITED option
Restore the files on the backup site.
- Ensure that on the backup system that the alternate key file
attribute (ALTKEY) for files amqcat and amqpdb of each queue
manager are set to the correct (backup system) node name

- Page 217: the example of the altmqfls command to set the RDF
compatibility mode for large persistent messages is correct but too
simplistic. Please use care when using altmqfls to set the queue options
(--qsoptions parameter) and refer to the reference section for the
control commands for a complete description of using this option.

- Page 217: the bullet point that describes the configuration of AutoSYNC
filesets is incorrect when it states that NO ALLSYMLINKS should be
specified. Replace sub-bullet item number 2 with the following text:

2. The entire queue manager OSS directory structure
var_installation_path/var/mqm/qmgrs/qmname.

You must specify the absolute path name of the queue managerÂ’s
directory. Specify the ALLSYMLINKS option for this fileset to
ensure that AutoSYNC correctly synchronizes the symbolic link
(G directory) in the queue manager's directory to the NonStop OS queue
manager's subvolume on the backup system.

Chapter 16 - Troubleshooting

- Page 230: after the section "Is your application or system running
slowly?", insert the following new section:

Are your applications or WebSphere MQ processes unable to connect?

If connection failures are occurring:
- is the User ID under which the application runs authorized to
use this queue manager?
- are SAFEGUARD permissions preventing read access to the WebSphere
MQ installation files by the User ID running the application?
- are the environment variables established for the application
process, so that the correct installation of WebSphere MQ is being
used?
- if necessary, has the application been relinked or rebound with
any static MQI libraries that it uses?
- is a resource problem preventing the queue manager from allowing
the connection? Review the troubleshooting section under TMF
Configuration on Page 185 and 186 for information about the
RMOPENSPERCPU TMF attribute.

Chapter 18 - 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
attribute value of "N" will be overridden 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.

- Page 255: the -nu parameter for setting the default CPUS attribute
in Pathway serverclasses does not accept all the values that Pathway
allows for this attribute. The only accepted values (and the result in
Pathway configuration) are of the form:

-nu value Pathway CPUS attribute
--------- ----------------------
-nu a CPUS (a:0)
-nu a:b CPUS (a:b)

More complex Pathway serverclass CPUS attributes settings must be
configured after the queue manager has been created, using the HP
PATHCOM utility.

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. This supplement has been extensively revised for V5.3.1.1
to clarify the requirements and process for creating and integrating
exits with WebSphere MQ.

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

- Page 431: the content of the ssl directory is revised with V5.3.1.1
as follows:

This directory contains up to four files used by the SSL support:
- The queue manager certificate and private key store (cert.pem)
- The trusted certificates store (trust.pem)
- The pass phrase stash file for the queue managers certificate
and private key store (Stash.sth)
- The certificate revocation list file (optional - crl.pem)

Appendix F - Environment variables

- Page 446: there are several environment variables that are used by the
Guardian sample build scripts to locate the header files and the
libraries. Suitable settings for these are established in the
WMQCSTM file (in the Guardian samples subvolume). The environment
variables, and their meanings, are:

MQNSKOPTPATH^INC^G include file/header subvolume
MQNSKOPTPATH^BIN^G binaries subvolume
MQNSKOPTPATH^LIB^G binaries subvolume
MQNSKOPTPATH^SAMP^G samples subvolume

In addition, an HP environment variable is also required (and set in
WMQCSTM) that locates the OSS DLLs for dynamic loading from Guardian.
The environment variable is ^RLD^FIRST^LIB^PATH.

Appendix H - Building and running applications

Building C++ applications,

Table 47 - there is no multi-threaded library support in
Guardian so there should not be an entry for a
multi-threaded guardian library

Table 48 - the name of this table should be "Native non-PIC"

References to G/lib symbolic links have changed with WMQ 5.3.1 to lib/G

Note that the MQNSKVARPATH and MQNSKOPTPATH environment variables must
be established in the environment, before an application starts up.
They cannot be programmatically set once a program is running by using
putenv().

Page 461: Building COBOL applications

Add the following text:

"In both the OSS and Guardian environment, the CONSULT compiler
directive referencing the MQMCB import library must now be used along
with correct linker options. Refer to the BCOBSAMP TACL script described
in Appendix I for more information."


Appendix I - WebSphere MQ for NonStop Server Sample Programs

Pages 465-466: The section "TACL Macro file for building C Sample Programs"
is replaced by the following:

BCSAMP - Build a C-Language Sample.

This TACL script will compile and link a C-language sample into an
executable program. The script expects that the WMQ environment has
been established using WMQCSTM.

BCSAMP usage:

BCSAMP <type> <source>

<type> The type of executable program that should be built.

Valid values are:

pic A native PIC program
nonpic A native Non-PIC program using the WMQ SRL
Userlibrary (MIPS only)
nonpics A native Non-PIC program using the WMQ SRL
Static Library (MIPS only)
tns A non-native TNS program

<source> The filename of the source module to be compiled and linked

The <source> filename should end with a 'C'. The final program name is
the same as the source filename with the trailing 'C' removed.

Page 467: The section "TACL Macro files for building COBOL Sample
Programs" is replaced by the following:

BCOBSAMP - Build a COBOL Sample.

This TACL script will compile and link a COBOL sample into an executable
program. The script expects that the WMQ environment has been established
using WMQCSTM.

BCOBSAMP usage:

BCOBSAMP <type> <source>

<type> The type of executable program that should be built.

Valid values are:

pic A native PIC program
nonpic A native Non-PIC program using the WMQ SRL
Userlibrary (MIPS only)
nonpics A native Non-PIC program using the WMQ SRL
Static Library (MIPS only)
tns A non-native TNS program

<source> The filename of the source module to be compiled and linked

The <source> filename should end with an 'L'. The final program name is
the same as the <source> filename with the trailing 'L' removed.

Page 469: The section "TACL Macro files for building TAL sample programs"
is replaced by the following:

BTALSAMP - Build a TAL Sample.

This TACL script will compile and link a TAL sample into an executable
program. The script expects that the WMQ environment has been established
using WMQCSTM.

BTALSAMP usage:

BTALSAMP <source>

<source> The filename of the source module to be compiled and linked

The final program name is the same as the <source> filename with the
trailing character removed.

Appendix J - User exits

- refer to the documentation supplement Exits.pdf for updated information
about configuring and building user exits. This supplement has been
extensively revised for V5.3.1.1 to clarify the requirements and process
for creating and integrating exits with WebSphere MQ.

SSLupdate.pdf page 7
-----------------------------------------------------------------------------

The SSLupdate.pdf document was first released with Fixpack 5.3.1.1

The SSL test scripts expect that a default TCP/IP process ($ZTC0) is
configured on the system to be used during the test. The configuration
will need modification if a non-default TCP/IP process does not exist
on the system or another TCP/IP process is used to communicate with the
partner system. The ALICE.sh and/or BOB.sh scripts that setup of the
listener (runmqlsr) will need modification to add the -g option to use a
non-default TCP/IP process.



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/support/entry/portal/Software/WebSphere/WebSphere_MQ) contains
links to a variety of self-help information and technical flashes. The
MustGather Web page
http://www.ibm.com/support/docview.wss?&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://www.ibm.com/support/customercare/sas/f/handbook/home.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 http://www.ibm.com/support/servicerequest.
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.ibm.com/support/docview.wss?&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