IBM Support

WebSphere MQ V5.3 for HP-UX fix pack readme

Product Readmes


Abstract

This documents contains the WebSphere MQ 5.3 for HP-UX fix pack readme. It is cumulative and is updated each time a fix pack is released.

Content

This file contains the following sections:

Installation and maintenance information
Documentation changes
Special information
Service and technical support
Fix pack history


 

########################################################################
#                                                                      #
# COMPONENT_NAME: WebSphere MQ                                         #
#                                                                      #
# FILE: MEMO.PTF                                                       #
#                                                                      #
# Program Number 5724-B41                                              #
# (C) COPYRIGHT International Business Machines Corp. 1995, 2006       #
# All Rights Reserved                                                  #
# Licensed Material - Property of IBM                                  #
#                                                                      #
# US Government Users Restricted Rights - Use, duplication or          #
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.    #
#                                                                      #
########################################################################
 
 
 
PTF Memo for: IBM WebSphere MQ for HP-UX Version 5.3
              Service Level 5.3.0.14 (Fix Pack CSD14)
----------------------------------------------------
 
 
This memo.ptf file contains information you need for updating IBM
WebSphere MQ for HP-UX V5.3 (server and/or client), as well as a
summary of the contents of the latest fix pack and any earlier fix
packs.
 
This is the thirteenth fix pack, corresponding to PTFs U808478 and
U808479, and it is numbered 14.  It will bring your WebSphere MQ for
HP-UX Version 5.3 installation up to service level 5.3.0.14 (PTFs
U808478 and U808479 - fix pack 14).
 
It will bring your WebSphere MQ for HP-UX Version 5.3 installation
filesets up to the following PTF levels:
 
         WebSphere MQ for HP-UX base product         U808478
 
         WebSphere MQ for HP-UX DCE component        U808479
 
All installations require PTF U808478 but PTF U808479 is only required
by installations that use DCE.
 
This fix pack can be used to update the WebSphere MQ for HP-UX V5.3
server.
 
This fix pack can be used to update the WebSphere MQ for HP-UX V5.3
client if you installed the client in one of the following ways:
 
         a) From the IBM WebSphere MQ for HP-UX V5.3 server product
            CD-ROM at the same time as you installed the server.
         b) From the IBM WebSphere MQ for HP-UX V5.3 server product
            CD-ROM without installing the server.
         c) From the WebSphere MQ V5.3 client CD-ROM
         d) By downloading the SupportPac MACX from the web and
            installing it.
 
The memo.ptf file for this fix pack is divided into the following
sections:
 
  o   Installation and maintenance information
 
  o   Documentation changes
 
  o   Special information
 
  o   Service and technical support
 
  o   Fix pack history
 
 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
 
INSTALLATION AND MAINTENANCE INFORMATION
----------------------------------------
 
A) Applying Maintenance
   --------------------
 
  Maintenance updates can be downloaded from the World Wide Web.
 
    ** Precaution **************************************************
    *                                                              *
    *  Do not have queue managers running while you are applying   *
    *  or removing maintenance updates to WebSphere MQ for HP-UX.  *
    *                                                              *
    *  Remove any existing WebSphere MQ shared memory and/or       *
    *  semaphores before applying or removing maintenance updates  *
    *  to WebSphere MQ for HP-UX.                                  *
    *                                                              *
    ****************************************************************
   
 
  Note: For SSL support, upgrade GSKit to the required level before    
  upgrading MQ filesets.  Refer to Section C) "Servicing the IBM Global  
  Security (GSKit) product component" of this memo.ptf file for the
  recommended GSKit version and installation instructions.                                
 
  The instructions for applying maintenance to IBM WebSphere MQ for
  HP-UX can be found in chapter 8 of the manual "WebSphere MQ for
  HP-UX Quick Beginnings" (GC34-6077-00), but must be amended by any
  changes documented in the following section of this memo.ptf file.
 
  If the base package WebSphere MQ for HP-UX V5.3 and a CSD are
  put into the same depot for ease of installation, then the
  following additional instructions are required:
 
     If installing from the command line, the swinstall option
     "autoselect_dependencies=false" will be required when
     installing the CSD.  If it is desired to install both the base
     package and the CSD, then it is required to install the base
     package first, followed by the CSD.  Installation will not
     succeed if the installer attempts to install both in the same
     operation.  If using the interactive installer, the user will
     be required to uncheck the "autoselect dependencies when
     marking software" checkbox under the Options->Change Options
     panel, before selecting the CSD for installation.
 
     Note that if autoselect_dependencies has been turned off, then
     the GSKit package will no longer be automatically installed,
     and the CSD could fail its installation preview if it required
     the updated version of the GSKit package.  This package will
     need to be manually selected in this case.
     
B)NOTE TO USERS OF SUPPORTPAC MA0C                                          
  --------------------------------                                          
  From Fix Pack 8 (CSD08), SupportPac MA0C: WebSphere MQ -              
  Publish/Subscribe, is now incorporated into WebSphere MQ.  If this    
  SupportPac is already installed it must be removed before installing      
  this fix pack.                                                            
                                                                             
  The following files and symbolic links need to be removed:                
                                                                             
  Files:                                                                    
                                                                             
  /opt/mqm/bin/amqfcxaa                                                      
  /opt/mqm/bin/amqfcxba                                                      
  /opt/mqm/bin/clrmqbrk                                                      
  /opt/mqm/bin/dltmqbrk                                                      
  /opt/mqm/bin/dspmqbrk                                                      
  /opt/mqm/bin/endmqbrk                                                      
  /opt/mqm/bin/migmqbrk                                                      
  /opt/mqm/bin/strmqbrk                                                      
  /opt/mqm/samp/bin/amqsgam                                                  
  /opt/mqm/samp/bin/amqspsd                                                  
  /opt/mqm/samp/bin/amqsres                                                  
  /opt/mqm/samp/pubsub/amqsfmda.tst                                          
  /opt/mqm/samp/pubsub/amqsgama.c                                            
  /opt/mqm/samp/pubsub/amqsgama.tst                                          
  /opt/mqm/samp/pubsub/amqspsra.c                                            
  /opt/mqm/samp/pubsub/amqsresa.c                                            
  /opt/mqm/samp/pubsub/amqsresa.tst                                          
  /opt/mqm/samp/pubsub/admin/amqspsda.c                                      
  /opt/mqm/samp/pubsub/admin/amqspsda.tst                                    
                                                                             
  Symbolic links:                                                            
                                                                             
  /usr/bin/amqfcxaa -> /opt/mqm/bin/amqfcxaa                                
  /usr/bin/amqfcxba -> /opt/mqm/bin/amqfcxba                                
  /usr/bin/clrmqbrk -> /opt/mqm/bin/clrmqbrk                                
  /usr/bin/dltmqbrk -> /opt/mqm/bin/dltmqbrk                                
  /usr/bin/dspmqbrk -> /opt/mqm/bin/dspmqbrk                                
  /usr/bin/endmqbrk -> /opt/mqm/bin/endmqbrk                                
  /usr/bin/migmqbrk -> /opt/mqm/bin/migmqbrk                                
  /usr/bin/strmqbrk -> /opt/mqm/bin/strmqbrk                                


 
 
C) Servicing the IBM Global Security (GSKit) product component
   -----------------------------------------------------------
 
     ** Important ***************************************************
     *                                                              *
     *  If you already have the IBM Global Security (GSKit)         *
     *  product installed on your system, then before starting      *
     *  any upgrade of the GSKit product, please ensure that        *
     *  the original package from which you installed your          *
     *  current version is available to you.  This package          *
     *  will be required if you should subsequently decide to       *
     *  downgrade the GSKit back to the level currently on          *
     *  your system.  Without this package, it will NOT be          *
     *  possible to downgrade this service level.                   *
     *                                                              *
     ****************************************************************
 
Please note that the current installed version might not be that which shipped with either the original release of WebSphere MQ V5.3 (service level 5.3.0.0)or the refresh releases of WebSphere MQ V5.3 (service levels 5.3.0.1 and 5.3.0.2), as another product may have upgraded GSKit after the original WebSphere MQ V5.3 installation, or you may have already had another product which installed GSKit at a higher level than the level to be installed with WebSphere MQ V5.3.
 
  In order to determine which version you have currently installed,
  use the following commands:
 
        swlist gsk6bas
 
  The level of GSKit which was distributed with the original release
  of WebSphere MQ V5.3 (service level 5.3.0.0) was "6.0.2.46"
 
  If this is the version you currently have installed, then you will
  find this package on the orignal WebSphere MQ V5.3 install media.
 
  The level of GSKit which was distributed with the refresh releases
  of WebSphere MQ V5.3 (service levels 5.3.0.1 and 5.3.0.2)
  was "6.0.3.33".
 
  If this is the version you currently have installed, then you will
  find this package on the refresh WebSphere MQ V5.3 install media.
 
  The level of GSKit which is distributed with fix pack CSD03 is
  "6.0.3.33".
 
  The level of GSKit which is distributed with fix pack CSD04 is
  "6.0.4.37".
 
  The level of GSKit which is distributed with fix pack CSD06 is
  "6.0.5.39".
 
  The level of GSKit which is distributed with fix pack CSD07 is
  "6.0.5.42".
 
  The level of GSKit which is distributed with fix pack CSD09 is
  "6.0.5.43".
 
   The level of GSKit which is distributed with fix pack CSD12 is
   "6.0-5.45".
 
   The level of GSKit which is distributed with fix pack CSD13 or later is
   "6.0-5.46".
 
  Upgrading and Downgrading the GSKit
  ===================================
 
     ** Precaution **************************************************
     *                                                              *
     *  If you have any programs installed on your system other     *
     *  than WebSphere MQ V5.3 that depend on GSKit, and these      *
     *  programs are currently running, you should stop these       *
     *  programs before performing the GSKit upgrade.               *
     *                                                              *
     ****************************************************************
 
 
  a) Upgrading the GSKit:
 
     From the same directory as the PTF package is in,
     install the package with the command:
 
     swinstall -s $PWD/hp-U808478.v11 gsk6bas
 
 
  b) Downgrading the GSKit:
 
     The downlevel GSKit package can be installed over the top of a
     newer level package, using the "-x allow_downdate=true" option.
     For example, to downgrade to the original level of GSKit, where
     "$PWD/p000-L020617.v11" corresponds to the original tape image
     that shipped with the WebSphere MQ V5.3 media, use the command:
 
     swinstall -x allow_downdate=true -s $PWD/p000-L020617.v11 gsk6bas
 
  Additional Instructions for GSKit key database administration
  -------------------------------------------------------------
  If you are installing fixpack 12 (CSD12) or earlier and you are using SSL
  channels with WebSphere MQ and have installed a later
  GSKit version as part of this CSD (e.g.  you had GSKit version
  6.0.2.20 or 6.0.3.33 and have installed GSKit 6.0.5.45, which is
  supplied as part of fix pack 12) you may need to manually update some
  'jar files' which are used by the GSKit key database administration
  utilities, gsk6cmd and gsk6ikm. If you are installing fix pack 13 or
  later do NOT follow the process below as the fix pack install will have
  already updated the jar files.

  To update the jar files follow the process as described below.
 
  For the following instructions JAVA_DIR and GSKIT_DIR refer to the
  following locations:
 
  On HP-UX 11 JAVA_DIR refers to /opt/mqm/ssl/jre/lib/ext
            GSKIT_DIR refers to /opt/ibm/gsk6/classes/jre/lib/ext
 
  To update the 'jar' files:
 
  1. Back up the files in JAVA_DIR
  2. su to the root user
  3. For each file in GSKIT_DIR, which is also present in JAVA_DIR, copy
     the file from GSKIT_DIR to JAVA_DIR. Note that not all the files
     in GSKIT_DIR are present in JAVA_DIR - you only need to copy the
     files which can be found in both directories.
  4. Ensure the permissions and owner ship of the copied files are the
     same as those on the old files. This can be done using the 'chown'
     and 'chmod' commands:
       chown mqm:mqm JAVA_DIR/*
       chmod 755 JAVA_DIR/*
  5. Log off as root.
 
  You can now use the GSKit administration programs as before.
 
 
 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 

DOCUMENTATION CHANGES
---------------------
 
   o SC34-6062 - WebSphere MQ Application Programming Reference manual
 
     Section: Return Codes "MQRC_MAX_CONNS_LIMIT_REACHED (2025)
     Replace with
 
     MQRC_MAX_CONNS_LIMIT_REACHED (2025)
     Explanation: The MQCONN or MQCONNX call was rejected because
     the maximum number of concurrent connections has been exceeded.
     If Java™ language is in use, this could be because the limit to
     the number of concurrent connections defined by the connection
     manager has been exceeded.
 
     On z/OS, connection limits are applicable only to TSO and batch
     requests.The limits are determined by the customer using the
     following parameters of the CSQ6SYSP macro:
         For TSO:   IDFORE
         For batch: IDBACK
 
     For more information, see the WebSphere MQ for z/OS System Setup
     Guide.
 
     On Compaq OpenVMS Alpha, OS/2, OS/400, Compaq NonStop Kernel,
     UNIX systems, and Windows, this reason code can also occur on
     the MQOPEN call:
           Completion Code: MQCC_FAILED
           Programmer Response: Increase the size of the appropriate
                                install parameter value, reduce the
                                number of concurrent connections,
                                or, if the Java connection manager
                                is responsible, increase the limit.
 
 
   o SC34-6066 - WebSphere MQ Using Java manual
 
     Chapter 1, "Getting Started"
     ============================
     In the section "Prerequisites", add an additional item to the
     end of the list describing publish/subscribe applications as
     follows:
 
         - WebSphere Business Integration Message Broker V5
 
 
 
     Chapter 2 Installation procedures
     =================================
     Section: Running WebSphere MQ Java applications under the Java 2
              Security Manager
     ----------------------------------------------------------------
     End of paragraph three (after bullets) add:
 
     The System property 'os.name' needs to be available to the
     WebSphere MQ Java classes when running under Java 2 Security
     Manager.
 
 
     Example of policy file needs to be replaced with the following:
 
     grant codeBase "file:/opt/mqm/java/lib/com.ibm.mq.jar"
     {
         permission java.net.SocketPermission "*","connect";
         permission java.lang.RuntimePermission "loadLibrary.*";
     };
 
     grant codeBase "file:/opt/mqm/java/lib/com.ibm.mqjms.jar"
     {
         permission java.util.PropertyPermission "MQJMS_LOG_DIR","read";
         permission java.util.PropertyPermission "MQJMS_TRACE_LEVEL","read";
         permission java.util.PropertyPermission "MQJMS_TRACE_DIR","read";
         permission java.util.PropertyPermission "MQ_JAVA_INSTALL_PATH","read";
         permission java.util.PropertyPermission "file.separator","read";
         permission java.util.PropertyPermission "os.name","read";
         permission java.util.PropertyPermission "user.name","read";
         permission java.util.PropertyPermission
     "com.ibm.mq.jms.cleanup","read";
     };
 
 
 
     Chapter 4, "Using WebSphere MQ classes for Java Message Service"
     ================================================================
     In the section "Running the sample applet", SubSection "Running the
     applet as an application", before running the applet using the
     command:
 
        java JMSTestApplet
 
     compile the applet using the command:
 
        javac JMSTestApplet.java
 
 
 
     Chapter 5 Using the WebSphere MQ JMS administration tool
     ========================================================
 
     Section: Administering JMS objects
     Subsection: Properties
 
     Add to Table 11 property names and valid
     ========================================
 
     Property                Shortform       Valid values
     -----------------       ------------    ------------
     LOCALADDRESS            LA              See Below
 
     Valid Values
     ------------
     null
 
     String in the format:   [ip-addr][(low-port[,high-port])]
     examples being:
     9.20.4.98               Channel binds to this address locally
     9.20.4.98(1000)         Channel binds to this address and port 1000 locally
     9.20.4.98(1000,2000)    Channel binds to this address and uses a
                             port in the range 1000 to 2000 locally
     (1000)                  Channel binds to port 1000 locally
     (1000,2000)             Channel binds to port in range 1000 to 2000 locally
 
     Note that it is also possible to provide a hostname in place of the
     dotted IP address, resulting in the same functionality.
 
     For DIRECT connections, this parameter only takes effect when
     multicast is used. For DIRECT connections, this parameter
     cannot have a port specifier, or the connection will be
     rejected, so of the above examples, only 'null' or '9.20.4.98'
     would be valid.
 
 
     Property                Shortform       Valid values
     -----------------       ------------    ------------
     MSGSELECTION            MSEL            CLIENT - Message selection is done by the Client
                                             BROKER - Message selection is done by the Broker
 
 
     Property                Shortform       Valid values
     -----------------       ------------    ------------
     SPARSESUBS              SSUBS           no  - Subscriptions receive frequent matching messages.
                                             yes - Subscriptions receive infrequent matching
                                                   messages. (This setting requires that the
                                                   subscription queue can be opened for
                                                   browse.)
 
     Property                Shortform       Valid values
     -----------------       ------------    ------------
     TEMPQPREFIX             TQP             Any string
 
     Property                Shortform       Valid values
     ----------------------  ------------    ---------------
     DIRECTAUTH              DAUTH           See Below
 
     Valid Values
     ----------------
     BASIC   - None, or username/password authentication
     CERTIFICATE  - Public key certificate authentication
 
     Property                Shortform       Valid values
     ----------------------  ------------    ---------------
     PROXYHOSTNAME           PHOST           Null (default)
                                             String   Name of the proxy hostname
 
     Property                Shortform       Valid values
     ----------------------  ------------    ---------------
     PROXYPORT               PPORT           443 (default)
                                             Any positive integer   Port number of proxy
 
     Property                Shortform       Valid values
     ----------------------  ------------    ---------------
     MULTICAST               MCAST           See Below
 
     Valid Values
     ----------------
     DISABLED  Multicast disabled (default setting for
               TopicConnectionFactory objects)
     NOTR      As 'ENABLED' but will not give a multicast connection
               (used for enabling multicast on legacy applications)
     RELIABLE  Multicast enabled with reliable delivery only
     ENABLED   Multicast enabled if available (may give a reliable
               multicast connection depending on server configuration)
     ASCF      As TopicConnectionFactory setting(default setting for
               Topic objects).  This option is only valid for MQTopic
               objects
 
 
     Add new valid value for TRANSPORT property
     ==========================================
 
     Valid Value
     -------------------
     DIRECTHTTP  - HTTP tunneling for DIRECT connections
 
 
 
     Add note to Table 11 property names and valid
     =============================================
     In certain environments, specifying the same queue name for
     both the brokerDurSubQueue and brokerCCDurSubQueue attributes
     on an MQTopic object can result in a JMSException being thrown.
     It is advised that separate queues are used for these two
     attributes.
 
 
     Add to Table 12 Valid combinations of object and property names
     ===============================================================
 
     Property        QCF     TCF     Q       T       WSQCF  WSTCF    Description
                                                     XAQCF  XATCF
     ------------    ---     ---     -       -       -----  -----    -----------
     LOCALADDRESS    Y       Y                                       see below
 
     Description
     -----------
     The range of local ports to be used when making a connection to an
     MQ queue manager
 
 
     Property        QCF     TCF     Q       T       WSQCF  WSTCF    Description
                                                     XAQCF  XATCF
     ------------    ---     ---     -       -       -----  -----    -----------
     MSGSELECTION                            Y                       see below
 
     Description
     --------------
     Determines whether message selection is done by the JMS Client or by
     the Broker. When using TRANSPORT=DIRECT message selection is always
     done by the Broker and the setting of this parameter is ignored.
     Message selection using the Broker is not supported when the BVER=V1.
     The default value for this parameter is CLIENT.
 
     Property        QCF     TCF     Q       T       WSQCF  WSTCF    Description
                                                     XAQCF  XATCF
     ----------      ---     ---     -       -       -----  -----    -----------
     SPARSESUBS                              Y              Y        Controls the message retrieval
                                                                     policy of TopicSubscribers
 
 
     Property        QCF     TCF     Q       T       WSQCF  WSTCF    Description
                                                     XAQCF  XATCF
     ----------      ---     ---     -       -       -----  -----    -----------
     TEMPQPREFIX     Y       Y                                       see below
 
     Description
     -----------
     The prefix to use when creating temporary/dynamic queues. If
     not specified defaults will be used Default AMQ.* (CSQ.* for
     390). The prefix follows the same rules as WebSphere MQ queue
     names and must have an asterisk at the end of the prefix to
     enable the dynamic part of the name to be generated. The length
     of the prefix is 33 characters or less including the asterisk.
 
     Property        QCF     TCF     Q       T       WSQCF  WSTCF    Description
                                                     XAQCF  XATCF
     ----------      ---     ---     -       -       -----  -----    -----------
     DIRECTAUTH              Y                                       see below
 
     Description
     -----------
     To enable SSL authentication for direct connections.
 
     Notes:
     1. Refer to Appendix D Connecting to other products.
 
 
     Property        QCF     TCF     Q       T       WSQCF  WSTCF    Description
                                                     XAQCF  XATCF
     ----------      ---     ---     -       -       -----  -----    -----------
     PROXYHOSTNAME           Y                                       see below
 
     Description
     -----------
     Name of the proxy host for direct connections.
 
     Notes:
     1. Refer to Appendix D Connecting to other products.
 
 
     Property        QCF     TCF     Q       T       WSQCF  WSTCF    Description
                                                     XAQCF  XATCF
     ----------      ---     ---     -       -       -----  -----    -----------
     PROXYPORT               Y                                       see below
 
     Description
     -----------
     Port number of proxy for direct connections.
 
     Notes:
     1. Refer to Appendix D Connecting to other products.
 
 
     Property        QCF     TCF     Q       T       WSQCF  WSTCF    Description
                                                     XAQCF  XATCF
     ----------      ---     ---     -       -       -----  -----    -----------
     MULTICAST               Y               Y                       see below
 
     Description
     -----------
     To enables multicast on direct connections.
 
     Notes:
     1. Refer to Appendix D Connecting to other products.
 
 
     Section: Sample error conditions
     --------------------------------
     Add to end of section, new paragraph
 
     This section provides examples of error conditions that may
     arise during the use of an object.
 
     On Windows platforms
 
     When looking up JNDI Administered objects from a JMS Client,
     1. If using the WebSphere JNDI Provider
        (com.ibm.websphere.naming.WsnInitiailContextFactory), use
        forward slashes to access administered objects defined in
        sub contexts, for example, jms/MyQueueName. Note if backward
        slash is used InvalidNameException is thrown.
 
     2. If using the Sun JNDI provider
        (com.sun.jndi.fscontext.RefFSContextFactory) use backward
        slashes to access to access administered objects defined in
        sub contexts, for example, ctx1\\fred.  Note if forward
        slash is used NameNotFoundException is thrown.
 
 
 
     Chapter 7 Writing MQSeries base Java programs
     =============================================
     Section: Connection differences
     -------------------------------
     Add to end of section, new SubSection: Specifying a range of ports
 
     A range of local ports to be selected when making a connection to an
     MQ queue manager. This can be used for Java client connections
     through a firewall, where the firewall only accepts connections
     originating from a defined port(s) or range of ports.
 
     This can be set in the following places depending upon the scope of
     definition required.
        1. MQEnvironment.properties
           o    Using the key/value pair MQC.LOCAL_ADDRESS_PROPERTY
        2. MQEnvironment.localAddressSetting
        3. MQJMS Administration Object
           o    Use the Connection Factory property LOCALADDRESS
 
     This property causes the MQInternalCommunications class to bind to a
     port and IP satisfying the property, giving similar functionality as
     the LOCLADDR property available for channels. If an error occurs as
     a result of the local port restrictions then the user receives a
     MQRC_Q_MGR_NOT_AVAILABLE message, containing a message stating
     "Socket connection attempt refused due to LOCAL_ADDRESS_PROPERTY
     restrictions".
 
     Note that this error may be due to the fact that the ports are in
     use or may be because the IP address or ports have been specified
     with incorrect values - for example a negative port number or a host
     name that does not exist.
 
     With JMS applications a range of ports should be used to allow for
     connections required internally and those explicitly used by the
     application, the number of ports required depends on the
     applications and the facilities it uses.  Typically  this will be
     the number of sessions the application uses plus 3 or 4 additional
     ports.  If you encounter errors where connections cannot be made
     the number of ports in the range should be increased.
 
     Note that connection pooling has some bearing on how quickly a
     port can be reused.  JMS uses connection pooling by default,
     hence it may be some minutes before a free port is reused.  In
     the meanwhile connection errors may occur.
 
 
     Section: Connection Pooling
     ---------------------------
     Insert following new paragraph after the third paragraph:
     MQSimpleConnectionManager can be made to limit the number of
     connections which it handles at any one time.  This is useful where
     there are conflicting demands for connections within one JVM.  In
     order to prevent one demand for connections from using too much
     resource, it can be forced to draw its connections from a
     size-limited connection pool so that the performance of the
     connections used by the other demands for connections are not
     downgraded.  By default, getMaxConnections() method returns zero,
     indicating that no limit to the number of connections supported by
     MQSimpleConnectionManager is enforced.  A limit only comes into play
     when setMaxConnections() method is used to change this to a non-zero
     value.
 
     If a limit has been set to the number of connections being handled
     by an instance of MQSimpleConnectionManager, there is a possibility
     that a request for a connection will cause an MQException, with a
     reason code of MQRC_MAX_CONNS_LIMIT_REACHED, to be thrown.
 
     Section: Supplying a different connection pool
     ----------------------------------------------
     Replace the text about application MQApp4
     The following application demonstrates this:
      import com.ibm.mq.*;
      public class MQApp4
      {
          public static void main(String []args)
          {
              MQSimpleConnectionManager myConnMan = new MQSimpleConnectionManager();
              myConnMan.setActive(MQSimpleConnectionManager.MODE_AUTO);
              myConnMan.setTimeout(3600000);
              myConnMan.setMaxConnections(75);
              myConnMan.setMaxUnusedConnections(50);
              MQEnvironment.setDefaultConnectionManager(myConnMan);
              MQApp3.main(args);
          }
      }
 
     The bold lines set up an MQSimpleConnectionManager. This is set to:
        o  destroy connections that have not been used for an hour
        o  limit the number of connections managed by myConnMan to 75
        o  limit the number of unused connections held in the pool to 50
        o  MODE_AUTO (actually the default). This means that the pool is
           active only if it is the default connection manager, and there
           is at least one token in the set of MQPoolTokens held by
           MQEnvironment.
 
     The new MQSimpleConnectionManager
 
     Section: JTA/JDBC coordination using WebSphere MQ base Java
     -----------------------------------------------------------
     Add an extra paragraph to the Usage subsection:
     
     In order to use this functionality you must include the following  
     option in your application:
     MQEnvironment.properties.put( MQC.THREAD_AFFINITY, new Boolean( true ) );
     
 
     Add an extra paragraph to the Known problems and limitations
     subsection:
 
     HP-UX and multiple XAResourceManager stanzas
       
     When attempting to use multiple XAResourceManager stanzas on any  
     given queue manager on HP-UX, the commit call might fail. Treat
     this as an unsupported combination; it does not affect queue  
     managers with a single XAResourceManager stanza.  
 
 
 
     Chapter 9 The WebSphere MQ base classes and interfaces
     ======================================================
 
     Section:MQEnvironment
     ---------------------
     Add to table
 
     Key                             Value
     -----                           -------
     MQC.LOCAL_ADDRESS_PROPERTY      String (overrides MQEnvironment.localAddressSetting)
 
     Add to Variables
     localAddressSetting*
             public static String localAddressSetting
 
     The following value is for storing the value defined for the local address
     property, used to support firewall requirements from base Java and JMS. The
     format of the string is [ip-addr][(low-port[,high-port])] examples being:
             9.20.4.98               Channel binds to this address locally
             9.20.4.98(1000)         Channel binds to this address and port 1000 locally
             9.20.4.98(1000,2000)    Channel binds to this address and
                                     uses a port in the range 1000 to 2000 locally
             (1000)                  Channel binds to port 1000 locally
             (1000,2000)             Channel binds to port in range 1000 to 2000 locally
 
             Note that it is also possible to provide a hostname in place
             of the dotted IP address, resulting in the same
             functionality.
 
     The value is initialized from a system property called
     "com.ibm.mq.localAddress" when starting the JVM.
 
     The default value is null
 
     is then set as the default connection manager.
     
     Section MQException                                            
     -------------------                                            
     Subsection: Methods                                            
     add:                                                            
     two new methods to either suppress or output messages to        
     system.err.                                                    
                                                                     
     to exclude a code from the exception logging routine,          
     i.e... System.err :                                            
                                                                     
         MQException.logExclude(new Integer( RC_value_to_suppress ));
                                                                     
     to include a code later on in the application assuming it has  
     already been excluded :                                        
                                                                     
         MQException.logInclude(new Integer( RC_value_to_include ));
                                                                     
     For example:                                                    
                                                                     
         MQException.logExclude(new Integer( 2033 ));                
 
     Section MQQueueManager
     ----------------------
     SubSection: Constructor
     Constructor: public MQQueueManager(String queueManagerName, ConnectionManager cxManager)
     Add to note:
     If the value of cxManager is null then the default ConnectionManager
     is used.
 
     Section: MQSimpleConnectionManager
     ----------------------------------
     Replace with:
 
     An MQSimpleConnectionManager provides basic connection pooling
     functionality. You can use an MQSimpleConnectionManager either as
     the default Connection Manager, or as a parameter to an
     MQQueueManager constructor. When an MQQueueManager is constructed,
     the most-recently-used connection in the pool is used.
 
     Connections are destroyed (by a separate thread) when they are
     unused for a specified period, when there are more than a specified
     number of unused connections in the pool, or when the maximum
     number of connections has been reached and room is made for new
     connections. You can specify the time out period, the maximum
     number of managed connections and the maximum number of unused
     connections.
 
     Variables
     -----------
      MODE_ACTIVE
          public static final int MODE_ACTIVE . See "setActive" on page xxx.
 
      MODE_AUTO
          public static final int MODE_AUTO . See "setActive" on page xxx.
 
      MODE_INACTIVE
          public static final int MODE_INACTIVE . See "setActive" on page xxx.
 
     Constructors
     ------------
      MQSimpleConnectionManager
          public MQSimpleConnectionManager()
          Constructs an MQSimpleConnectionManager.
 
     Methods
     -------
      getActive
          public int getActive()
          Gets the mode of the connection pool.
          Returns
          The current active mode of the connection pool, with one of the following
          values (see "setActive" on page xxx):
          MODE_ACTIVE
          MODE_AUTO
          MODE_INACTIVE
 
      getHighThreshold (deprecated)
          public int getHighThreshold()
          This should not be used in new applications.  It is synonymous
          with getMaxUnusedConnections and returns the maximum number of
          unused connections in the pool.
 
      getMaxConnections
          public int getMaxConnections()
          Returns the maximum number of connections managed by the connection manager.
 
      getMaxUnusedConnections
          public int getMaxUnusedConnections()
          Returns the maximum number of unused connections in the pool.
 
      getTimeout
          public long getTimeout()
          Returns the Timeout value.
 
      setActive
          public void setActive(int mode)
          Sets the active mode of the connection pool.
 
          Parameters
          mode The required active mode of the connection pool. Valid values are:
 
             MODE_ACTIVE
                The connection pool is always active. When
                MQQueueManager.disconnect() is called, the underlying
                connection is pooled, and potentially reused the next
                time that an MQQueueManager object is constructed.
                Connections are destroyed by a separate thread if they
                are unused for longer than the Timeout period, if the
                size of the pool exceeds the value set by
                setMaxUnusedConnections(), or if room needs to be made
                for a new connection.
 
             MODE_AUTO
                The connection pool is active while the connection
                manager is the default connection manager and there is at
                least one token in the set of MQPoolTokens held by
                MQEnvironment. This is the default mode.
 
             MODE_INACTIVE
                The connection pool is always inactive.  The pool of
                connections to WebSphere MQ is cleared when this mode is
                entered. The connection that underlies any active
                MQQueueManager object is destroyed when
                MQ QueueManager.disconnect() is called,
 
      setHighThreshold (deprecated)
          public void setHighThreshold(int maxUnusedConnections)
          This should not be used in new applications.  It is synonymous
          with setMaxUnusedConnections and sets the maximum number of
          unused connections in the pool.
 
      setMaxConnections
          public void setMaxConnections(int maxConnections)
          Sets the maximum number connections to be managed. In order to
          prevent this number being exceeded, the oldest unused
          connection in the pool may be destroyed or a request for a new
          connection may be refused and an MQException thrown with reason
          code MQRC_MAX_CONNS_LIMIT_REACHED.
 
          Parameters
          maxConnections The maximum number of connections in the pool.
 
      setMaxUnusedConnections
          public void setMaxUnusedConnections(int maxUnusedConnections)
          Sets the maximum number of unused connections in the pool. In
          order to prevent this number being exceeded, the oldest unused
          connection in the pool is destroyed.
 
          Parameters
          maxUnusedConnections The maximum number of unused connections in the pool.
 
      setTimeout
          public void setTimeout(long timeout)
          Sets the Timeout value, where connections that remain unused for this
          length of time are destroyed by a separate thread.
 
          Parameters
          timeout The value of the timeout in milliseconds."
 
     Chapter 10 Writing WebSphere MQ JMS Programs
     ============================================
     Section: Building a connection
     Sub Section: Creating factories at runtime
 
     Add to Table 14 Set methods on MQQueueConnectionFactory
     =======================================================
 
     Method                  Description
     ------                  --------------------------------------------------
     SetTempQPrefix(String)  Set the prefix name from which temporary/dynamic queues will be named on.
 
 
     Section: Sending a message
     Subsection: Table 15
     ==========================
 
     Change description of table 15 from "Property names for queue
     URIs" to "Property names for queues and topic URIs".
 
     Add entry to table 15
     =====================
 
     Property    Description                                 Values
     ----------- ------------------------------------------  -------------
     Multicast   Sets multicast mode for direct connections  See Below
 
     Values
     --------
     -1 = ASCF
      0 = DISABLED
      3 = NOTR
      5 = RELIABLE
      7 = ENABLED
 
     Next to the queue example (just before the table) add
     =====================================================
 
     An example of creating a topic URI is:
       session.createTopic("topic://Sport/Football/Results?multicast=7");
 
 
     Section: Sending a message
     Subsection: Setting properties with the set method
     ===================================================
 
     Add entry to table 16
     =====================
 
     Property  Keyword   Values
     multicast ASCF      JMSC.MQJMS_MULTICAST_AS_CF
               DISABLED  JMSC.MQJMS_MULTICAST_DISABLED
               NOTR      JMSC.MQJMS_MULTICAST_NOT_RELIABLE
               RELIABLE  JMSC.MQJMS_MULTICAST_RELIABLE
               ENABLED   JMSC.MQJMS_MULTICAST_ENABLED
 
 
     Chapter 11 Programming publish/subscribe applications
     =====================================================
 
     Section: Getting started with WebSphere MQ JMS and publish/subscribe
     Sub Section: Choosing a broker
     ====================================================================
 
     Change third bullet to:
     WebSphere MQ Event Broker and WebSphere Business Integration
     Message Broker V5 provide a broker that can be connected to in
     two different ways.
 
 
     Section: Setting up the broker to run the WebSphere MQ JMS
     Sub Section: Connecting to your Broker directly
     ====================================================================
 
     Change first sentence to:
     This is only possible when you use the broker provided in
     WebSphere MQ Event Broker or WebSphere Business Integration
     Message Broker V5.
 
 
     Section: Using Topics
     SubSection: Topic Names
     =======================
 
     Add to Note:
 
     Unicode characters are supported.
 
     Section: Subscriber options
     SubSection: Using message selectors
     ===================================
 
     Add this text at the end of the existing section.
 
     You can control whether the JMS Client or the Broker performs
     message filtering by setting the MessageSelection property on the
     Topic ConnectionFactory. In most cases when the Broker is capable of
     performing message selection it is preferable to make use of this,
     as it reduces the number of messages sent to your Client. However if
     the Broker is very heavily loaded then it may be preferable to move
     this function back onto the Client.
 
 
     Section: Solving publish/subscribe problems
     -------------------------------------------
     SubSection: Topic Names
     Add  New section at the end, as follows:
     "Other Considerations"
 
     When connecting to WebSphere MQ Event Broker V2.1 on a Microsoft
     Windows system, with a large number of JMS clients using TCP/IP sockets
     (that is with a JMSAdmin property type of TRANSPORT(DIRECT)),
     note the following.
 
     If a large number of connections happen almost simultaneously, a
     java.net.BindException Address in use exception might be thrown in
     response to a TopicConnection call. You can try to avoid this by
     catching the exception and retrying, or by pacing the connections.
 
 
     Chapter 14 JMS interfaces and classes
     =====================================
 
     Section: MQConnectionFactory
     ============================
     Add methods
 
     getLocalAddress*
             public String getLocalAddress()
 
             Get method for local address attribute
             Returns
                     String containing the local address in the format
                     [ip-addr][(low-port[,high-port])]
                     examples being
                     9.20.4.98               Channel binds to this address locally
                     9.20.4.98(1000)         Channel binds to this address and port 1000 locally
                     9.20.4.98(1000,2000)    Channel binds to this address and uses a port in the
                                             range 1000 to 2000 locally
                     (1000)                  Channel binds to port 1000 locally
                     (1000,2000)             Channel binds to port in range 1000 to 2000 locally
 
             Note a hostname maybe provided in place of the dotted IP address.
 
     setLocalAddress*
             public void setLocalAddress(java.lang.String x) throws JMSException
 
             Set method for local address attribute
 
             Parameters:
                     x - the local address to be used in the format described above
             Throws:
                     JMSException if local address format incorrect.
 
             A range of ports should be used to allow for connections
             required internally and those explicitly used by the
             application, the number of ports required depends on the
             applications and the facilities it uses.
             Typically  this will be the number of sessions the
             application uses plus  3 or 4 additional ports. If you
             encounter errors where connections can not be made the
             number of ports in the range should be increased.
 
             Note that connection pooling has some bearing on how
             quickly a port can be reused.  In JMS connection
             pooling is switched on by default and it may be some
             minutes before a port if free to be reused and
             connection errors may occur.
 
             For DIRECT connections, this attribute determines which
             of the local network interfaces will be used for
             multicast connections. When setting this parameter for
             a DIRECT connection, you should not specify a port as
             this is not configurable for multicast and will cause a
             failure at connect time.
 
 
     Section: QueueConnectionFactory
     ===============================
     Add methods
 
     getTempQPrefix*
             public String getTempQPrefix()
 
             Get method for temporary queue prefix attribute
             Returns
                     String containing the queue prefix attribute
 
     setTempQPrefix*
             public void setTempQPrefix(java.lang.String tempQPrefix) throws JMSException
 
             Set method for temporary queue prefix attribute
 
             Parameters:
                     tempQPrefix - the prefix to be used when creating temporary/dynamic queues
             Throws:
                     JMSException - prefix is null, empty, greater than 33 characters in length or
                     equal to '*'
 
 
     Section: TopicConnectionFactory
     ===============================
     Add methods
 
     getMessageSelection * $
               public int getMessageSelection()
 
               Get method for message selection attribute.
 
               Returns:
                           The value for the message selection attribute.
 
     GetSparseSubscriptions *
               public boolean getSparseSubscriptions()
 
               Get method for sparseSubscriptions attribute.
 
               Returns:
               The value for the sparsesubscription attribute.
 
     setMessageSelection * $
               public void setMessageSelection(int x)
 
               Set method for message selection attribute
 
               Parameters:
                     An integer indicating whether message selection
                     is done by the Client or the Broker.
                     The constants representing the valid values are:
                            JMSC.MQJMS_MSEL_CLIENT
                            JMSC.MQJMS_MSEL_BROKER
 
     SetSparseSubscriptions *
             public void setSparseSubscriptions(boolean x)
 
             Set method for the sparseSubscriptions attribute. A sparse
             subscription is defined as one which receives infrequent
             matching messages.  The default value of this property is
             false. A value of true may be required if an application
             using sparse subscriptions fails to receive messages because
             of log overflow. Setting sparseSubscriptions to 'true'
             requires the subscription queue to be openable for browse.
 
             Parameter:
             x indicates whether sparse subscriptions are selected.
 
     getDirectAuth*
             public int getDirectAuth();
 
             Get method for direct authentication attribute
 
             Returns:
             An integer corresponding to the current direct
             authentication type
 
     getProxyHostName*
             public String getProxyHostName();
 
             Get method for hostname attribute
 
             Returns:
             The name of the hostname to be used as a proxy when
             performing DIRECT connections, or null if no proxy is
             to be used.
 
     getProxyPort*
             public int getProxyPort();
 
             Get method for proxy port attribute
 
             Returns:
             The port to connect to on the proxy host.
 
     getMulticast*
             public int getMulticast();
 
             Get method for multicast attribute
 
             Returns:
             An integer corresponding to the current multicast
             setting
 
     setDirectAuth*
             public void setdirectAuth( int x ) throws JMSException;
 
             Set method for direct authentication attribute
 
             Parameters:
             An integer representing one of the valid direct
             authentication values as represented by one of these
             constants:
                JMSC.MQJMS_DIRECTAUTH_BASIC
                JMSC.MQJMS_DIRECTAUTH_CERTIFICATE
 
     setProxyHostName*
             public void setProxyHostName(String x ) throws JMSException;
 
             Set method for proxy hostname attribute
 
             Parameters:
             proxyHostName: the name of the host to be used a proxy
             when establishing a direct connection, or 'null' if no
             proxy is to be used
 
     setProxyPort*
             public void setProxyPort(int  x ) throws JMSException;
 
             Set method for proxy port attribute
 
             Parameters:
             proxyPort: the port number on the proxy host to connect
             to.
 
     setMulticast*
             public void setDirectAuth( int x ) throws JMSException;
 
             Set method for multicast attribute
 
             Parameters:
             An integer representing one of the valid multicast
             values as represented by one of these constants:
                JMSC.MQJMS_MULTICAST_DISABLED
                JMSC.MQJMS_MULTICAST_NOT_RELIABLE
                JMSC.MQJMS_MULTICAST_RELIABLE
                JMSC.MQJMS_MULTICAST_ENABLED
 
 
     Section: ConnectionFactory
     ==========================
     Amend Method setTransportType*
 
     Add new transport type:
        JMSC.MQJMS_TP_DIRECT_HTTP
 
 
     Section: Topic
     ==============
     Add methods
 
     getMulticast*
             public int getMulticast();
 
             Get method for multicast attribute
 
             Returns:
             Multicast attribute value. This will be one of the
             constants.
                JMSC.MQJMS_MULTICAST_AS_CF
                JMSC.MQJMS_MULTICAST_DISABLED
                JMSC.MQJMS_MULTICAST_NOT_RELIABLE
                JMSC.MQJMS_MULTICAST_RELIABLE
                JMSC.MQJMS_MULTICAST_ENABLED
 
     setMulticast*
             public void setMulticast(int x ) throws JMSException;
 
             Set method for multicast attribute
 
             Parameters:
             An integer representing one of the valid multicast
             values. These are represented by the constants:
                JMSC.MQJMS_MULTICAST_AS_CF
                JMSC.MQJMS_MULTICAST_DISABLED
                JMSC.MQJMS_MULTICAST_NOT_RELIABLE
                JMSC.MQJMS_MULTICAST_RELIABLE
                JMSC.MQJMS_MULTICAST_ENABLED
 
             Throws:
             JMSException - parameter x invalid
 
 
 
     Appendix A. Mapping between Administration tool properties and programmable properties
     ======================================================================================
 
     Add to Table 37 new property names
     ==================================
 
 
     Property        Member                  Tool                    Program
                     variable name           property values         property values
     --------        -------------           ---------------         ---------------
     LOCALADDRESS    localAddress
 
 
     Property        Member                  Tool                    Program
                     variable name           property values         property values
     --------        -------------           ---------------         ---------------
     SPARSESUBS      sparseSubscriptions     YES                     true
                                             NO                      false
 
     Property        Member                  Tool                    Program
                     variable name           property values         property values
     --------        -------------           ---------------         ---------------
     DIRECTAUTH      directAuth              See below               See below
 
     Tool             Program
     property values  property values
     ---------------  ---------------
     BASIC            JMSC.MQJMS_DIRECTAUTH_BASIC
     CERTIFICATE       JMSC.MQJMS_DIRECTAUTH_CERTIFICATE
 
 
     Property        Member                  Tool                    Program
                     variable name           property values         property values
     --------        -------------           ---------------         ---------------
     MULTICAST       multicast               See below               See below
 
     Tool             Program
     property values  property values
     ---------------  ---------------
     DISABLED         JMSC.MQJMS_MULTICAST_DISABLED
     NOTR             JMSC.MQJMS_MULTICAST_NOT_RELIABLE
     RELIABLE         JMSC.MQJMS_MULTICAST_RELIABLE
     ENABLED          JMSC.MQJMS_MULTICAST_ENABLED
     ASCF             JMSC.MQJMS_MULTICAST_AS_CF
 
     Property        Member                  Tool                    Program
                     variable name           property values         property values
     --------        -------------           ---------------         ---------------
     PROXYHOSTNAME   proxyHostName
     PROXYPORT       proxyPort
 
 
     Appendix D.  Connecting to other products
     =========================================
 
     Section: Setting up a publish/subscribe broker
     ==============================================
 
     Add new sub Section
     Direct connect to WebSphere Business Integration Broker V5
     ----------------------------------------------------------
     For this, set a message flow within an execution group on
     WebSphere Business Integration Broker V5. This message flow
     reads messages from the TCP/IP socket on which the broker is
     listening.
 
     The basic message flow consists of a Real-timeOptimizedFlow set
     to listen on the port configured for direct connections. By
     default, this port is 1506.
 
 
     Add new Section: WebSphere Business Integration Broker V5
     Add SubSection:
     =========================================================
 
     JMS can now connect to the WebSphere Business Integration
     Broker V5.  The range of functions expands on those available
     with WebSphere MQ Event Broker with the following additions for
     direct connections (TCP/IP) to the broker:
 
     1) Authentication using a public key certificate
     2) Multicast
     3) HTTP Tunnelling and Connect via Proxy
 
     Details on these functions can be found in the WebSphere
     Business Integration Broker V5 Information Center. The
     following describes how the JMS client configuration parameters
     can be configured.
 
     1. Support for SSL authentication
        ------------------------------
 
        JMS client connection to the broker provides both server
        authentication and mutual (or client) authentication.
 
        This is NOT a full SSL implementation and is not the same as
        connecting to WebSphere MQ using the SSLCIPHERSUITE option -
        SSL is not used to encrypt or perform integrity checks on
        the data when connecting to WebSphere Business Integration
        broker.
 
        The difference between the behaviour of WebSphere MQ SSL and
        this SSL authentication option is that the former uses SSL
        for the lifetime of the connection, thereby providing
        link-level encryption as well as authentication; the latter
        only uses SSL in order to accomplish authentication and
        establish a session key; messages may then be protected on a
        per-topic basis. If encryption is required it needs to be
        set up using the QoP options on the broker. The certificates
        used for this are the same as are required as for full SSL.
 
        This is configured either:
        i)  Programmatically by getDirectAuth/setDirectAuth methods
            on MQConnectionFactory.
        ii) Administratively using JMSAdmin to set the property
            DIRECTAUTH.
 
        Notes:
        1. If the TRANSPORT property is set to the value DIRECT,
           then a new DIRECTAUTH property is examined to determine
           whether SSL authentication should be used.
 
        2. The SSLPEERNAME and SSLCRL properties can be used to
           perform the same checks as for MQ CLIENT SSL connections
           when DIRECTAUTH is set i.e.setting DIRECTAUTH enables the
           SSLPEERNAME and SSLCRL options in the same way as
           SSLCIPHERSUITE does for MQ SSL
 
        3. The JSSE KeyStore and TrustStore configuration will
           determine the client's certificate and acceptable server
           certificates respectively, in the same way as for MQ
           CLIENT connections.
 
 
     2. Multicast
        ---------
 
        JMS client multicast connection to the broker can be
        configured either:
        i)  Programmatically by getMulticast and setMulticast
            methods on MQTopicConnectionFactory or MQTopic.
        ii) Administratively using JMSAdmin to set the property
            MULTICAST.
 
        Note: The TRANSPORT property must be set to DIRECT before
              the MULTICAST property will have any effect.
 
 
     3. HTTP Tunnelling and Connect-via-Proxy
        -------------------------------------
 
        JMS client can now connect via HTTP tunneling and
        connect-via-proxy.
 
        HTTP Tunnelling
        This is suitable for use in applets, where, due to sandbox
        security, an attempt to connect explicitly to the HTTP proxy
        server would be rejected.  HTTP tunneling exploits the web
        support built into browsers and connects through the proxy
        as if it were connecting to a web site. This is configured:
 
        i)  Programmatically using a new value of TransportType
            property on MQConnectionFactory of
            JMSC.MQJMS_TP_DIRECT_HTTP.
        ii) Administratively using JMSAdmin to set the property
            TRANSPORT to DIRECTHTTP.
 
        Note that HTTP tunnelling cannot be used in combination with
        SSL Authentication.
 
        Connect-via-Proxy
        This is suitable for use in non-applets where there is no
        "sandbox" security restriction.  It connects directly to the
        proxy and uses the Internet protocol defined in RFC 2817 to
        request that the proxy forward the connection to the broker.
        This option does not work in applets, where the security
        manager will normally reject the explicit connection to the
        proxy. This is configured:
 
        i)  Programmatically using the get/set methods on
            MQTopicConnectionFactory.
        ii) Administratively using JMSAdmin to set the properties
            PROXYHOSTNAME and PROXYPORT.
 
        Connection type
        The type of connection formed depends on the value of
        ProxyHostName and that of TransportType:
        - If ProxyHostName is  set to the empty string, then
          connections are made directly to the hostname and port
          specified in the HostName and Port properties.
        - If ProxyHostName is set to a non-empty value, and
          TransportType is set to DIRECT, then connect-via-proxy
          behaviour is used with the proxy host name and port taken
          from the ProxyHostName and ProxyPort properties;
        - If TransportType is set to any value other than DIRECT,
          then connections are made directly to the hostname and port
          specified in the HostName and Port properties.
 
 
   o 60225   - The WebSphere MQ Extended Transactional Clients book
 
     The WebSphere MQ Extended Transactional Clients book is
     supplied in Adobe Acrobat PDF format on the WebSphere MQ
     Extended Transactional Clients CD-ROM.  The book is in the file
     csqzar00.pdf, which is in the root directory of the CD-ROM.

 
   o SC34-6059 - WebSphere MQ Intercommunication
 
     Part 7. Further intercommunication considerations
     =================================================
     Chapter 46. Channel-exit programs
     =================================                                
     Section: Writing and compiling channel-exit programs
     ----------------------------------------------------
     Subsection: WebSphere MQ for HP-UX                                
                                                                       
     CHANGE FROM:                                                      
     ================================================================  
     Figure 141. Sample compiler and loader commands for channel      
     exits on HP-UX                                                    
     $ c89 -c +z +e exit.c                                            
     $ ld -o exit exit.o +b : -c exit.exp +IMQStart +eMQStart -b      
     $ cp exit /usr/xmp/lib # (or wherever you require)                
     ================================================================  
                                                                       
     TO:                                                              
     ================================================================  
     Figure 141. Sample compiler and loader commands for channel      
     exits on HP-UX                                                    
     $ c89 -c +z +e exit.c                                            
     $ ld -o exit.sl +b /opt/mqtest/lib:/opt/mqm/lib:/usr/lib +s -e    
     MQStart exit.o -L/opt/mqm/lib -b                                  
                                                                       
     #To make an exit thread-safe (POSIX Draft 10 pthreads)            
     $ ld -o exit.sl +b /opt/mqtest/lib:/opt/mqm/lib:/usr/lib +s -e    
     MQStart exit.o -L/opt/mqm/lib -lpthread -b                        
                                                                       
     $ cp exit /usr/xmp/lib # (or wherever you require)                
     ================================================================  
     NOTE: Refer to "Linking libraries" under "Building your          
     application on HP-UX" of Application Programming Guide for more  
     details.                                                          
     ================================================================  
                                                                       
     The above "NOTE" is added just after the "Figure 141.". Please    
     note that this is not part of the figure.                        
 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 

SPECIAL INFORMATION
-------------------
 
A) Fix Pack CSD14 (PTFs U808478 and U808479)
   -----------------------------------------
This fixpack includes a change which may improve the performance of a
multithreaded C++ application. Prior to this change, MQPUT operations
may serialize - ie if 2 threads issue MQPUT together then one may wait
for the other to complete - This is most visible when running in client
bindings as the MQPUT flows involve network I/O. This change can potentially mean that the WMQ Server experiences a higher workload than it would previously have done because more multiple concurrent calls can now be in effect.
   
In most cases this is the desired behaviour, as it improves the throughput but the previous behaviour can be restored by setting an environment variable 'AMQ_CPP_LOCK_ON_PUT' to any value.
   
B) Fix Pack CSD13 (PTFs U804874 and U804875)
   -----------------------------------------
   There is no special information for this fix pack.
   
C) Fix Pack CSD12 (PTFs U803577 and U803578)
   -----------------------------------------
   There is no special information for this fix pack.
   
D) Fix Pack CSD11 (PTFs U802131 and U802132)
   -----------------------------------------
   There is no special information for this fix pack.
   
E) Fix Pack CSD10 (PTFs U800392 and U800449)
   -----------------------------------------
   XAOpenString
   ------------
   Support for an escape character in the XAOpenString parameter of a
   XAResourceManager stanza is added.
   
   '\' has been introduced to allow ';' and '#' characters to be        
   specified.  This allows the strings '\;' or '\#' to be used to      
   specify these characters.  If an existing parameter includes a '\'  
   character, but this is not followed by either a ';' or '#' character,
   then the interpretation of this parameter will not change following  
   application of this fix pack.
   
   ';' and '#' characters may be required in Informix database xa_open
   strings.                                            
   
F) Fix Pack CSD09 (PTFs U498684 and U498685)
   -----------------------------------------
   There is no special information for this fix pack.
   
G) Fix Pack CSD08 (PTFs U497534 and U497535)
   -----------------------------------------
o  SupportPac MA0C: WebSphere MQ - Publish/Subscribe.
   -------------------------------------------------

   This SupportPac is now incorporated into WebSphere MQ. See the
   install section above for instructions on how to install this Fix
   Pack if you have installed the MA0C SupportPac.
   
o  JMS Performance changes
   -----------------------

   0. Introduction.                                                                                
   ================                                                                                
   WebSphere MQ V5.3 CSD8 for distributed platforms introduces an      
   additional set of tuning options that can be used to enable improved
   JMS publish/subscribe performance in selected persistent messaging  
   scenarios.                                                          
                                                                       
   Significant performance improvements are possible in suitable JMS                              
   publish subscribe environments which make heavy use of persistent    
   messages and exhibit a low degree of concurrent activity.            
                                                                                                   
   1. JMS configuration                                                                            
   ====================                                                                            
      Four new properties are added to the ConnectionFactory and                                    
      TopicConnectionFactory administrable objects.                                                
      These are settable through the JMSAdmin tool.                                                
      Getter and setter methods are provided on the MQSession object to
      allow the setting of these properties to be more finely tuned,    
      however it is recommended that these attributes are managed      
      through the administrable objects where possible.                
                                                                                                   
      The four new properties are:                                                                  
                                                                                                   
      ReceiveIsolation                                                                              
      ----------------                                                                              
      ReceiveIsolation is used to determine when messages can be seen
      and dealt with by MessageConsumers.                                                                    
                                                                                                   
      ReceiveIsolation is an integer attribute and valid values are:                              
      JMSC.MQJMS_RCVISOL_COMMITTED                                                                  
           The MessageConsumer will only see committed messages.                                    
           This is the current default behaviour.                                                  
      JMSC.MQJMS_RCVISOL_UNCOMMITTED                                                                
           The MessageConsumer is able to receive uncommitted messages.
           Although the MessageConsumer may be given visibility to an  
           uncommitted message it will not be allowed to commit such a  
           message unless the producer also commits.  This option should
           only be used if the effect of the message is not made visible
           outside the MQ recovery domain before the commit completes.  
           Note that setting this option ALLOWS the queue manager to    
           deliver an inflight message to a consumer, but that it does  
           not REQUIRE the queue manager to make inflight messages      
           available to a consumer.                                    
                                                                                                   
      JMSAdmin configuration data for this attribute:                                              
      JMSAdmin longname: RECEIVEISOLATION                                                          
      JMSAdmin shortname: RCVISOL                                                                  
      JMSAdmin values: COMMITTED / UNCOMMITTED / DEFAULT                                            
                                                                                                   
                                                                                                   
                                                                                                   
      ProcessDuration                                                                              
      ---------------                                                                              
      ProcessDuration allows the consumer to indicate how long it will  
      take in dealing with any received message before acknowledging it.
      ProcessDuration is an integer attribute and valid values are:                                
                                                                                                   
      JMSC.MQJMS_PROCESSING_UNKNOWN                                                                
           It is not known how long the consumer will hold the message  
           before acknowledging the message.  This is the current      
           default behaviour.                                                                      
                                                                                                   
      JMSC.MQJMS_PROCESSING_SHORT                                                                  
           The consumer will acknowledge the message after a 'short'    
           interval.  Setting MQJMS_PROCESSING_SHORT allows the queue  
           manager to deliver the message synchronously to an active    
           consumer.  In conjunction with MQJMS_RCVISOL_UNCOMMITTED this
           option can enable synchronous delivery in a transactional                                
           environment.  If the queue manager delivers the message      
           synchronously and the consumer does NOT acknowledge the      
           message after a 'short' interval then the flow of                                        
           publications through this queue manager may be interrupted.  
                                                                                                   
      JMSAdmin configuration data for this attribute:                                              
      JMSAdmin longname: PROCESSDURATION                                                            
      JMSAdmin shortname: PROCDUR                                                                  
      JMSAdmin values: UNKNOWN / SHORT / DEFAULT                                                    
                                                                                                   
                                                                                                   
      OutcomeNotification                                                                          
      -------------------                                                                          
      OutcomeNotification will determine whether the MessageConsumer    
      needs to be informed of the outcome of a Message acknowledgement  
      (or a Session.commit() in a transacted Session).                  
                                                                       
                                                                                                   
      OutcomeNotification is a boolean attribute and valid values are:                              
      YES                                                                                          
          When a message is acknowledged the MessageConsumer will be    
          informed whether the Message has successfully committed or    
          been rolled-back.  This is the current default behaviour.                                
                                                                                                   
      NO                                                                                            
          When a message is acknowledged the MessageConsumer will not be
          informed of whether the Message has successfully committed or
          been rolled-back (though the result will still be one or the  
          other, as before).  Applications for which the correct        
          response to a rolled back exception is to ignore the exception                            
          can typically use this option.  For example a server          
          application which receives a message, sends a reply, and      
          commits can typically safely use this option.  In the event of
          the transaction rolling back then the original request message
          will be reinstated with the BackoutCount incremented and      
          presented to the application on its next receive to be        
          reprocessed.                                                  
                                                                       
                                                                                                   
      JMSAdmin configuration data for this attribute:                                              
      JMSAdmin longname: OUTCOMENOTIFICATION                                                        
      JMSAdmin shortname: NOTIFY                                                                    
      JMSAdmin values: YES / NO                                                                    
                                                                                                   
                                                                                                   
      OptimisticPublication                                                                        
      ---------------------                                                                        
      OptimisticPublication allows the queue manager to defer some error
      checking when a transacted MessageProducer/TopicPublisher produces
      a message.  OptimisticPublication is a boolean attribute and valid
      values are:                                                      
                                                                       
      NO                                                                                            
          The queue manager will validate the publication request before
          control is returned to the message producer.  This is the    
          current default behaviour.                                                                
                                                                                                   
      YES                                                                                          
          This allows the queue manager to overlap processing the      
          message in the interval between producing the message and    
          committing the message.  In the case where the message can be                            
          delivered synchronously to one or more consumers (as a result
          of MQJMS_RCVISOL_UNCOMMITTED and MQJMS_PROCESSING_SHORT) then
          if one or more of those consumers rolls back its transaction  
          then the producers transaction will also roll back.          
                                                                                                   
      JMSAdmin configuration data for this attribute:                                              
      JMSAdmin longname:  OPTIMISTICPUBLICATION                                                    
      JMSAdmin shortname:  OPTPUB                                                                  
      JMSAdmin values:  NO / YES                                                                    


   2. Broker configuration
   =======================

   A. WebSphere MQ publish subscribe broker
      -------------------------------------

      JmsStreamPrefix='string'

      This is an attribute of the WebSphere MQ publish subscribe broker
      and is specified in the "Broker:" configuration stanza.  All      
      streams whose names begin with the JmsStreamPrefix are restricted
      to JMS semantics.  In particular they do not support retained    
      messages and relative message ordering is not guaranteed across  
      publishers.  The WebSphere MQ publish subscribe broker optimizes  
      processing of publications which are restricted to JMS semantics.
                                                                       
      There is no default value for this attribute.
   
      For example, JmsStreamPrefix=JMS could be specified to indicate  
      that the streams 'JMS.STREAM.PURCHASE' and 'JMS.STREAM.SALES' were
      both restricted to JMS semantics.                                
   
   B. WebSphere MQ Message Broker
      The SupportPac, "WebSphere Business Integration Message Broker -  
      MQOptimizedFlow Node ( IA0Z )" will enable you to install a new  
      node into the message brokers toolkit which provides a            
      Publish-Subscribe message flow for MQ-JMS messages optimized for  
      use in the environments described above.                          

   3. Conclusion                                                                          
   ==============                                                                        
   In a trivial publish subscribe benchmark where a single consumer      
   consumes all messages produced by a single producer then performance  
   improved by over 100% by setting MQ_RCVISOL_UNCOMMITTED,              
   MQJMS_PROCESSING_SHORT,outcomeNotification=NO,                                          
   OptimisticPublication=YES and by using a stream whose name started    
   with the JmsStreamPrefix of the WebSphere MQ publish/subscribe      
   broker.  This test was run in an environment where a high performance
   disk cache was active.  In an environment with higher latency disks  
   then a greater improvement would be likely.  In more sophisticated    
   benchmarks then the cost of reliable I/O can usually be amortized    
   across a large number of producers and consumers and the potential  
   performance benefits of a more synchronous implementation are        
   typically outweighed by the reduced application independence such a  
   design imposes.                                                      
                                                                       
                                                                         
                                                                         

   
H) Fix Pack CSD07 (PTFs U496730 and U496758)
   -----------------------------------------
   There is no special information for this fix pack.
   
I) Fix Pack CSD06 (PTFs U489864 and U489997)
   -----------------------------------------
   
 o SSL:
 
   In January 2004 some certificates supplied as part of the default    
   Queue Manager Key Repository expired.  The certificates were          
   automatically inserted into key databases at key database creation      
   time.  These expired certificates affect the UNIX platforms and the      
   Windows platform in slightly different ways, so please see the        
   appropriate section below for actions you need to take.              
                                                                           
   Expired certificates on the UNIX Platforms                              
   ==========================================                              
   On the UNIX Platforms the following two certificates are affected by    
   this:                                                                    
                                                                           
   The certificate labelled                                                
     'VeriSign Class 3 CA Individual Subscriber-Persona Not Validated'      
   which expired on the 7th January and                                    
                                                                           
   The certificate labelled                                                
     'VeriSign Class 2 CA-Persona Not Validated'                            
   which expired on the 6th January                                        
                                                                           
   The expired certificates impact MQ and GSKit (the program used on        
   UNIX platforms to administer certificates) in two ways:                  
                                                                           
   1. SSL connections requiring one of the recently expired certificates    
      to authenticate personal certificates will fail.                      
   2. Due to a GSKit defect it may be impossible to create new key          
      databases.                                                            
                                                                           
   This CSD provides a new version of GSKit which contains a fix for        
   problem 2 so the expired certificate no longer prevent the creation  
   of a key database.  The newly created key databases will also include
   the replacement (valid) certificates from Verisign, which addresses      
   problem 1.                                                              
                                                                           
   Customers who are already using these certificates to validate          
   connections will not be affected by problem 2 (they have already        
   created the key database) but they will need to manually upgrade the    
   certificate to the valid versions to address problem 1.  The          
   replacement certificates can be obtained from Verisign and inserted  
   into the key database using the steps described below:                
                                                                           
   Step One - Obtain the replacement certificates. Customers need to        
   contact VeriSign who should provide instructions for obtaining          
   currently valid certificates.                                            
                                                                           
   Step Two - Put the replacement certificates into the keystore:            
   2.1. Start iKeyman                                                        
   2.2. Open keystore                                                        
   2.3. Select "signer certificates"                                          
   2.4. Click add certificate.                                                
   2.5. Select type "Base64-encode ASCII data"                                
   2.6. Enter the file name saved in Step One above and click OK or use  
        the "Browse" button to select the file saved in Step One and    
        click Open followed by OK.                                      
   2.7. There will be a pop-up window to enter a label for the new            
        certificate. Enter a label (e.g., Verisign Class 3) and click OK.    
   2.8. Repeat for all required certificates                                  
   2.9. End iKeyman or close the keystore.                                    
   2.10. Recycle the queue manager to pick up the new certificates.          
                                                                           
   Expired certificates on the Windows Platform                            
   ============================================                            
   On the Windows platform the following three certificates are affected    
   by this:                                                                
                                                                           
   The certificate labelled/issued to                                      
     'VeriSign Class 3 CA Individual Subscriber-Persona Not Validated'      
   which expired on the 7th January and                                    
                                                                           
   The certificate labelled/issued to                                      
     'VeriSign Class 2 CA-Persona Not Validated'                            
   which expired on the 6th January and                                    
                                                                           
   The certificate labelled/issued to                                      
     'For VeriSign authorized testing only. No assurances (C)VS 1997'      
   which expired on the 4th March 2003.                                    
                                                                           
   The expired certificates impact MQ because SSL connections requiring    
   one of these CA certificates to authenticate personal certificates  
   will fail.                                                                    
                                                                           
   Customers who are using these certificates to validate connections    
   will need to manually upgrade the certificate to the valid versions.  
   The replacement certificates can be obtained from Verisign and          
   inserted into the key database using the steps described below:          
                                                                           
   Step One - Obtain the replacement certificates. Customers need to        
   contact VeriSign who should provide instructions for obtaining          
   currently valid certificates.                                            
                                                                           
   Step two - Put the replacement certificates into the keystore:          
    1. Open MQ Explorer                                                    
    2. Right click the Queue Manager that requires the updated              
       certificates. Select 'Properties'                                    
    3. Click the 'SSL' tab                                                  
    4. Click the 'Manage SSL Certificates...' button                        
    5. Click the 'Add...' button                                            
    6. Select the location where the certificates are (either a file or    
       copy them from another store - depending on how you obtained the    
       certificates from Verisign)                                          
    7. Click 'Add'                                                          
    8. Repeat for all required certificates                                
    9. Close the MQ Explorer GUI windows.                                  
 
 
   Importing Certificates
   ======================
   There is a problem with the GSKit command 'gsk6cmd' which may affect  
   customers who edit key databases from the command line on UNIX.  You  
   may need to edit the GSKit file 'ikminit.properties' to change the    
   stanza DEFAULT_KEYDB_LOCATION_CMS from '.' to blank ('') - or comment
   this line out with a '#' character.  If you do not do this GSKit may  
   place a '.' in front of the location of a key database which you are
   editing which can cause problems, especially if you fully qualify the
   path to the key database.  You can find the 'ikminit.properties' file
   in the following platform dependant locations:                        
 
   AIX /usr/opt/ibm/gskak/classes
   HP11 /opt/ibm/gsk6/classes
   Linux /usr/local/ibm/gsk6/classes
   Solaris /opt/ibm/gsk6/classes
 
 
 o New Queue Attribute
 
   This WebSphere MQ V5.3 update introduces a new queue attribute
   NPMCLASS which applies to local and model queues.  NPMCLASS can
   take one of two values:
 
   1.NPMCLASS(NORMAL)  -  This is the default value and indicates
     that non-persistent messages on this queue are only lost following
     a failure, or a queue manager shutdown.  These messages will be
     discarded in the event of a queue manager restart.
 
   2.NPMCLASS(HIGH) - This setting enables non-persistent messages on
     this queue to be retained across a queue manager restart.
     Non-persistent messages may still be lost in the event of a
     failure.
 
   The WebSphere MQ V5.3 JMS classes are extended to allow exploitation
   of the NPMCLASS queue attribute.  This is done by adding a new value,
   JMSC.MQJMS_PER_NPHIGH, to the list of persistence modes accepted by
   the Destination.setPersistence(int persistence) method.  If this
   value is set and the underlying queue(s) supports it, then persistent
   JMS messages will be mapped to non-persistent (MQPER_NOT_PERSISTENT)
   MQ messages.  If the underlying queue(s) do not specify
   NPMCLASS(HIGH), then persistent JMS messages will map to persistent
   (MQPER_PERSISTENT) MQ messages.
 
   In order to determine if the underlying queue supports NPMCLASS then
   when JMSC.MQJMS_PER_NPHIGH is specified the JMS classes will issue
   an MQINQ against the base queue.  JMSC.MQJMS_PER_NPHIGH should not
   be specified when the JMS application is not authorized to inquire
   upon the base queue.
 
   It is the administrator's responsibility to ensure that all
   appropriate queues specify NPMCLASS(HIGH). Note that for  
   Publish/Subscribe applications, both the publisher and subscriber  
   queues must be specify NPMCLASS(HIGH).
 
   For maximum reliability it is advised that the JMS Persistent
   attribute is mapped to WebSphere MQ persistence rather than use of
   JMSC.MQJMS_PER_NPHIGH.
 
 
 o JMS1.1
 
   WebSphere MQ classes for Java Message Service (also referred to as
   WebSphere MQ JMS) are a set of Java classes that implement Sun's Java
   Message Service (JMS) interfaces to enable JMS programs to access
   WebSphere MQ systems.  This WebSphere MQ V5.3 update implements
   Version 1.1 of the JMS API specification, which is backwards
   compatible with Version 1.0.2b.  Both the point-to-point and
   publish/subscribe models of JMS are supported.  New features of the
   Version 1.1 implementation are shown here:
 
   Provides a common set of interfaces for a domain independent view of
   both the point-to-point and publish/subscribe messaging domains,
   Semantic differences between the messaging domains are retained,
   Enables actions from both the point to point and publish/subscribe
   domains to be included in the same transaction, Domain unification
   provides a simplified client programming model.  JMS 1.1 cross-domain
   objects can only be used where both point-to-point and
   publish/subscribe use the same connection properties
 
 
   For more details, refer to the "WebSphere MQ Using Java" book, book
   form number SC34-6066-02 included with this fix pack.  This is in
   file csqzaw12.pdf which is contained within the download CSD image
   file (for example U489864.gskit.tar.Z for the CSD06 image file),
   along with the HP-UX CSD install image file.
   
   There is a minor error in this version of the Using Java book:
   In Chapter 10, "Writing WebSphere MQ JMS applications" and
   Chapter 12, "Writing WebSphere MQ JMS 1.1 applications"
   In the section "Specifying a range of ports for client connections",
   the last sentence of the first paragraph should contain the phrase  
   "... or a range of ports ...",  
   and not "... or a range of points ...".  
 
   For JMS1.0.2 applications that use accessor methods on                
   ConnectionFactory objects and are compiled using a Java SDK1.3        
   compiler and are to be deployed on BOTH WebSphere MQ V5.3 CSD06 or    
   later and WebSphere MQ V5.3 CSD05 or earlier, special measures are    
   required to ensure correct execution in both environments.  Failure  
   to do this might result in a NoSuchMethodError exception being thrown
   by the JVM.                                                          
 
   To avoid this either:
   - compile the application using the CSD05, or earlier, version of the  
     WebSphere MQ classes for JMS.                                      
   - or compile the application using Java SDK1.4 or later on either  
     environment.  
 
  o JTA/XA support.
 
   New support is introduced in this WebSphere MQ V5.3 update to provide
   JTA/JDBC coordination using WebSphere MQ base Java on the HP-UX
   V11.00 and V11i platforms.  This support is limited to HPs JDK 1.3.1
   level.  Installation and use of this functionality is the same as
   described for the Solaris platform in the "MQSeries: Using Java" .pdf
   included with this update.  Supported levels of databases now include
   Oracle 9iR2 (at patch set 9.2.0.4) and DB2 (V7.2 at fixpack 6 for
   V11.0).
 
 
 
 J) Fix Pack CSD05 (PTFs 8U487851 and U487852)
   -----------------------------------------
 
 
   MQ XA applications
 
   This Fix Pack (CSD) modifies the support for COBOL applications which
   make calls to MQ from within a CICS environment.  If you use CICS with
   MQ then following the installation of this CSD you may have to rebuild
   some of your environment according to the instructions below.
 
 
1. If you use MQ in a 2-phase environment from within CICS then you must
   rebuild you MQ switch-load following the installation of this CSD.
   The updated instructions for building the switch load file are shown
   below and are replacements for Chapters 20, 25 and 30 in the
   WebSphere MQ Application Programming Guide.
 
2. If you use MQ from Microfocus COBOL applications in a CICS
   environment then you must rebuild your COBOL Runtime using the
   modified instructions below for preparing the COBOL Runtime using the
   cicsmkcobol command.
 
3. If you are using the Extended Transactional Client on UNIX platforms  
   you must rebuild your applications linking against the libmqiz and    
   libmqmcs libraries as well as the libmqic library appropriate to you  
   platform and application.  Typically this means adding                
   -lmqiz and -lmqmcs or
   -lmqiz_r and lmqmcs_r to the link step.
 
4. If you are using MQ as a resource manager in a Tuxedo application    
   then you must rebuild all programs that call into MQ's XA functions.  
   For these applications you must re-link with libmqz and libmqmcs as    
   well as libmqm.                                                      
 
5. If you are using MQ as a resource manager in an Encina application    
   then you must rebuild all programs that call into MQ's XA functions.  
   For these applications you must re-link with libmqz and libmqmcs as    
   well as libmqm.                                                      
 
Update the documentation to show this change:
 
HP-UX
Application Programming Guide - Chapter 25: SubSection "Preparing CICS programs"
 
 
Preparing the CICS switch load file.
 
  XA switch modules are provided to enable you to link CICS with WebSphere MQ:
 
 
  Table 22. Essential Code for CICS applications (HP-UX)
  +--------------------------+--------------+-----------------------------------+
  |Description               |C (source)    |C (exec) - add to your XAD.Stanza  |
  +--------------------------+--------------+-----------------------------------+
  |XA initialization routine |amqzscix.c    |amqzsc - CICS for HP-UX            |
  +--------------------------+--------------+-----------------------------------+
 
  For WebSphere MQ 5.3 CSD 5 or later use the following command to build
  the Switch load file:
 
  export MQM_HOME=/opt/mqm
 
  c89 -c $MQM_HOME/samp/amqzscix.c -I/opt/encina/include +e +z -o amqzscix.o
 
  ld +I CICS_XA_Init +e CICS_XA_Init -b \
      -o amqzscix amqzscix.o /opt/cics/lib/regxa_swxa.o  \
      -L$MQM_HOME/lib -L/opt/cics/lib -L/opt/encina/lib \
      -lcicsrt -lEncina -lEncServer -ldcekt -lpthread -lc_r \
      -lmqmcics_r -lmqmxa_r -lmqz_r -lmqmcs_r -lmqmzse
 
  For Earlier versions of WebSphere MQ use the following command to build
  the Switch load file:
 
  cc -c -s -I/opt/encina/include /opt/mqm/samp/amqzscix.c -Aa +z -o amqzscix.o
 
  ld -b -o amqzscix amqzscix.o /opt/cics/lib/regxa_swxa.o +e CICS_XA_Init \
      -L/opt/encina/lib -L/opt/mqm/lib -L/opt/cics/lib \
      -lmqmxa_r -lmqm_r -ldbm -lc -lm
 
  Always link your C transactions with the thread safe WebSphere MQ
  library libmqm_r.sl and you Cobol transactions with the COBOL library
  libmqmcb_r.sl
 
  You can find more information about supporting CICS transactions in
  the WebSphere MQ System Administration Guide.
 
 
CICS on Open Systems support
  WebSphere MQ on UNIX systems support CICS on Open Systems via the XA
  interface.  You must ensure that CICS applications are linked to the
  threaded version of the MQ libraries.
 
  The following sections describe how to build your MQ applications
  for use in the CICS environment.
 
 
Preparing CICS COBOL programs using Micro Focus COBOL
  To use Micro Focus COBOL, follow these steps:
 
  1. Add the WebSphere MQ COBOL run-time library module to the run-time
     library using the following command:
        cicsmkcobol -L/usr/lib/dce -L/opt/mqm/lib /opt/mqm/lib/libmqmcbrt.o -lmqmz_r
 
     This creates the Micro Focus COBOL language method file and enables
     the CICS run-time COBOL library to call WebSphere MQ on UNIX
     systems.
 
     Note:
       cicsmkcobol must be run only when one of the following is installed:
          . New version or release of Micro Focus COBOL
          . New version or release of TXSeries for HP-UX
          . New version or release of any supported database product
   (for COBOL transactions only)
          . New version or release of WebSphere MQ
 
  2. Export the following environment variables:
      COBCPY=/usr/mqm/inc  export COBCPY
 
  3. Translate, compile, and link the program by typing:
      cicstcl -l COBOL -e <yourprog>.ccp
 
Preparing CICS C programs
  You build CICS C programs using the standard CICS facilities:
 
  Export one of the following environment variables:
    LDFLAGS = "-L/opt/mqm/lib -lmqm_r" export LDFLAGS
    USERLIB = "-L/opt/mqm/lib -lmqm_r" export USERLIB
 
  Translate, compile, and link the program by typing:
    cicstcl -l C amqscic0.ccs
 
 
CICS C sample transaction
  Sample C source for a CICS WebSphere MQ transaction is provided by
  AMQSCIC0.CCS.  The transaction reads messages from the transmission
  queue SYSTEM.SAMPLE.CICS.WORKQUEUE on the default queue manager and
  places them onto the local queue whose name is contained in the
  transmission header of the message.  Any failures will be sent to the
  queue SYSTEM.SAMPLE.CICS.DLQ.  The sample MQSC script AMQSCIC0.TST may
  be used to create these queues and sample input queues.
 
 
 
 
K) Fix Pack CSD04 (PTFs U486875 and U486876)
   -----------------------------------------
 
 o 73019,72805,73069 - Firewall Support
 
   The restrictions on the use of the local address property, used to
   support firewall requirements from base Java and JMS have been
   removed in fix pack CSD04.
 
   However the following new information will be put into the JMS
   publication information under firewall support and will be marked
   as iSeries only.
 
      When using Local Address for firewall sockets the HostName
      MUST always be explicitly stated in the Java/JMS calls even if
      the Client and Server are on the same machine.
 
      For example, use setHostName(< actual local host name >) on
      MQTopicConnectionFactory to enable the firewall support to
      work correctly when the Client and Server are on the same
      machine. Do not allow the HostName to default to localhost if
      firewall support is required.
 

L) Fix Pack CSD03 (PTFs U485562 and U486241)
   -----------------------------------------
 
 o AMQLDPMA executable
 
   There is a problem with the file /opt/mqm/bin/amqldmpa.  This was
   incorrectly shipped this as a file with the product, when it
    should have been shipped as a link, pointing to one of the files
   /opt/mqm/bin/amqldmpa_d or /opt/mqm/bin/amqldmpd_nd depending on
   whether or not you use a DCE install.
 
   When installing the product for the first time, the postinstall
   scripts would have overwritten this file with the appropriate
   link anyhow, so there was no problem at that stage.
 
   But because this file was shipped on the original product, so it
   was also shipped on fix pack CSD01. So if you have subsequently
   applied fix pack CSD01 to the IBM WebSphere MQ for HP-UX V5.3.0.0
   product level, then the link has been changed to the non-DCE
   version of the file.
 
   On a non-DCE installation, this is not so significant (see
   uninstalling problem below).  But on a DCE installation in
   addition to the uninstall problem there is also an incorrect
   version of this executable installed on your machine.
 
   Fix pack CSD03 and all subsequent fix packs will ship the correct
   files /opt/mqm/bin/amqldmpa_nd and /opt/mqm/bin/amqldmpa_d.
 
   To avoid this problem from occurring in the future, we suggest
   that you uninstall fix pack CSD01 on its own before applying any
   subsequent fix pack.
 
   It is also recommended that you ensure that, after removing
   fix pack CSD01, /opt/mqm/bin/amqldmpa is now a link pointing to
   /opt/mqm/bin/amqldmpa_nd for non-DCE installations and
   /opt/mqm/bin/amqldmpa_d for DCE installations.
 
   This problem will only occur if you installed fix pack CSD01 on
   the original version 5.3.0.0 of the product.  The problem will
   not occur if you installed the refresh versions 5.3.0.1 or
   5.3.0.2 of the product (these already have fix pack CSD01
   incorporated in them).
 
        Uninstalling Problem
        --------------------
 
        If you try to uninstall the complete product in one go (ie.
        original product and fix pack CSD01 at the same time), the
        uninstall will fail, with a message saying the backed up
        files are not present and so uninstalling the fix pack could
        break the product.
 
        If you have fix pack CSD01 installed, and wish to uninstall
        IBM WebSphere MQ for HP-UX V5.3 from your machine, please
        uninstall fix pack CSD01 prior to uninstalling the main
        product.
 
        This fixes the problem as the link is restored.
 
 
 o 73019,72805,73069 - Firewall Support
 
   Restrictions on the use of the local address property, used to
   support firewall requirements from base Java and JMS.
 
   1.When the Client is on one machine and the Server is on a
     different machine the local address property IP address must
     ALWAYS be specified along with the port range.
 
   2.Do not use the local address property on machines with more
     than one network card.
 
 
M) Fix Pack CSD01 (PTFs U484024 and U484131)
   -----------------------------------------
 
 o 62221 - Upgrade to GSKit 6.0.3.30
 
   This fix pack contains an upgrade to the IBM Global Security
   (GSKit) product. This fix pack installs a new level of the GSKit
   product.  Please follow the instructions shown in the
   Installation and Maintenance information in this PTF memo to
   install/re-install this component of the fix pack.
 
 o 67831   - Include "properties" files in com.ibm.mq.jar
 
   Fix pack CSD01 moves the "mqji*.properties" files from their
   original position in directory "../java/lib" to "com.ibm.mq.jar".
   Any subsequent product release, including the recent product
   refreshes at service levels 5.3.0.1 and 5.3.0.2, will delete the
   original files and also remove the "../java/lib" entry from
   CLASSPATH.  Fix pack CSD01 (and any later fix pack) only adds the
   files to "com.ibm.mq.jar" - it does not remove the old ones, or
   update CLASSPATH.  To prevent problems in future due to using an
   old version of these files instead of the new one, you are
   recommended to manually remove the "../java/lib" entry from
   CLASSPATH, or to put it after the "../java/lib/com.ibm.mq.jar"
   entry.
 
 
 
 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 

SERVICE AND TECHNICAL SUPPORT
-----------------------------
 
A) Service Level Information
   -------------------------
 
   o This release incorporates the following APARs from IBM MQSeries
     for OS/2 V5.1:
 
        IC23891 IC24521 IC25358 IC25882 IC26417 IC26919 IC27948
        IC29218 IC29413 IC29643 IC29645 IC31041 IC32544 IC34063
 
   o This release incorporates the following APARs from IBM MQSeries
     for Windows NT and Windows 2000 V5.2:
 
        IC27211 IC27655 IC27656 IC29103 IC29358 IC29405 IC29498
        IC29675 IC29687 IC29774 IC29805 IC29815 IC29847 IC29850
        IC29975 IC29984 IC30002 IC30035 IC30062 IC30106 IC30149
        IC30213 IC30219 IC30225 IC30228 IC30246 IC30250 IC30309
        IC30335 IC30343 IC30468 IC30514 IC30555 IC30566 IC30569
        IC30595 IC30697 IC30844 IC30897 IC31323 IC31530 IC31673
        IC31755 IC31808 IC31814 IC31833 IC31899 IC31901 IC31920
        IC32055 IC32103 IC32221 IC32223 IC32260 IC32296 IC32581
        IC32582 IC32651 IC32656 IC32674 IC32753 IC32843 IC32875
        IC32938
 
   o This release incorporates the following APARs from IBM MQSeries
     for AIX V5.2:
 
        IY03669 IY08799 IY09958 IY12689 IY15169 IY15945 IY16092
        IY16483 IY17118 IY17285 IY18201 IY18932 IY19816 IY20510
        IY20768 IY21794 IY21854 IY22429 IY23957 IY24221 IY24268
        IY24515 IY24677 IY24857 IY25120 IY25648 IY25676 IY25746
        IY27109 IY27517 IY27710 IY28921 IY29202 IY29238 IY29305
        IY29497 IY29933 IY30457
 
   o This release incorporates the following APARs from IBM MQSeries
     for HP-UX V5.2:
 
        IY12776 IY14251 IY15170 IY15173 IY15655 IY15839 IY15947
        IY15984 IY17946 IY18203 IY19831 IY19850 IY20234 IY20727
        IY20763 IY22185 IY22995 IY23667 IY23736 IY24181 IY24795
        IY25121 IY25122 IY25463 IY25494 IY25639 IY25652 IY26290
        IY26494 IY27111 IY27112 IY28347 IY28931 IY28959 IY28978
        IY29099 IY29699 IY30152
 
   o This release incorporates the following APARs from IBM MQSeries
     for Sun Solaris V5.2:
 
        IY12110 IY12240 IY14518 IY14563 IY15171 IY15320 IY15794
        IY15801 IY15948 IY16190 IY16357 IY16442 IY17319 IY17471
        IY17737 IY17846 IY18500 IY18567 IY18779 IY19317 IY19401
        IY19616 IY19848 IY20931 IY21665 IY21795 IY21985 IY22333
        IY22456 IY22951 IY23553 IY24753 IY24879 IY25080 IY25129
        IY25309 IY25774 IY25795 IY25800 IY27113 IY27191 IY27208
        IY27550 IY28292 IY28451 IY28504 IY28906 IY30005 IY30380
        IY30561
 
   o This release incorporates the following APARs from IBM MQSeries
     for Linux V5.2:
 
        IY15172 IY15983 IY19849 IY25128 IY27114
 
   o This release incorporates the following APARs from IBM MQSeries
     for Tru64 V5.1:
 
        IC27696 IC29149 IC29945 IC30518 IC30908 IC31431 IC32038
        IC32320 IC33691
 
   o No PTFs from IBM WebSphere MQ for HP-UX V5.3 have been incorporated
     into this release.
 
 
 
B) Service Support Available from the Internet
   -------------------------------------------
 
   The WebSphere MQ support page is located at:

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

 
   From the WebSphere MQ support page, you can obtain the latest
   information about the following topics:
 
         IBM Transaction Processing SupportPacs
         Closed APARs
         Fix Packages
         Frequently Asked Questions
         Tips and Techniques
         Device Drivers
         Forums
         Related Links
 
 
C) Cross Product Dependencies
   --------------------------
 
   1. TXSeries CICS and IBM WebSphere MQ Extended Transactional
      Client
 
      If you are using TXSeries CICS as the XA compliant Transaction
      Manager to coordinate the IBM WebSphere MQ Extended
      Transactional Client, then either the TPM or AXLIB parameter
      of the xa_open string must be supplied, see the IBM WebSphere
      MQ Extended Transactional Clients book, Chapter 3.
      Configuring an extended transactional client, for more details
      of these parameters.
 
      The version of TXSeries CICS used must be:
           V5.0 + PTF 1 + e-fix 2 or later PTF
 
      Note that the pre-build switch load file amqczsc is built
      for CICS V4.2, so is of no use, see below for instructions to
      build a CICS V5.0 switch load file.
 
   2. HP-UX Version 11i and SSL
 
      WebSphere MQ SSL runs successfully on HP-UX Version 11i when
      the following patch bundles are applied:
 
      HWEnable11i    B.11.11.0112.5 Hardware Enablement Patches for
                     HP-UX 11i, December 2001
      GOLDAPPS11i    B.11.11.0112.6 Gold Applications Patches for
                     HP-UX 11i, December 2001
      GOLDBASE11i    B.11.11.0112.6 Gold Base Patches for HP-UX 11i,
                     December 2001.
 
   3. IBM WebSphere MQ V5.3 Server and IBM WebSphere MQ Extended
      Transactional Client
 
      The service level of the IBM WebSphere MQ V5.3 server, to
      which the IBM WebSphere MQ Extended Transactional Client is
      connected, must be 5.3.0.3 (fix pack CSD03) or later service
      levels 5.3.0.x.
 
   4. HP-UX Versions 11/11.1 and WebSphere MQ for HP-UX V5.3 Client
 
      The following patches are required for HP-UX V11/V11.1 when
      using the IBM WebSphere MQ for HP-UX V5.3 client with service
      level 5.3.0.3 (fix pack CSD03) or higher service level applied:
 
           HP-UX 11:   PHSS_26559 or later
           HP-UX 11.1: PHSS_26560 or later
 
   5. TXSeries CICS and IBM WebSphere MQ V5.3 Server or IBM WebSphere
      MQ Extended Transactional Client
 
      Note that the pre-build switch load file (Server: amqzsc; Client:
      amqczsc) is built for CICS V4.2, to build a CICS V5.0 switch load
      file, do the following:
 
      export MQM_HOME=/opt/mqm
 
      For IBM WebSphere MQ V5.3 Server:
 
         c89 -c $MQM_HOME/samp/amqzscix.c -I/opt/encina/include +e +z \
             -o amqzscix.o
         ld +I CICS_XA_Init +e CICS_XA_Init -b \
             -o amqzsc5 amqzscix.o /opt/cics/lib/regxa_swxa.o  \
             -L$MQM_HOME/lib -L/opt/cics/lib -L/opt/encina/lib \
             -lcicsrt -lEncina -lEncServer -ldcekt -lpthread -lc_r \
             -lmqmcics_r -lmqmxa_r -lmqz_r -lmqmcs_r -lmqmzse
 
      For IBM WebSphere MQ Extended Transactional Client:
 
         c89 -c $MQM_HOME/samp/amqzscix.c -I/opt/encina/include +e +z \
             -o amqzscix.o
         ld +I CICS_XA_Init +e CICS_XA_Init -b \
             -o amqczsc5 amqzscix.o /opt/cics/lib/regxa_swxa.o \
             -L$MQM_HOME/lib -L/opt/cics/lib -L/opt/encina/lib \
             -lcicsrt -lEncina -lEncServer -ldcekt -lpthread -lc_r \
             -lmqccics_r -lmqcxa_r -lmqiz_r -lmqmcs_r -lmqmzse
 
 
 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 

FIX PACK HISTORY
================
 
A) Fix Pack CSD14 (PTF U808478 and U808479)
   ----------------------------
 
   This is the thirteenth fix pack for IBM WebSphere MQ for HP-UX
   Version 5.3 from IBM. It is delivered via PTFs U808478 and
   U808479 for APAR IY85694.
   
   This fix pack includes fixes for all the problems listed below:
   

   IC49578 - Cumulative maintenance #13 (CSD14) for WebSphere MQ for Windows V5.3
   IY85693 - Cumulative maintenance #13 (CSD14) for WebSphere MQ for AIX V5.3    
   IY85694 - Cumulative maintenance #13 (CSD14) for WebSphere MQ for HP-UX V5.3  
   IY85724 - Cumulative maintenance #13 (CSD14) for WebSphere MQ for Linux for Intel V5.3  
   IY85725 - Cumulative maintenance #13 (CSD14) for WebSphere MQ for Linux for zSeries V5.3
   IY85695 - Cumulative maintenance #13 (CSD14) for WebSphere MQ for Solaris V5.3
   
   IC49520 - WHEN RUNNING WITH WEBSPHERE APPLICATION SERVER, A COMPLETE LIST    
   IC49616 - FDCS WITH AT040010 AND AT003001 WHILE REUSING THE AGENT            
   IC49857 - MQ RC = 2354 MQRC_UOW_ENLISTMENT_ERROR WHEN USING MSDTC IN MSCS    
   IC49967 - RESTRICTED (NON-ADMINISTRATOR) MS WINDOWS USERS ARE UNABLE TO      
   IC50215 - ACCESS VIOLATION SEEN IN DLLHOST WHEN RUNNING A VB OR STA          
   IC50309 - MSCS HANG WHEN RESTART THREASHOLD HAS BEEN SET.                    
   IC50327 - FDC with Probe KN101001 from kqiCloseIt during MQDISC              
   IC50431 - MQ MODIFIES THE PROCESSES ACCESS PERMISSIONS AND GRANTS            
   IC50453 - AMQSTRG0 COMMENTS SAY IT IS USING MQTMC2 BUT THE SAMPLE SAYS      
   IC50536 - QUEUE HANDLE LEAK WHEN ACCESSING ALIAS OR REMOTE QUEUES ON Z/OS    
   IC50588 - FDC AQ109001 FROM AQHLOGICALMSGLOCK DURING BROWSE,LOCK OF A        
   IC50734 - ACCESS VIOLATION IN THE AMQMTSXATM.DLL WHEN MSDTC.EXE HAS PASSE    
   IC50831 - MESSAGE ENDS UP ON DLQ WITH ERROR 2082 USING 'PUT TEST MESSAGE'    
   IC50901 - AMQXSSVN PROCESS PREVENTS QUEUE MANAGER RESTARTING UNDER MSCS      
   IC51054 - "MQRC_STORAGE_NOT_AVAILABLE ERROR DUE TO THE INVALID DATALENGTH    
   IC51315 - WEBSPHERE MQ ROLLS BACK PREPARED TRANSACTIONS IF MSDTC GOES DOW    
   IC51322 - CODE CHANGES FOR OPTIMIZATION OF DEFAULT CONVERSION                
   IC51324 - WMQ INVOKES ENLISTWITHDTC TO ENLIST WITH THE TRANSACTION LEADIN    
   IC51439 - LOG WRITE OPERATIONS DO NOT RETRY WHEN AN ERROR_LOCK_VIOLATION    
   IC51451 - ACCESS VIOLATION OCCURRING WHEN PRINTING OUT THE OBJECT            
   IC51496 - MSG SEGMENTS ALL HAVE THE SAME FORMAT CCSID & ENCODING            
   IC51497 - GET COMPLETE MSG FAILS WITH MQRC_MATCH_OPTIONS_ERROR              
   IC51589 - RUNMQDLQ SUFFERS XC130031 ACCESS VIOLATION WHEN IT ENCOUNTERS -  
   IC51667 - APPLICATION SERVER SENDING THE XA FLOWS WHICH ARE RESULTING IN    
   IC51721 - UNABLE TO REBUILD A SYNCFILE USING RCRMQOBJ IF USING CIRCULAR      
   IC51749 - AMQ7006 ERROR GENERATED WHEN ATTEMPTING TO CREATE QUEUE MANAGER    
   IC51754 - SSL CHANNEL CLOSES WITH AMQ9207 ERROR WHEN HP NSS QUEUE            
   IC51952 - TRUNCATED_MSG_FAILED FROM MQGET CALL EVEN THOUGH ENOUGH BUFFER    
   IC52019 - OPTIMIZE CODE WHERE MQ READS THE SYNC FILE TO GET THE              
   IC52021 - VALID WEBSPHERE MQ USERIDS ARE BEING REJECTED                      
   IC52223 - ACCESS VIOLATION FDC XC130031 IN THE AMQFCXBA PROCESS.            
   IC52590 - DELETING THE CUSTOM SERVICE OBJECT DOES NOT DELETE IT FROM THE    
   IC52817 - MISSING CHANNEL NAME IN AMQ9503 MESSAGE                            
   IC52878 - WHEN THE WMQ SERVICE IS RESTARTED, THE ENDCOMMAND PARAMETER IS    
   IC53255 - LOGIC ERROR IN THE PROCESSING OF THE CERTIFICATES                  
   IC53318 - INCORRECT ACE TYPE SPECIFIED MC033007                              
   IY84998 - AGENT LOOPING INSIDE ZLAHEALTHTHREAD PRODUCING REPEATED            
   IY85622 - FDC CO052000 FROM CCITCPRECEIVE BY AMQRMPPA PROCCESS WITH ERROR    
   IY85679 - XLLOSSPINLOCKWAITLOCK CAN HIT AN INCONSISTENT STATE WHEN RELEAS    
   IY85806 - XC034071 DURING OR SHORTLY AFTER CALL TO MQLPGILD                  
   IY86395 - OUTPUT OF ERRPT -N MQSERIES IS NOT FORMATTED CORRECTLY            
   IY86827 - QUEUE MANAGER IS NOT ABLE TO WRITE TO QUEUE MANAGER LOG FILES.    
   IY86828 - DELIVERY PROBLEM WITH TWO LISTENERS ON SAME-NAME MQ DESTINATION    
   IY86994 - WEBSPHERE MQ CLUSSDR CHANNEL DOES NOT START FOR MESSAGES          
   IY87192 - MQRC_CONNECTION_BROKEN AND RECURSIVE IMQ_IMPL_DISC_BACKOUT        
   IY87523 - CORRECTIONS TO ENSURE PROPER MAPPING BETWEEN EURO-ENABLED CCSID    
   IY87702 - HANDLE NULL RETURN FROM XCSGETPWNAM                                
   IY87753 - XC130004 (SIGSEGV) WHEN TRACING MQGET OF MESSAGES GREATER          
   IY87797 - MQ RUNMQSC CREATES FDC WITH PROBE ID XC267011 SHOWING SIGPIPE      
   IY87802 - OBJECT NAMES ARE STORED IN A 48-CHARACTER SPACE, PADDED WITH      
   IY87804 - AX_UNREG IS CALLED REGARDLESS OF THE XID RETURNED FROM AX_REG I    
   IY87844 - AVOID CACHING PROCESS ID IF LOOKUP FAILS                          
   IY88246 - SEMAPHORE MAY NOT BE CREATED WITH CORRECT PERMISSIONS              
   IY88509 - CHANNEL WITH SSL ENABLED NEVER ENDS ON LINUX.                      
   IY88514 - CONNECTIONS LEFT OPEN WHEN AN XA CREATE SESSION FAILS              
   IY88873 - MEMORY LEAK IN QUEUESESSION FOR JMS 1.1 CALLS ONLY.                
   IY88909 - RESOLUTION FOR THE QUEUE NAME OR QUEUE MANAGER NAME FAILS WITH    
   IY88954 - POOLSCAVENGER IS NEVER STARTED AND SO CONNECTIONS ARE NOT          
   IY89259 - NULLPOINTEREXCEPTION IN GETCONNECTIONCCSID() OR SPIGET()          
   IY89374 - JMS CLIENTS SHOULD NOT ASSUME THE DEFAULT PERSISTANCE (DEFPSIST    
   IY89755 - INCORRECT LOCKING STRATEGY FOR PIPELINED CHANNELS                  
   IY90244 - CHANNELS UNABLE TO CONNECT TO THE QUEUE MANAGER AFTER PROBE ID    
   IY90460 - AMQRMPPA PROCESS WILL NOT RELEASE THREADS CAUSING HIGH CPU UTIL    
   IY90521 - LISTENER PROCESS CRASHES WHEN RECEIVING A BAD MESSAGE (ENOBUFS)    
   IY90524 - AMQRMPPA XC130003 SIGSEGV IN XCSLOADFUNCTION FOR CHANNEL EXIT      
   IY90995 - SIGSEGV OCCURS IF GID IS NOT FOUND                                
   IY91269 - FFST WITH PROBE XC006001 WHEN USING CHANNEL EXITS                  
   IY91357 - ALTERING CHANNEL DEFINITION RESETS THE SSLPEER() ATTRIBUTE.        
   IY92929 - AFTER RECEIVING HRCE_MQLO_DISK MSG IF QUEUEMANAGER IS NOT RECYC    
   IY92963 - SIGSEGV IN PREPAREDUMPAREAS DURING CRTMQM AND RESULTING CORE      
   IY93324 - MQJMS2003 GETS GENERATED WITH A NULL POINTER EXCEPTION.            
   IY93655 - PERFORMANCE PROBLEMS RELATED TO RESOLVING HIGH LOCK CONTENTION    
   IY93752 - EXCESSIVE DNS LOOKUPS                                              
   IY93881 - TIMEING ISSUE                                                      
   IY94032 - FIXPACK 13 (CSD13) NON-SSL U804876.NOGSKIT.TAR.Z FOR SOLARIS      
   IY94250 - WHEN MQ_CHANNEL_SUPPRESS_INTERVAL IS SET TO "0,0" CAUSES          
   IY94267 - JVM CRASH WHEN USING XA IN BINDINGS MODE IN WAS 6.1                
   IY94451 - CLUSTER QUEUE DEFINITIONS MAY NOT BE REMOVED FROM CLUSTER CACHE    
   IY94625 - AMQFCXBA SUFFERING A SIGSEGV IN FUNCTION FKIRESTORESUBSCRIPTION    
   IY94674 - FILE DISCRIPTOR FOR FCLOSE() REACHED                              
   IY94700 - RUNMQLSR STALLS AFTER RECV FUNCTION IS INTERRUPTED WITH RETURN    
   IY94811 - NULLPOINTER EXCEPTION OCCURS IF WEBSPHERE APPLICATION SERVER      
   IY94832 - CONFLICTING SUBSCRIPTIONS                                          
   IY94876 - UNIX FILE DESCRIPTORS BEING LEFT OPEN WHILE GENERATING FDC FOR    
   IY94977 - QUEUE MANAGER FAILS TO START THROWING LOG NOT AVAILABLE ERROR      
   IY95078 - LONG DELAYS IN MULTI-THREADED PUTS IN WMQ C++ CLIENT              
   IY95181 - JMS NULL VALUED CAUSES EXCEPTION IN MQ JMS APPLICATION            
   IY95370 - SYNCHRONIZATION ISSUE WITH THE JMSCONNECTION                      
   IY95513 - PATCH 112960-42 FOR SOLARIS 9 IS CAUSING QUEUE MANAGER FAILURE    
   IY95538 - 2080 IS ISSUED WHEN MCA AGENT IS TRYING TO GET MESSAGES FROM SY    
   IY95706 - SIGSEGV IMMEDIATELY FOLLOWING RETURN FROM ZFUDOESOBJECTEXIST      
   IY96066 - MQ JMS PUBLISH/SUBSCRIBE CLEAN UP DOES NOT PROCESS ALL            
   IY96629 - LOCAL QUEUES WITH NPMCLASS(HIGH) MIGHT BE DAMAGED DURING          
   IY98620 - QUEUE MANAGER HANG DURING DEFINE OBJECT WHEN AN API EXIT          
   IY98777 - WEBSPHERE MQ HANGS AFTER RC=STOP FROM A CALL TO                    
   IY99050 - RCDMQIMG FAILS WITH AMQ7084 FOR A QUEUE CONTAINING SEGMENTED      
   IY99051 - EXISTING VALID INSTANCES OF CLUSTER CHANNELS ARE NOT RECOGNIZED    
   IY99200 - SEGV OCCURS WHEN EXECUTION CONTROLLER IS TRYING TO CLEANUP A PI    
   IY99415 - EXTRA VALIDATION FOR DATA RECEIVED FROM TCP/IP TO HANDLE          
   IY99591 - THE ASYNCHRONOUS MONITOR THREAD FAILS TO END ALONG WITH MQ PROC    
   IY99598 - FDC GETS GENERATED WITH PROBE ID ZI032002 IN ZIISTOPHEALTHTHREA    
   IY99790 - AMQZLAA0 AGENT HANGS DURING ERROR HANDLING.                        
   IY99912 - MQ CODE DOES NOT CHECK THAT THE BOUNDS OF THE ARRAY OF LOG        
   IZ01272 - APAR defect for 107286 and 107286.1.                              
   IZ01355 - COMMUNICATION BETWEEN V5.3 QMGR AND V6.0 QMGR FAILS DUE TO        
   IZ01512 - ROOT CAUSE FOR THIS PROBLEM IS THE LOGGER PROCESS FAILING TO  
   IZ11247 - DEFECTS FIXED IN WEBSPHERE MQ V5.3 FIX PACK 14      
   PK24087J - Under WAS on z/OS, bindings mode sessions can get the wrong uid    
   PK29218J - MQJMS2005 received on z/OS creating a unified JMS Connection      
   PK32885J - DLH shows wrong queue name when backout requeue fails              
   SE25940 - MQM400-MSGMCH3601 AND RC3029 RESOURCE BUSY WHEN MQPUT FAILS AND    
   SE25949 - F/QUSRJOBI-MSGCPF3C53 FDC GENERATED WITH PROBE XC037013 FOR
   SE25969 - OSP-MSGAMQ8135-PAR AMQ8135 NOT AUTHORIZED WHEN USING *ALLOBJ      
   SE26233 - MQM400 PNGMQMCHL FAILS WITH MSGMCH3601, IF USER PROFILE LOCALE    
   SE26739 - MQM400 AMQ9207 CO052000 CCITCPRECEIVE RRCE_BAD_DATA_RECEIVED      
   SE27324 - MQM400 INCORROUT - CONVERSION CODEPAGE 37 X'15'                    
   SE27700 - MQM400 CRTMQM AND STRMQM OF QUEUE MANAGER RECEIVES AF089070 A      
   SE28711 - MQM400 - MSGMCH3601 WHEN ATTEMPTING TO DISPLAY MESSAGE AMQ6106    
   SE28827 - MQM400 SDR(1256) TO RCVR(420) FAILS TO START WITH AMQ9520          
   SE28955 - QUEUE BECOMES DAMAGE AT LEAST 2 TO 3 TIMES A WEEK.                
   SE29414 - MQM400 - P0000* AND/OR S0000* FILES IN QMQM LIBRARY NOT REMOVED    


B) Fix Pack CSD13 (PTF U804874 and U804875)
   ----------------------------
 
   This is the twelfth fix pack for IBM WebSphere MQ for HP-UX
   Version 5.3 from IBM. It is delivered via PTFs U804874 and
   U804875 for APAR IY75437.
   
   This fix pack includes fixes for all the problems listed below:
   

   IC47174 - Cumulative maintenance #12 (CSD13) for WebSphere MQ for Windows V5.3
   IY75436 - Cumulative maintenance #12 (CSD13) for WebSphere MQ for AIX V5.3    
   IY75437 - Cumulative maintenance #12 (CSD13) for WebSphere MQ for HP-UX V5.3  
   IY75561 - Cumulative maintenance #12 (CSD13) for WebSphere MQ for Linux for Intel V5.3  
   IY75562 - Cumulative maintenance #12 (CSD13) for WebSphere MQ for Linux for zSeries V5.3
   IY75510 - Cumulative maintenance #12 (CSD13) for WebSphere MQ for Solaris V5.3
   

   IC47289 - Deadlock on object catalog caused by performance events on
             SYSTEM.AUTH.DATA.QUEUE.
   IC47739 - Cannot end the pubsub broker from the MQ services GUI.
   IC47771 - Channel terminated FFST RM487001 with memory access
             violation XC130031.
   IC47974 - Trap due to a stack underflow in a COM+/MTS environment
             whilst continually connecting to a non-running queue
             manager.
   IC47978 - Timing problem may cause WebSphere MQ for Windows queue
             manager not to start in auto mode.
   IC48046 - MQMESSAGECONSUMER.RECEIVE(TIMEOUT) does not honour the
             timeout value when message selectors are used.
   IC48156 - AMQ9210: remote attachment failed.
   IC48217 - EOFEXCEPTION occurs when calling MQMESSAGE.READSTRING().
   IC48309 - COM+ application hangs when connecting to queue manager.
   IC48397 - Exits are deleted when migrating from WebSphere MQ V5.3 to
             v6.0 on Windows platforms.
   IC48478 - MQJMS3023 in PUB SUB application after quiescing and
             restarting the queue manager.
   IC48512 - FDC indicating incorrectly configured DCOM object.
   IC48515 - .NET (dotnet) applications fail when WebSphere MQ trace is
             running.
   IC48555 - JMS PUB/SUB cleanup utility fails with 2009 in SSL
             environment.
   IC48595 - The JMS TOPICCONNECTION constructor creates an additional
             MQQUEUEMANAGER to resolve the queue manager name.
   IC48596 - WebSphere MQ using incorrect user ID, and receiving
             MQRC_NOT_AUTHORISED (2035) errors, in a COM+ environment.
   IC48662 - Convert chained header to UCS-2 returns wrong reason code.
   IC48680 - Stopping the first instance of a receiver channel which is
             connected to multiple sender channel throws AMQ9533 error.
   IC48699 - Deadlock within the MQ COM+ layer following a connection
             broken return code in the Extended Transactional Client.
   IC48705 - WebSphere MQ creates FDC with probe ZF165008 from
             WASRECEIVEDATA.
   IC48727 - WebSphere MQ message AMQ7227 does not clearly define
             possible causes.
   IC48775 - MQ Java classes when run as a client fail to negotiate to
             an MQ server running pre-FAP 4 LEVEL, and incorrectly use
             HBINT value.
   IC48784 - using AMQMCERT -R option, the wrong certificate is removed.
   IC48803 - AMQ9207 invalid data received on a channel following a
             timeout on the Windows platform. FDC with probe ID CO052000
             is created.
   IC48913 - Performance problem getting message from a large queue.
   IC48914 - Conversion from CCSID 819 to 912 fails on get/convert.
   IC48920 - Repeated RESRCMON.EXE FDC's following MSCS related errors.
   IC49003 - Multi threaded C++ application hangs.
   IC49024 - Explorer cannot connect to queue manager on HPUX with CCSID
             923.
   IC49084 - .NET sample code(for CS and CPP files) supplied with WMQ
             V5.3/V6 is missing close and disconnect methods.
   IC49150 - DCOM security corruption on Windows 2003 SP1, XP SP2 and
             later.
   IC49167 - Data conversion error causes segmented messages to be dead
             letter queued (or return MQRC_FORMAT_ERROR from mqget).
   IC49409 - CLUSRCVR disappearing at queue manager startup time.
   IC49484 - AMQ9633 Error on SSL enabled channels caused by
             RRCE_SSLCM_LIB_NOT_INIT from CCITCPSSLOBTAINLDAPCRLS.
   IY72089 - JMS property MSG.SETSTRINGPROPERTY(JMS_IBM_FORMAT) not
             copied in a Weblogic environment.
   IY77448 - Rare deadlock possibilities involving FDC reporting.
   IY78420 - SETMQCAP fails silently when disk space is low or a disk
             I/O error occurs.
   IY78438 - Clustering: large numbers of subscriptions cause slowdown
             of repository cache creation (during STRMQM); or
             recreation.
   IY78788 - SIGSEGV in AQSRELEASEBCLIST during queue manager shutdown.
   IY78836 - JMSADMIN cannot find its configuration file.
   IY79142 - Channels fail with AMQ9631 when using a global server
             certificate.
   IY79158 - Rare timing condition in MQCONN causes hang.
   IY79226 - Some processes (E.G. AMQRMPPA) may not recreate a trace
             file (.TRC) if it has been deleted and trace restarted.
   IY79234 - XAER_RMERR returned by extended transaction client XA
             calls, following MQRC_ANOTHER_Q_MGR_CONNECTED from MQCONN
             or MQCONNX.
   IY79288 - FDC probe XC130003 reporting sigbus or sigsegv in broker
             function FKIRESTORESUBSCRIPTION.
   IY79616 - Linux: small timing window can result in spurious semaphore
             unlock, giving FDC probes such as XC346012.
   IY79906 - After FDC with PROBE ID AD031001, component ADIWRITEFILE
             with comment RC=0 from write, the queue manager can fail to
             restart.
   IY79915 - Write FFST if deleting a cluster object with a live
             subscription.
   IY80247 - Subscription to full repository manager object is deleted
             if there is a problem when the subscription is renewed.
   IY80410 - MQJMS2013 error when connecting to WebSphere MQ in bindings
             mode.
   IY80428 - AMQRRMFA can end abruptly when two or more cluster
             receivers are defined with the same name within the same
             cluster.
   IY80516 - HP-UX: compiling and linking clarification for a
             thread-safe channel-exit program.
   IY80952 - Memory leaks in clustered channels, and (V6) PCF filtering.
   IY81533 - CONNECTIONNAME is often not included in "Channel SSL error"
             event messages.
   IY81580 - Cluster workload exit reason not set for cluster PCF
             message.
   IY81671 - XC308090 when XA_START and XA_ROLLBACK or XA_COMMIT are
             issued concurrently for same XID.
   IY82062 - Deadlock in COM+ when one thread issues an MQCONN which
             fails, at the same time as another issues MQDISC.
   IY82297 - RCDMQIMG records image of damaged object leading to
             subsequent RCRMQOBJ failure.
   IY82419 - Probe ID'S XC332070 and XC034071 from XLSWAITEVENT.
   IY82481 - GSKit unable to receive CA-SIGNED SSL certificate: "All the
             signer certificates must exist in the database".
   IY82629 - RESET_ICONV_TABLE not found when installing client on
             HP-UX.
   IY82779 - RCRMQOBJ of syncfile can result in misleading AMQ7047
             message; also, references to RCRMQMOBJ should be to
             RCRMQOBJ.
   IY82806 - NPMCLASS on local queue is not inherited from 'like'
             object.
   IY82834 - When one or more /TMP/MQSERIES.[PID] files are deleted then
             ENDMQM can hang.
   IY82889 - When using cross domain connection factory definitions in
             WAS V6 the TCPIP connection is not released during the
             cleanup.
   IY82973 - MQCONN from non-MQM user fails with
             MQRC_Q_MGR_NOT_AVAILABLE due to RC (20806210)
             XECX_E_NO_SUCH_EXTENT.
   IY83093 - Workload balancing temporarily unbalanced after a lot
             balancing.
   IY83372 - XCSFREEQUICKCELL reports XECS_E_BLOCK_ALREADY_FREE in
             error.
   IY83588 - Extremely long running channel exits cause channels to end
             due to hbint not taking the exit time into account.
   IY83825 - XC014030 FDC in XCSALLOCATEQUICKCELL at CSD12.
   IY83952 - /TMP/CMDDB00000.STH files created and not removed when an
             SSL key repository created using -stash with GSKit.
   IY83956 - GSKit allows SSL key repository to be deleted with the
             wrong password.
   IY83957 - GSKit gives incorrect error message when user enters
             incorrect password for key repository in a GSK6CMD command.
   IY84127 - When QM runs out of resource and error logic is being
             exercised, MQ calls XCSFREEQUICKCELLBLOCK() instead of
             XCSFREEQUICKCELL().
   IY84410 - FDC with probe AT002001 is generated when ATM.RMIDGENERATOR
             reaches 2147483647.
   IY85203 - WebSphere MQ script reset_iconv_table may cause blank file
             name or incorrect permissions on conversion tables.
   IY85562 - A TCP send failure may retry indefinitely as of MQ5.3
             CSD11.
   IY85802 - WebSphere MQ queue manager restart failure referencing log
             records outside active log after disk space shortage.
   SE23096 - MQM400-MSGMCH3601 exception occurs in loadexit when MQCD
             structure supplied by chad exit is not valid.
   SE23914 - MQM400 STRMQMCHL sometimes gets MSGAMQ6125.
   SE24271 - MQM400 Abnormal end of MQ application program may hang
             queue manager.
   SE24477 - MQM400 MCH0601 after multiple STRMQMCHL.
   SE25214 - MQM400 RFRMQMAUT removes group members authorities.
     97044 - MQM400 ENDMQM with ENDCCTJOB(*YES) is not forcing a
             checkpoint and logging messages AMQ7460/AMQ7462.
     96928 - Improved error reporting for message catalog problems.
     95357 - MQM400 additional diagnostic trace and FDC report in
             ADIWRITEFILE.
     86112 - Channel status shows incorrect value of SSLPEER.
    101027 - XC014030 FDC in XCSALLOCATEQUICKCELL at CSD12.
    100211 - Cleanup of connections in terminated threads could effect
             other threads in same process.
   
C) Fix Pack CSD12 (PTFs U803577 and U803578)
   -----------------------------------------
 
   This is the eleventh pack for IBM WebSphere MQ for HP-UX
   Version 5.3 from IBM. It is delivered via PTFs U803577 and
   U803577 for APAR IY70928.
   
 
   For a full list of problems included in this fix pack please refer to the
   web site
http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006919
   
 
   It includes fixes for all the problems listed below:
   

   IC45940 - Cumulative maintenance #11 (CSD12) for WebSphere MQ for Windows V5.3
   IY70911 - Cumulative maintenance #11 (CSD12) for WebSphere MQ for AIX V5.3    
   IY70928 - Cumulative maintenance #11 (CSD12) for WebSphere MQ for HP-UX V5.3  
   IY70962 - Cumulative maintenance #11 (CSD12) for WebSphere MQ for Linux for Intel V5.3  
   IY70963 - Cumulative maintenance #11 (CSD12) for WebSphere MQ for Linux for zSeries V5.3
   IY70953 - Cumulative maintenance #11 (CSD12) for WebSphere MQ for Solaris V5.3
   
   IC45869 - MQ service fails to stop, and trap occurs if a queue
             manager is deleted.                                                                                          
   IC46145 - MQRC_NO_MSG_AVAILABLE MQRC2033 when getting locked
             segments.                                                                                                      
   IC46301 - MC011057 When stopping Windows while MSCS controlled
             queue manager is still running.                                                                              
   IC46369 - Pub/sub broker (AMQFCXBA.EXE) traps saying "access
             violation at address XXXXXXXX when reading".                                                                    
   IC46407 - Incorrect truncation of queue file during log full caused
             a damaged queue.                                                                                        
   IC46433 - MQ .NET classes need +INQ authority to get dynamic queue
             name.                                                                                                    
   IC46530 - AMQ2018 .NET MQBEGIN.                                                                                                                                              
   IC46539 - .NET dotnet dynamic queue name MQRC_DYNAMIC_Q_NAME_ERROR
             2011 accessqueue.                                                                                        
   IC46548 - MQRC_OPTIONS_ERROR is returned if
             QPMO_ALTERNATE_USER_AUTHORITY is specified with
             MQQUEUEMANAGER.PUT() call.                                                      
   IC46653 - MQQUEUEMANAGER constructor does a connect to the QM, but
             it does not check to see if it is connected already
             before reconnecting.                                  
   IC46684 - Custom service entry displays wrong value in "execution"
             box on windows Chinese edition.                                                                          
   IC46766 - PUTDATETIME property in 'MQMESSAGE' MQ .NET class is read
             only and cannot be altered or set.                                                                      
   IC46774 - MMC shows incorrect status information,
             overlapping/multiple AMQMSRVN processes.                                                                                  
   IC46955 - Various SETMQSCP problems.                                                                                                                                        
   IC46987 - Coinitialize failure RPC_E_CHANGED_MODE (-2147417850) with
             MSCS.                                                                                                  
   IC47224 - Multiple POOLSCAVENGER threads created when using either
             WebSphere application server version 5.X or WebSphere MQ.                                                
   IC47236 - MQRC_CONTEXT_HANDLE_ERROR (2097 error)- when
             PASS_ALL_CONTEXT option is used with Java distribution
             list.                                                          
   IC47255 - When message selector is used with durable subscriber and
             application terminates abruptly, the messages are lost.                                                  
   IC47332 - MQ client AMQ9691 error when trying to add a certificate
             using AMQMCERT -A when the certificate is already present
             in the store.                                  
   IC47335 - JMS cumulative interim fix for WebSphere MQ V5.3
             fix pack 11                                                                                                      
   IC47443 - JMS MESSAGEPRODUCER memory leak.                                                                                                                                  
   IC47447 - Messages not acknowledged when using CONNECTIONBROWSERS
             with AUTO_ACK or DUPS_OK sessions.                                                                        
   IC47481 - Multi-threaded client return MQRC_ALREADY_CONNECTED.                                                                                                              
   IC47804 - MQ MSCS resource fails to apply local MQM group
             permissions to the dirs containing the queue manager data
             even after IC43947.                                      
   IY72218 - MQDISC fails with MQRC_HCONN_ERROR (2018 0X7E2) and the
             CICS application returns abnormal termination u8035.                                                      
   IY72519 - AMQ9652 error message generated incorrectly when the
             cryptographic store / key repository password has expired.                                                    
   IY72714 - Failure of LDAP server providing O/S user identification
             data to wmq through the GETGRENT interface observed on
             Solaris.                                          
   IY72844 - Queue manager cannot restart: FDC with probe ID HL083114.                                                                                                          
   IY72879 - Continuous use of one MQQUEUEBROWSER for several
             MQQUEUEENUMERATIONS uses too much memory.                                                                        
   IY72981 - Truncated was FDCs (Probes ZF178* to ZF216*).                                                                                                                      
   IY72996 - Sigsegv in XPPRUNDESTRUCTORS for channel using SSL.                                                                                                                
   IY73062 - Selector ignored on CONNECTIONCONSUMER.                                                                                                                            
   IY73202 - Software may get permissions failure reading AMQCAP.INF
             file.                                                                                                      
   IY73543 - Probe XC307004 FDC from XLSREQUESTMUTEX (Linux only).                                                                                                              
   IY73548 - MQ may write a XC130003 FDC under ZCPQUERYTERMINUS when
             using XA.                                                                                                  
   IY73579 - MQMESSAGE.RESIZEBUFFER(INT SIZE) value ignored.                                                                                                                    
   IY73907 - FDC with probe XC006001 from XCSFREEMEM from the
             repository manager process.                                                                                      
   IY73941 - Queue manager restart failure (loop) after syncq/channel
             definition file become out of sync.                                                                      
   IY74045 - RM409000 FFST from RRIWAITSECONDARY.                                                                                                                              
   IY74092 - Parent publish subscribe broker ends abruptly when a child
             broker is started (FDC probe PU522010).                                                                
   IY74175 - XLSRELEASESOCKETMUTEX FDC with probe XY033001, no such
             file or directory.                                                                                          
   IY74339 - Sigbus/sigsegv in KQIINQUIREQUEUEHANDLESTATUS.                                                                                                                    
   IY74420 - MQ hang following PTHREAD_CANCEL on Solaris.
             XCSKILLTHREAD, XLSLOCKMUTEXFN MCATYPE(THREAD).                                                                        
   IY74567 - ALTDATE and ALTTIME of clusqmgr displayed twice on WMQ5.3.                                                                                                        
   IY74802 - Probe XC015001 FDCs, XECS_E_BLOCK_ALREADY_FREE, from
             XCSFREEQUICKCELL.                                                                                            
   IY74818 - WMQ not rolling back a transaction after XA calls
             return XAER_NOTA.                                                                                                
   IY74915 - Performance impact on AIX when an API exit is invoked.                                                                                                            
   IY75252 - MQ commands fail if the MQ files path is specified at the
             end of the path string and is not terminated with a
             colon (:).                                          
   IY75467 - WMQ broker dies with probe XC130003 FDC in function
             FAIADDERRORTAG.                                                                                                
   IY75589 - MQJMS1061: Unable to deserialize object message due to
             JAVA.LANG.CLASSNOTFOUNDEXCEPTION when using WebSphere MQ.                                                  
   IY75657 - Cluster receiver channels do not work with message retry
             exits.                                                                                                    
   IY75854 - Publishing applications are delayed by up to 60 seconds
             when publishing. Error 2033 MSG_NOT_AVAILABLE return code
             is seen.                                        
   IY76063 - Channels in stopping/binding state which cannot be stopped
             using STOP CHL(CHLNAME) MODE(FORCE).                                                                    
   IY76101 - SIGSEGV in AMQFCXBA after MQRFH2 message sent to
             SYSTEM.BROKER.CONTROL.QUEUE.                                                                                      
   IY76314 - XA Client ending abruptly leaves outstanding units of work
             locked until they span the active log, when they are
             backed out.                                          
   IY76712 - Unpredictable results when the topic associated with a
             durable subscription changes when using the MQ broker.                                                      
   IY76799 - Failed call to GETPEERNAME leaks file descriptor in
             AMQRMPPA.                                                                                                      
   IY76845 - Failure to perform data conversion of an MQRFH2 which
             contains NameValueData which is not aligned on a 4 byte
             boundary.                                            
   IY77059 - Probe ID'S MQ000010 and XY180010 following application of
             IY74420.                                                                                                
   IY77233 - OBject catalog corruption during resource exhaustion.                                                                                                              
   IY77769 - Messages remain on the SYSTEM.CLUSTER.TRANSMIT.QUEUE after
             the channel is suppressed by a CHADEXIT.                                                                
   IY77854 - Non-durable subscription messages not getting cleaned on
             z/OS QUEUEMANAGER (or when SUBSTORE = QUEUE is used).                                                    
   IY78429 - Channel process (AMQRMPPA) may fail due to bad data from
             pre-CSD10 Java client.                                                                                    
   SE20597 - MQM400 RPG file QMQM/QRPGLESRC(CMQCIHG) corrupted in
             MQ V5.3.                                                                                                      
   SE21113 - Browsing message using WRKMQMMSG on local queue, if F11
             pressed for alternative view, the local date column values
             are corrupt.                                    
   SE21176 - MQM400 WRKMQM generates MSGMCH6902 and MSGCZM1212 when
             more than nine queue managers to be displayed.                                                              
   SE21231 - MQM400 agent jobs are not being ended after FDC probe
             ZL000028 has been logged.                                                                                    
   SE21834 - MQM400 STRMQM failed for migrated queue manager with
             MCH0601.                                                                                                      
   SE22006 - CICS header flags for the MQCIH structure not there in
             RPG and COBOL header/copy files.                                                                            
   SE22035 - FFST in component AOTADDENTRY with probe ID AO124001
             causing queue manager to end.                                                                                

D) Fix Pack CSD11 (PTFs U802131 and U802132)
   -----------------------------------------
 
   This is the tenth pack for IBM WebSphere MQ for HP-UX
   Version 5.3 from IBM. It is delivered via PTFs U802131 and
   U802132 for APAR IY67004.
   
 
   For full details of problems included in this fix pack please refer to the
   web site http://www.ibm.com/support/docview.wss?rs=171&uid=swg27007221.
   
   It includes fixes for all the problems listed below:
   

   IC44500 - Cumulative maintenance #10 (CSD11) for WebSphere MQ for Windows V5.3
   IY67002 - Cumulative maintenance #10 (CSD11) for WebSphere MQ for AIX V5.3    
   IY67004 - Cumulative maintenance #10 (CSD11) for WebSphere MQ for HP-UX V5.3  
   IY67062 - Cumulative maintenance #10 (CSD11) for WebSphere MQ for Linux for Intel V5.3  
   IY67063 - Cumulative maintenance #10 (CSD11) for WebSphere MQ for Linux for zSeries V5.3
   IY67005 - Cumulative maintenance #10 (CSD11) for WebSphere MQ for Solaris V5.3
   
   SE19814 - MQM400: Diagnostic testfix for providing additional debuging                
             inside xcswaiteventsem.                                                            
   SE19791 - MQM400-Channel pair remains in retrying/binding status    
             after a network change and does not recover.              
   SE19719 - Channel gets disconnected when committing a batch of messages.
   IY78473 - No workload balancing when using multiple clustered queue
             manager alias.
   IY74278 - SIGSEGV FDC with AQHIMAGESIZE in the call stack, at CSD10                  
   IY73014 - Build up of AMQRMPPA processes                                            
   IY72849 - Message corruption getting messages > 4k in Java                          
   IY71943 - Channel agent thread accumulation                                          
   IY71335 - Channel remains in stopping status after stop channel                      
   IY71223 - SIGSEGV XAOPEN XC130003 extended transactional client                      
   IY71204 - Damaged temporary dynamic queue inadvertently added to pool of            
             reusable queues at startup                                                        
   IY71004 - MQ logs fill up and QMGR won't restart after many AO084010 FDCS            
   IY70415 - incorrect message may be returned to MQGET with MQGMO_WAIT and            
             MQGMO_MSG_UNDER_CURSOR                                                            
   IY70366 - FDC ZD008040 from ZDMOPENDEFERREDQ when starting queue manager            
   IY70233 - RCDMQIMG command to re-create a damaged object unresponsive with          
             FFSTs with probe id XC307070                                                        
   IY69886 - PCF command MQCMD_INQUIRE_Q_STATUS does not return any data if            
             only the default parameters are supplied.                                          
   IY69885 - Running out of semaphores doesn't output a useful error message.          
   IY69883 - FFST with probe id XC130003, COMMENT1 :- SIGSEGV and                      
             ATMQUERYACTIVE in MQM function stack.                                              
   IY69464 - With pipelining enabled, the channel synchronisation file may              
             not be closed by the second thread - no external symptoms known.                  
   IY68875 - WebSphere MQ is not properly re-owning a spinlock from a dead              
             owner. FFST PROBE ID: XC028018 is generated.                                      
   IY68798 - The second thread of pipelined channels fails to return messages              
             to XMITQ when channel fails, leaving XMITQ in uncom(yes) status.                  
   IY68509 - Customer is receiving FDC with XC015001 from XCSFREEQUICKCELL.            
             Fix for APAR IY60472 was supposed to resolve problem.                              
   IY68487 - UserIDs between 9 and 12 characters on UNIX WMQ clients are                
             passed to WMQ server as 'UNKNOWN'.                                                
   IY67891 - MQ cluster repository process fails with probe id RM220005                
   IY67232 - Slow MQ channel startup/shutdown due to status table locking              
   IY67176 - Command server crash with SIGSEGV XC130003 when processing                
             channel PCF commands with no OAM.                                                  
   IY67021 - Handle leak in JMS producing application (2017-                            
             MQRC_HANDLE_NOT_AVAILABLE).                                                        
   IC46238 - Channel terminates on client connected to server at 5.3 FP10                
             with probe RM046002 FDCs - INVALID DATA FORMAT                          
   IC46074 - Client channel to Z/OS never times out after a connection drop            
   IC45816 - XC130031 and HL081010 but no message when logpath is incorrect            
   IC45414 - AMQZLAA0 uses 100% CPU while loading a queue with persistent              
             and non-persistent messages                                                        
   IC43749 - Shift-out character truncated when message data ends with DBCS            
   94315   - SSL authentication with JMS realtime node fails from JMS client              
             when JDK1.4.2 is used at client side with LEGALARGUMENTEXCEPTION                  
   94168   - Using CRL with JMS, with revoked certificates, the first                    
             connect fails but following connects succeed.                                      
   93078   - Complete shipment of fix for IC43892                                        
   92775   - use correct bind option when putting to a clustered queue                    
             manager alias.                                                                    
   92244   - Channel namelist alteration on the local partial repository                  
             queue manager                                                                      
   89105   - unable to view queues belonging to remote qmgr through MMC                  
   87457   - Invalid property for a COM.IBM.MQ.JMS.MQTOPICCONNECTIONFACTORY:              
             MAXBUFFSIZE in WebSphere MQ V5.3 fix pack 8 JMSADMIN.                            

 
E) Fix Pack CSD10 (PTFs U800392 and U800449)
   -----------------------------------------
 
   This is the ninth fix pack for IBM WebSphere MQ for HP-UX
   Version 5.3 from IBM. It is delivered via PTFs U800392 and
   U800449 for APAR IY62486.
   
 
   For full details of problems included in this fix pack please refer to the
   web site http://www.ibm.com/support/docview.wss?rs=171&uid=swg27007222.
 
 
   It contains fixes for all the problems listed below:

   IC42841 - Cumulative maintenance #09 (CSD10) for WebSphere MQ for Windows V5.3
   IY62474 - Cumulative maintenance #09 (CSD10) for WebSphere MQ for AIX V5.3    
   IY62486 - Cumulative maintenance #09 (CSD10) for WebSphere MQ for HP-UX V5.3  
   IY62515 - Cumulative maintenance #09 (CSD10) for WebSphere MQ for Linux for Intel V5.3  
   IY62516 - Cumulative maintenance #09 (CSD10) for WebSphere MQ for Linux for zSeries V5.3
   IY62503 - Cumulative maintenance #09 (CSD10) for WebSphere MQ for Solaris V5.3
   
   SE18835 - MQM400-MSGAMQ9543 FDC RM012000 in RRXACCESSSTATUSENTRY status          
             table corruption - locking problem.                                    
   SE18376 - MQM400 WRKMQMMSG fails with MQRC_MD_ERROR on migrated queue.
   SE18138 - MQM400-Agent fails with MCH3601, attempting to get from a queue.        
   IY69760 - shared memory leak for each connection where a syncpointed              
             MQGET/MQPUT is performed.                                              
   IY69467 - Log space leak during XA transactions observed at WMQ5.3 CSD08          
             and CSD09.                                                              
   IY67844 - MQCONN after fork without exec in unthreaded application                
             returns 2059 on HP-UX and AIX.                                          
   IY67371 - Pub/sub application fails with MQJMS1061 after applying fix            
             pack 08.                                                                
   IY67239 - The WebSphere MQ JMS client sends incorrect TSH data.                  
   IY67178 - A JMS application hitting IY67239 causes the channel pool              
             process to trap.                                                        
   IY67165 - Connection problems when using an MQ topic connection                  
             with multicast network addresses.                                      
   IY67125 - Post installation script does not set mqm ownership to                  
             files installed under /var/mqm/tivoli.                                  
   IY66826 - CLUSSDR does not start, QMGR cache status starting.                    
   IY66583 - Readme file for CSD08 is confusing with GSKit/MQSeries.                
   IY66581 - WebSphere Application Server listener ports do not stop and            
             restart following a JMS exception.                                      
   IY66462 - Message on cluster command queue read multiple times.                  
   IY66331 - When MQPMO.RECSPRESENT is set in a client application MQPUT1            
             fails with 2154 (MQRC_RECS_PRESENT_ERROR).                              
   IY66326 - WebSphere MQ queue manager ends after user manually kills              
             MQRRMFA.                                                                
   IY66278 - XC130003 (SIGSEGV) from XEHEXCEPTIONHANDLER with a large number        
             of threads (>1024) in a single WMQ client process connecting to WMQ.    
   IY66048 - MQ JMS throws exception MQJE001: completion code 2, reason 2090.        
   IY66042 - Dynamic queue corrupted when one thread deletes queue whilst            
             another thread opens the (partially) deleted queue.                    
   IY65613 - Queuebrowser does not show underlying jmsexception.                    
   IY65612 - Channel fails with AMQ9636 when DN of a cert contains escaped          
             characters such as , and sslpeer is specified.                          
   IY65447 - MQ Java client allows the get of a message whose size                  
             is greater the the MAXMSGL value on the SVRCONN channel.                
   IY65287 - Unblock sigusr1,sigusr2 and sigalrm in RUNMQTRM.                        
   IY65033 - Client MQGET fails with 2009 MQRC_CONNECTION_BROKEN after the          
             AMQRMPPA terminates with sigbus during conversion of an MQRFH2.        
   IY64640 - MQRC_SYNCPOINT_NOT_AVAILABLE from MQPUT/MQGET after beginning          
             new Tuxedo transaction using dynamic resource management.              
   IY64428 - Cluster migration problem - when a 5.3 queue manager is added          
             to a 5.2 cluster, FDCs from ZXCRESTOREOBJECT are created.              
   IY64363 - SIGILL in INIT_TRACE in LIBMQJBND05.SO.                                
   IY64349 - Channel hang after a comms failure as a result of a failed              
             DNS lookup.                                                            
   IY63833 - C++ SSL connection fails with 2381 MQRC_KEY_REPOSITORY_ERROR.          
   IY63820 - Unblock sigusr1 before calling the user application. RUNMQTRM          
             of MQ V5.3 masks signal while MQ V5.2 does not.                        
   IY63458 - Sslpeer value is incorrectly checked by WebSphere MQ which              
             results in channel failure, including error AMQ9636.                    
   IY63426 - Refresh cluster repository manager repeatedly ends abnormally.          
             miscalculating SSLPEERNAMEPTR, an internal pointer to SSL peer          
             name string.                                                            
   IY59833 - Channel goes to initializing when started from script.                  
   IC45588 - JMS client application fail with 2009 (MQRC_CONNECTION_BROKEN)          
             at receive.                                                            
   IC44243 - WebSphere may forget MDB message selectors after a long time.          
   IC43892 - MQ sample program AMQSBLST generates duplicate MQMD.MSGID values.      
   IC43762 - Default personal cert is used to authorise client during SSL            
             handshake when IBMWEBSPHEREMQUSERNAME cert does not match.              
   IC43533 - Cluster: only suspend or resume cluster queue manager                  
             objects which are not deleted.                                          
   IC43515 - COM.IBM.MQJMS.JAR contains an incorrect class-path statement in        
             the file MANIFEST.MF.                                                  
   IC43176 - Command server reports RC 2005.                                        
   IC43014 - Failure to retrieve a large segmented message with                      
             MQGMO_BROWSE_MSG_UNDER_CURSOR.                                          
   90564   - Support added for use of ';' and '#' characters in XA_OPEN              
             string, as required by Informix.                                        
   90299   - Queue manager cannot restart and/or damaged objects with                
             potential message corruption following restart.                        
   87597   - Client applications segv when using large number of threads            
             simultaneously connected to WebSphere MQ.                              
   82774   - Provide PID and program name of asynchronous signal sender.            

 
F) Fix Pack CSD09 (PTFs U498684 and U498685)
   -----------------------------------------
 
   This is the eighth fix pack for IBM WebSphere MQ for HP-UX
   Version 5.3 from IBM. It is delivered via PTFs U498684 and
   U498685 for APAR IY57557.
   
 
   For full details of problems included in this fix pack please refer to the
   web site http://www.ibm.com/support/docview.wss?rs=171&uid=swg27007218.
 
 
   It contains fixes for all the problems listed below:

   IC41042 - Cumulative maintenance #08 (CSD09) for WebSphere MQ for Windows V5.3
   IY57552 - Cumulative maintenance #08 (CSD09) for WebSphere MQ for AIX V5.3  
   IY57557 - Cumulative maintenance #08 (CSD09) for WebSphere MQ for HP-UX V5.3  
   IY57559 - Cumulative maintenance #08 (CSD09) for WebSphere MQ for Solaris V5.3  
   IY57567 - Cumulative maintenance #08 (CSD09) for WebSphere MQ for Linux for Intel V5.3  
   IY57568 - Cumulative maintenance #08 (CSD09) for WebSphere MQ for Linux for zSeries V5.3
   
   SE16933 - MQM400-MSGMCH0601 FDC XY353001 in XCSALLOCATEQUICKCELL causing    
             agent crash after a timing problem within XLLSPINLOCKRELEASE.      
   IY65599 - Incorrect truncation of a queue greater than 2gb in size,          
             causing read beyond end of file and leading to a damaged object.  
   IY65279 - Allowing applications and CICS Switch Load file to not need a      
             re-link post fix pack 5.                                          
   IY63499 - Log full condition in a RCDMQIMG operation, reported by probe      
             HL010004 FDC, may cause unrecoverable queue corruption.            
   IY62636 - Setting MAXMSGL of a channel to 0, should mean the MAXMSGL of      
             the queue manager is used.                                        
   IY62101 - XC130004 for SIGSEGV out of KPISPIADOPTUSER instead of 2035        
             MQRC_NOT_AUTHORIZED.                                              
   IY61664 - Cleanup thread returns 2058 when jms client connection to          
             default queue manager (no QMNAME given in TCF).                    
   IY60992 - XC130003 FDC after AT061010 FDC under the function ATXSTART.      
   IY60843 - Message selectors that contain the <> (not equal) operator do      
             not work.                                                          
   IY60786 - FDCS from *MEMBLOCK components with probe id like XY398006        
             when enquiring queue handle information.                          
   IY60765 - JMS spec states that  a close terminates all pending message      
             receives on the connection when a session.close() is invoked.      
   IY60590 - Queue manager hangs after alter QL(SYSTEM.AUTH.DATA.QUEUE)        
             QDPHIEV(ENABLED).                                                  
   IY60472 - XC015001 from XCSFREEQUICKCELL showing XECS_E_BLOCK_ALREADY_FREE.  
   IY60448 - Spurious AMQ9546 error output on starting channel from RUNMQSC.    
   IY60106 - .FDC file cut with HL142100 from MQLOOPEN upon CRTMQM.            
   IY59854 - Heap memory leak with each thread created when tracing is on.      
   IY59661 - Output from  RCDMQIMG -T ALL  does not report syncfile recorded.  
   IY58536 - AL036002 FDC in ALSRECORDCHECKPOINT: error 13, permission denied.  
   IY58535 - Queue manager hang following AO175001 FDCs from AOULOCKQHANDLE.    
   IY57545 - Client App creates Non-MQM UID:GID IPC resources/fails with        
             2059 after fix for IY54058 is applied.                            
   IY52823 - Installation or control commands fail on Linux without            
             environment variable LD_ASSUME_KERNEL SET.                        
   IC43531 - Client applications trap when tracing is enabled under            
             WMQ 5.3 CSD08.
   IC43446 - Clusters: AMQ9248 when trying to start a cluster sender channel
             after applying fix pack 8.                                                    
   IC42742 - Application receives a 2009 MQRC_CONNECTION_BROKEN occasionally    
             even though application still alive.                              
   IC42089 - Using JMS_IBM_LAST_MSG_IN_GROUP=TRUE in a message selector fails  
             to return the last message in a group.                            
   84797   - In order to use the request metrics application with WebSphere    
             Application Server version 6 this Ifix must be applied.            
   82952   - GSKit may create a key database file with a file extension        
             of '..kdb', for example 'key..kdb'.                                
   82028   - MQM400: RCDMQMIMG misleading statistics in message AMQ8190.        
   81896   - An MQPUT of a valid segmented PCF message fails with reason        
             MQRC_CFH_ERROR.                                                    
           
           
G) Fix Pack  CSD08 (PTFs U497534 and U497535)
   ------------------------------------------
 
   This is the seventh fix pack for IBM WebSphere MQ for HP-UX
   Version 5.3 from IBM. It is delivered via PTFs U497534 and
   U497535 for APAR IY53823.
 
   Number of APARs in fix pack = 48.
 
   It contains fixes for all the problems listed below:
   
   IC39515 - Cumulative maintenance #07 (CSD08) for WebSphere MQ for Windows V5.3
   IY53820 - Cumulative maintenance #07 (CSD08) for WebSphere MQ for AIX V5.3  
   IY53823 - Cumulative maintenance #07 (CSD08) for WebSphere MQ for HP-UX V5.3  
   IY53862 - Cumulative maintenance #07 (CSD08) for WebSphere MQ for Solaris V5.3  
   IY53871 - Cumulative maintenance #07 (CSD08) for WebSphere MQ for Linux for Intel V5.3  
   IY53872 - Cumulative maintenance #07 (CSD08) for WebSphere MQ for Linux for zSeries V5.3
   
 
   IC39048 - JMS client applications will cease processing messages for
             no apparent reason.  Message consumers will never receive
             messages despite messages being available.  No exceptions
             are thrown.
             Trace shows that a SocketException "connection reset"
             occurred.  This is wrapped in a MQRC 2009 error.
   IC39409 - A channel is defined with a short retry interval.  For    
             example 4 seconds.  When the channel ends with an error,  
             the retry messages occur at 10 second intervals rather than
             4.                                                        
   IC39601 - Clustering.  Many AMQ9456 error messages are found in the  
             queue manager error logs when queues have not been used for
             some time and have this has allowed the subscriptions to
             these queues to expire.                                          
   IC40221 - The PartnerName in the MQCXP structure is not set to the
             logged-on user name from the client when passed to an exit
             on a SVRCONN channel.          
   IC40227 - The user creates a lot of dynamic queues due to the
             caching which occurs from the channel processes (they
             cache 200 queue handles per channel). Over a long period,
             the logs fill up and the queue manager reports problems
             relating to a lack of available log space.
   IC40444 - C++: MQI calls return an 2009 "(MQRC_CONNECTION_BROKEN)"
             when the Queue Manager is restarted.              
   IC40533 - JMS: If using MQConnection Caching an exception  
             javax.resource.spi.ResourceAllocationException is thrown.
             Linked exception is NullPointerException thrown from
             com.ibm.mq.ClientConnectionRequestInfo.fixedEquals method.
   IC40733 - Publish/subscribe support pack MA0C: The broker            
             intermittently stops with an FDC file with probe XC130031.  
             This reports an exception in the pubsub worker process    
             AMQFCXBA.
   IC40975 - A message is put under syncpoint and expires before it is
             committed. During this time, messages are put and got from
             the queue.  The queue depth shown in runmqsc is non-zero,
             amqsbcg does not display the message(s) left on the queue,
             implying they are in a unit of work, but dspmqtrn and
             amqldmpa outputs confirm there is no residual units of
             work outstanding.
   IC41163 - JMS: Putting to a remote fully qualified queue which is not
             in a cluster results in a failure after upgrading from    
             CSD05 to CSD06.  This results in error:                    
             com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason
             2045                                                      
   IC41195 - JMS: Publish Subscribe: An application publishes a message
             and then tries to register a subscriber for that message.
             As expected a 2033 error is returned but a null pointer
             exception is generated:
             Exception:javax.jms.JMSException: MQJMS1016: an internal
             error has occurred.
             Detail:{0}Linked exception: java.lang.NullPointerException
             TopicSubscriber tsubscriber = tSession.createSubscriber(t).
   IC42309 - Connection handle leak with MQ 5.3 on Windows using MQ JMS
             which results in a mqrc_handle_not_available error.
   IY53290 - FDC files are created on two program threads when one      
             thread is opening a pre-existing dynamic queue while      
             another thread is considering it for reuse.  The FDC files
             may have probe IDs of XC304020, XY398007, AO175001 and    
             AO173001.  Object damaged/wounded/missing FDCs can follow.
             The problem is most likely to be seen as problems on two
             separate threads at the same time.
   IY50293 - An FDC file is produced for a read error - disk full. The
             probe ids in the file are      
             AD030001 adiReadFile xecF_E_UNEXPECTED_SYSTEM_RC                
             AQ168001 aqpReadData arcE_PAST_EOF
   IY53827 - A queue manager agent process ends after a SIGSEGV in
             aqhAllocMsg.
   IY53946 - User apps trap if they specify a Format in a message header
             which does not describe the following data.
   IY53967 - Users using Dual Unit of Work find MQ traps.
   IY54058 - An application using MQCONNX and connecting before any    
             other WMQ command is run on the system crashes when with  
             non-mqm uid resources are removed on the system as key      
             semaphores had been created with the wrong uid and gid.
   IY54314 - An infinite succession of FDC files are created with
             probe ID AO180000 from function aouLocateMultipleEntryName.
             The same FDC can also be created when deleting an dynamic
             object which is no longer in use.
   IY54397 - After using the setmqaut command with an object type qmgr
             and the -remove flag, all attempts to issue
             setmqaut -remove commands against that queue manager with
             object type qmgr result in:
             AMQ7085: Object , type qmgr not found.
   IY54507 - SSL: The Certification Revocation List (CRL) LDAP password
             is encrypted before being written to the AUTHINFO object.  
             If the encrypted password contains a NULL, x0, the password
             is truncated at the NULL and then space filled.  This      
             causes the password to be invalid when unencrypted, and so    
             authentication with the CRL LDAP server fails.            
             The message AMQ9667:Bad password for CRL LDAP server; SSL
             channel  A.TO.B is written to the error log.
             Also, in runmqsc the password is returned as incomplete
             when the AUTHINFO object is displayed.
   IY54508 - Clustering: If CLWLMode=FAST in mqs.ini, calling MQXCLWLN
             from a cluster workload exit returns 2102,
             MQRC_ENVIRONMENT_ERROR.
   IY55063 - Errors in setmqaut commands generated by amqoamd.  
             A warning message is generated:                                
             FAIL : setmqaut cannot generate +crt authority for        
             storage_class objects, as none currently exist.            
             An invalid auth spec is generated, resulting in this error      
             message when the generated setmqaut commands are executed:      
             AMQ7097: You gave an authorization specification that is
             not valid.
   IY55290 - Instructions for compiling amqzscg (source for the MQ task
             termination exit library) in shipped sample amqzscgx.c are
             incorrect.
   IY55558 - Channels stop sending messages because a message is stuck  
             on the transmit queue.  If the internal MQGET from the    
             transmit queue fails the message is left on the queue, the
             channel goes into RETRYING.  When the channel restarts at  
             the retry interval the message fails again.  This blocks  
             the channel and stops later messages from flowing. This
             fix moves the failing message to the dead letter queue.
   IY55707 - JAVA: MissingResourceException then rc 2102 when an entry
             cannot be found in a message file.
             Details of the exception:
             An MQJE001: Completion Code 2, Reason 2102
                          (MQRC_RESSOURCE_PROBLEM) can be thrown:                          
             at com.ibm.mq.MQManagedConnectionJ11.authenticate                
             at                                                              
             com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManaged  
             Connection(MQBindingsManagedConnectionFactoryJ11.java:163)      
             atcom.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManaged
             Connection(MQBindingsManagedConnectionFactoryJ11.java:189)      
             atcom.ibm.mq.StoredManagedConnection.<init>                      
             (StoredManagedConnection.java:80)
   IY56525 - Channel stops when trying to send a large message.  The    
             channel must have CONVERT set and be sending a message    
             which can expand on conversion: for example if the target  
             CCSID is 1208 (UTF-8 Unicode).  This may be accompanied by
             an FDC file with probe XC023005, and description 12 - There
             is not enough memory available now from iconv.
   IY56641 - Clustering: If the LOCLADDR attribute is defined on a      
             manual CLUSSDR, the attribute is not used when the channel
             is started the second time.  Instead, the LOCLADDR is      
             copied from the CLUSRCVR in the cluster cache, if present.
             The attribute is used if there is no cache copy of the    
             CLUSRCVR, that is if the channel is being started for the    
             first time.  Change this so that the IP address and port  
             that the outbound channel binds to is a merger of the IP  
             address from the LOCLADDR on the manual CLUSSDR, and the  
             port range from the cluster cache.  If there is no port    
             range in the cache, the port range from the CLUSSDR    
             LOCLADDR is used.
   IY56696 - dspmqtrn is incorrectly returning 71 'Unexpected Error'
             when 102  'No Transaction Found' is expected.
   IY56725 - If an application calls MQCONN/MDISC in a loop in an MQ
             client application,  a memory small leak may be seen.
   IY56861 - Problems recording media imaging for linear logging:            
             rcdmqimg hangs after a segv.                                
             With the -z option rcdmqimg runs to completion without a  
             problem but without the -z option the expected messages are
             written to the MQ logfiles but the command does not        
             terminate.                                                
   IY56956 - The UNIX man pages do not show the same information for
             SETMQAUT as the system administration manual.  
   IY57062 - SSL: When using a multithreaded client application
             connecting to MQ using SSL, an FDC file reporting a SIGSEGV
             with probe XC130003 is received.
   IY57683 - Channels: When a channel is started, the short and long
             retry counts, SHORTRTS and LONGRTS, are not always reset.
   IY57774 - When a JMS Publisher publishes messages on a topic, the
             first message takes a long time to be published.
   IY60052 - At fixpack 07 level, if a queue damaged many FDC files with
             Probe Ids of AO173001 from component aouLockObjectCatalogue
             and AO175001 from component aouLockQHandle.  The queue
             manager then hangs.        
   IY60601 - JMS: Memory leak when users create many MQQueueReceivers
             within a single session.
   IY60895 - An FDC file is created with Probe Id ZF048020, from        
             component zfu_as_searchprincipallist with a major error    
             code of 16 (EBUSY) returned from xcsSetgrent.              
   PQ89406 - JMS: A JMS QueueReceiver with JMSXDeliveryCount < 1 will
             ignore MQ messages that have been rolled back once.
             An MDB with selector whatever and JMSXDeliveryCount < 2
             will ignore MQ messages that have been rolled back once.
             An MDB with selector whatever and JMSXDeliveryCount < 1
             will not pick up any MQ messages.
   SE14442 - The PNGMQMCHL command (iSeries only) and the MQSC
             command 'PING CHANNEL' fail when SSL is enabled, but the
             channels start and operate correctly.
   SE14675 - RUNMQLSR (MQ threaded listener) is ending unexpectedly with
             an exception (MCH3601 on iSeries) when ending dual
             pipelined channels.  
   SE15031 - The Queue Manager ends unexpectedly and creates an FDC file
             with probe id AQ080000, from component aqhLoadMsgDetails
             and Major Errorcode of STOP_ALL.          
     76916 - SSL:JAVA: setting the tcf.setSSLPeerName("") the following
             exception is created:
             javax.jms.JMSException: MQJMS1006:  
             invalid value for SSL Peer DN:                            
     78176 - JMS: add instructions to sample file JMSTestApplet.java
     78814 - JMS: creating a Temporary Queue results in a
             NullPointerException from
             com/ibm/mq/jms/MQConnection.createTemporaryQueue.
     79498 - A long running application which spawns threads that      
             connect to MQ, but which end the thread without explicitly
             disconnecting, leave unused agent processes running.      
     79892 - JMS: Connection Meta Data is reporting JMS version as 1.0  
             but this should be 1.1.                                    
     79906 - an FDC file is created with Probe Id XC130004, from        
             Component xehExceptionHandler.  The function stack shows  
             the function executing is xcsCheckSubpoolProcessH.        
     80503 - Inquire qstatus with tracing on results in the agent
             process ending with an FDC file created with Probe Id of
             XC130031 from Component xehExceptionHandler and the last
             entry in the MQM Function Stack is
             kqiInquireQueueHandleStatus.
     80772 - Oracle.  An application using the Oracle database calls    
             dlclose then exit, at which point the application gets a  
             SIGSEGV and a core dump.
     81303 - JMS: The JMSXDeliveryCount is incorrectly calculated.  
   81611.1 - Add information in Doc section for APAR IC34863
             (shipped in Fix Pack 3 - CSD03). See WebSphere(R) MQ Using
             Java, Chapter 9. The WebSphere MQ base Java classes and
             interfaces, Section MQException above.
     82119 - JMS: When the broker and queue manager are on different
             system types, an javax.jms.JMSException is created:
             MQJMS1087: Unrecognizable or invalid RFH content.            
   
H) Fix Pack CSD07 (PTFs U496730 and U496758)
   -----------------------------------------
 
   This is the sixth fix pack for IBM WebSphere MQ for HP-UX
   Version 5.3 from IBM. It is delivered via PTFs U496730 and
   U496758 for APAR IY50375.
 
   Number of APARs in fix pack = 46.
 
   It contains fixes for all the problems listed below:
   
   IC38022 - Cumulative maintenance #06 (fix pack CSD07) for WebSphere MQ for Windows V5.3
   IY50364 - Cumulative maintenance #06 (fix pack CSD07) for WebSphere MQ for AIX V5.3
   IY50375 - Cumulative maintenance #06 (fix pack CSD07) for WebSphere MQ for HP-UX V5.3
   IY50381 - Cumulative maintenance #05 (fix pack CSD07) for WebSphere MQ for Linux for Intel V5.3
   IY50382 - Cumulative maintenance #05 (fix pack CSD07) for WebSphere MQ for Linux for zSeries V5.3
   IY50378 - Cumulative maintenance #06 (fix pack CSD07) for WebSphere MQ for Solaris V5.3
 
   IC38202 - FDC file indicating a sigsegv exception in component  
             rrxReportError.  
   IC38311 - An API Exit puts a message within the BEFORE CMIT entry      
             using MQPUT with SYNCPOINT which fails when runmqchl is a    
             SENDER or SERVER channel type.  Then it gets a 2195, thereby  
             failing the channel.  An FDC file is created with a Probe  
             ID of AT032010, from component atmStartOp.                        
   IC38899 - JMS: When using a message selector that contains either an  
             IS NULL or IS NOT NULL clause, messages that meet the      
             selection criteria  are not detected and are left on the    
             queue.  
   IC38907 - If the queue manager name passed to amqiclen contains a    
             .(dot), for example MY.QMGR, amqiclen does not produce any  
             output.              
   IC39007 - JMS: After deploying a Message Driven Bean (MDB) that uses  
             an ALIAS queue, the listener port that is bound to the    
             ALIAS queue fails to start, and the following messages    
             appear in the servers SystemOut.log file:    
             JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB  
             <MDB name> , JMSDestination <destination name>  :          
             javax.jms.JMSException: MQJMS2008: failed to open MQ queue  
               at com.ibm.mq.jms.services.ConfigEnvironment.            
                 newException(ConfigEnvironment.java:540)                
             .....                                                              
                com.ibm.mq.MQException: MQJE001: Completion Code 2,    
             Reason 2035 at com.ibm.mq.MQQueueManager.                                        
             accessQueue(MQQueueManager.java:1527)                              
             .....  
   IC39432 - JMS: When sending a message to a queue in CCSID 819 then    
             receiving the message and putting the message back to the  
             queue exception received. Throwing javax.jms.JMSException:  
             MQJMS1006: invalid value for JMS_IBM_Character_Set:ISO8859_1              
   IC39436 - JMS: If a Connection has been used to create a number of    
             Message Consumers, and an exception is detected on that      
             connection, the Exception Listener for that Connection is    
             called multiple times with the same exception.  
   IC39898 - JMS: When setting the correlationId in a message and        
             setting the same selector on the MessageConsumer, the      
             message is not received.  This works with base ascii        
             characters but with characters greater than hex 80 or      
             Unicode in the correlationId the get fails.                                                  
   IC39916 - When rcdmqing reaches a temporary dynamic queue while      
             recording the objects, it creates an AMQ7087 msg:      
             Object AMQ.xxxxxx , type queue is a temporary object and    
             fails to record the rest of the objects.                    
   IY29028 - SDR channels stay in INITIALIZING state during start-up.  
   IY35297 - Clustering: MQSeries did not return an error when an          
             MQCOMMIT was not successful in a clustering environment.      
   IY47766 - After enabling pipelining on a channel that sends messages  
             larger then 4MB, regular AMQ9514 'Channel <name> is in    
             use' and AMQ9558 'Remote Channel is not currently    
             available' messages are reported.  
   IY49438 - MQBEGIN fails with RC= 2128 ( MQRC_UOW_IN_PROGRESS ).  
             Two applications connect to the same queue manager and they  
             run transactions using two phase commit at the same time.    
             If one of them executes a transaction (not using two phase      
             commit) without an MQBEGIN after an MQBACK, the next          
             MQBEGIN of the other application fails with 2128.            
   IY50034 - If running APA (Auto-Port Aggregation) on HP-UX, crtmqm and    
             strmqm exit with a SIGSEGV and produce an FDC file with the  
             following characteristics:                              
             The FDC contains:                                      
             Probe ID :- XC130003                                    
             Component :- xehExceptionHandler                        
             Arith1 :- 11 b                                          
             Comment1 :- SIGSEGV                                      
             and  
             MQM function stack:  
             { zslCheckIfLicensed  
             -{ zslInitNetls      
   IY50439 - An FDC file is created with probe CO052000, claiming to have  
             received invalid data.  This is seen when the sending end      
             violates the TSH protocol.  A new FDC (probe CO000044) is      
             created to directly report the protocol violation and to      
             dump the received data.                                        
   IY50795 - An MQ application takes a long time to do its processing      
             and the transaction monitor software assumes the              
             transaction has timed out.  The queue manager fails to        
             complete the xa_rollback call it receives from the            
             transaction monitor and program amqzlaa0 creates FDC files    
             with probe IDs of XC304020 from xlsDestroyMutex and            
             XY398007 from xcsFreeMemBlock.                                
   IY51152 - An FDC file with probe RM409000 from rriWaitSecondary is    
             followed by XC130003 from rriSendThread2 from the same    
             process (runmqchi), causing the channel initiator to die.    
             This stops all channels running as threads in runmqchi,    
             and stops channels from restarting, and  the channel state  
             stays as RETRYING.  
   IY51386 - JMS pubsub keeps sending messages to queue after    
             MQRC_Q_FULL, RC2053, is returned.  Messages are put to the    
             dead letter queue, until it reaches its maximum queue    
             depth.  
   IY51907 - Checkpointing for users with large queues of persistent    
             messages takes along time and locks out other operations.  
             RUNMQSC is not able to execute.  
   IY51992 - When creating a queue manager using the application group    
             option, for example                                          
               crtmqm -g groupname qmgrname    
             the permissions are not created properly for    
             /var/mqm/qmgrs/<qmgrname>/zsocketapp.    
             The zsocketapp directory is being created with    
             universal access (drwxrwxrwx) which is incorrect.  
   IY52011 - Channels create an FDC file with a 'channel in use'  
             message.  
   IY52065 - Linking the XA switch load file with DB2 version 8 will      
             fail because the xaswit.mak file only contains linker        
             details for DB2 version 7 and earlier.  
   IY52182 - Channel name is missing from message AMQ9514 when    
             displayed by runmqsc.              
   IY52344 - amqiclen -p <qmgr-prefix> does not work; it fails to find      
             mqs.ini.  Create a queue manager with MQSPREFIX set so that  
             the queue manager data is in a separate directory, for        
             example:                                                      
             # export MQSPREFIX=/var/mqm/QMGRDIR                                  
             # crtmqm NEWQMGR                                                    
             amqiclen -c -m NEWQMGR -v -p QMGRDIR</b> gives the error            
             message:                                                            
             Unable to get subpool lock. mqs.ini does not exist.  
   IY52444 - If the queue manager name passed to amqiclen contains a    
             .(dot), for example MY.QMGR, amqiclen does not produce any  
             output.      
   IY52569 - dis q(*) and dis ql(*) runmqsc commands hang unexpectedly  
            while a large queue is being loaded.                                                  
   IY52572 - runmqsc is connected to a remote qmgr and the DIS QS          
             command  is issued with a wild card specified in the queue  
             name.  After the end of the list, runmqsc always displays    
             AMQ8416: MQSC timed out waiting for a response from the      
             command server.              
   IY52575 - Improvements to amqiclen utility:  
             1. SEM: -1 -1 is output if the semaphore set associated    
                with the queue manager QMGR directory is not found.                                  
             2. Add -h flag to print headings in the amqiclen output.            
             3. Add -t flag to work with the -x flag to remove the        
             trace control SEM and SHM IPC resources associated with      
             /var/mqm/errors.                                                    
             4. Add the description of the errno (strerror) to error      
             output.                                                      
   IY52676 - SIGSEGV in zfu_as_SearchPrincipalList, while authenticating  
             the user ID passed from the client.                          
   IY52951 - When strmqcsv is started repeatedly without stopping after    
             approximately 8182 times the strmqcsv command creates an      
             FDC file (probe-id XC307010 from xlsRequestMutex).  Also    
             with each restart of strmqcsv (after 8182 times) strmqcsv                
             returns with AMQ8101 error code.                              
   IY53065 - An FDC file (Probe ID:ZL043050) is generated with a          
             segmentation violation(SIGSEGV).  The customer uses group      
             messages.  This problem is generated only when the            
             receiving process is completed without getting a part of      
             the messages.                                                
   IY53173 - Improve parameters traced on API exits.              
   IY53481 - Return value from rcrmqobj is incorrectly set to 71    
             (Unexpected error) when -z option is used.              
   IY53665 - JMS: Listener Port fails to automatically recover after a    
             broken connection is detected.  The problem occurs after      
             errors:                                                        
             JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB    
             <MDB name> , JMSDestination <jms destination>  :                
             javax.jms.JMSException: MQJMS2002: failed to get message    
             from MQ queue                                                        
               at com.ibm.mq.jms.services.ConfigEnvironment.                  
                  newException( ConfigEnvironment.java:540).....  
             and    
             com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009    
             at com.ibm.mq.jms.MQSession.consume(MQSession.java:2420)    
             at com.ibm.mq.jms.MQSession.run(MQSession.java:999            
   IY53668 - High CPU use in a threaded MCA process, for example:          
             amqrmppa, runmqlsr, or runmqchi, when a channel runs an      
             exit which creates a thread which persists after the exit    
             is called for MQXR_TERM.                                      
   IY53700 - Clustering: There is an alias queue defined on QMGR_A whose  
             target queue (targq) is a queue on QMGR_B.  The queue on      
             QMGR_B is a CLUSTER queue.  The alias queue on QMGR_A is      
             not in the cluster.  When putting a message to the alias      
             queue, the message goes to the Dead Letter Queue with a      
             reason of 2082 0x00000822 MQRC_UNKNOWN_ALIAS_BASE_Q.          
   IY53907 - Clustering: During MQSET a user who has all permissions for  
             the cluster queue, but does not have a put permissions to    
             the   SYSTEM.CLUSTER.COMMAND.QUEUE.  The agent fails with a  
             2035 error and creates an FDC file with probe KN204020 from        
             function KqiDoPendingChangeCLQ.                            
   IY53917 - Sender or server channels went into STOPPED state after    
             migrating from WMQ 5.2 to WMQ 5.3 (see also SE14601)      
   IY53953 - JMS: When a JMS Client application experiences an error      
             delivering a message, it will invoke an Exception          
             Listener if one has been registered.  If the Listener        
             attempts to close the existing connection by calling the      
             close() method on an instance of the MQQueueConnection        
             class, the Exception Listener will hang.                      
   IY54013 - JMS: The customer finds that a message fails to be          
             delivered and the trace shows following information.        
             ServerSession W WMSG0031E:Exception processing JMS              
             Message for                                                      
             MDB <MDB Name>, JMSDestination <jms destination> :                
             java.lang.NullPointerException                                    
              at com.ibm.mq.jms.MQSession.run(MQSession.java:1011)            
              at com.ibm.ejs.jms.JMSSessionHandle.                            
                 run(JMSSessionHandle.java:922)                                
              at com.ibm.ejs.jms.listener.ServerSession.                      
                 connectionConsumerOnMessage(ServerSession.java:697)          
              at com.ibm.ejs.jms.listener.ServerSession.                      
                 onMessage(ServerSession.java:482)                            
              at com.ibm.ejs.jms.listener.ServerSession.                      
                 dispatchServerSession.java:449)                              
              at java.lang.reflect.Method.invoke(Native Method)                
   IY54269 - JMS: A durable subscriber is abnormally terminated (using a  
             kill -9 or ctrl c).  When the application attempts to        
             reconnect the durable subscriber they receive the error      
             message MQRCCF_SUBSCRIPTION_LOCKED.  
   IC41691 - CURDEPTH value does not reset after restart of queue    
             manager.  
     78677   JMS: Unable to set the FIQ field to true in MQQCF.  
     79611 - JMS: JMS 1.1 connection fails  
             caught JMSException: com.ibm.mq.jms.JMSWrappedException:  
             MQJMS6115: An exception occurred while creating the  
             TopicConnection, exception java.io.IOException:  
             MQJMS6228: Minimal client authentication failed because  
             exception com.ibm.disthubmq.spi.AuthException.  
 
I) Fix Pack CSD06 (PTFs U489864 and U489997)  
   -----------------------------------------  
 
   This is the fifth fix pack for IBM WebSphere MQ for HP-UX  
   Version 5.3 from IBM. It is delivered via PTFs U489864 and  
   U489997 for APAR IY46791.  
 
   Number of APARs in fix pack = 41.  
 
   It contains fixes for all the problems listed below:  
 
   IC36779 - Cumulative maintenance #04 (fix pack CSD06) for WebSphere MQ for Windows V5.3  
   IY46790 - Cumulative maintenance #04 (fix pack CSD06) for WebSphere MQ for AIX V5.3  
   IY46791 - Cumulative maintenance #04 (fix pack CSD06) for WebSphere MQ for HP-UX V5.3  
   IY46801 - Cumulative maintenance #03 (fix pack CSD06) for WebSphere MQ for Linux for Intel V5.3  
   IY46802 - Cumulative maintenance #03 (fix pack CSD06) for WebSphere MQ for Linux for zSeries V5.3  
   IY46799 - Cumulative maintenance #04 (fix pack CSD06) for WebSphere MQ for Solaris V5.3  
 
   IC36223 - JMS/Java An exception occurred using MQJMS JMSStreamMessage  
             class java.lang.ArrayIndexOutOfBoundsException at            
             java.lang.System.arraycopy(Native Method) at                      
             com.ibm.jms.JMSStreamMessage.readBytes(JMSStreamMessage.java:  
              416)  
   IC39888 - JMS: If an MQQueue is bound into JNDI and then looked up      
             and cast to a javax.jms.Queue, creating a QueueSender with    
             this object throws an InvalidDestinationException.            
   IC36938 - JMS: A client doing a batched MQGET for a message of      
             more than 32767 bytes can generate an FDC file on the        
             server with probe CO007001 coming from component ccxSend      
             and a return code of rrcE_BAD_PARAMETER, with Comment1        
             showing Length.  On the JMS client side, the symptom may be  
             that, simply, anything over 32k of the message appears        
             incorrect.  
   IC37456 - AMQ8077 Shows a blank object name when INQ is not  
             authorized.  
   IC37515 - Messages remain on the SYSTEM.CLUSTER.TRANSMIT.QUEUE for  
             ever if the queue is removed from a cluster and then added  
    into a cluster while an application is putting messages to  
    the queue.  
   IC37592 - When using the amqoamd utility to dump all authority  
             information with a -n option, no error message or output is  
             received for objects whose name is exactly 48 characters  
    long.  
   IC37728 - After migrating from MQSeries v5.2 to WebSphere MQ V5.3, an  
             auto defined cluster sender channel fails to start  
             reporting error AMQ9519.  This indicates that the channel  
    was not found.  
   IC38247 - If a user who is not in the mqm group attempts to run a  
             command, runmqlsr for example, an access violation error is  
    created.  
   IC39048 - JMS client applications will cease processing messages for
             no apparent reason.  Message consumers will never receive
             messages despite messages being available.  No exceptions
             are thrown.
   IY46567 - Failure of a database (under transaction control by MQ in  
             global units of work) when ThreadOfControl is set to  
    PROCESS can result in MQCMIT calls rolling back the whole  
    transaction and giving a reason code of MQRC_BACKED_OUT.  
    Transaction integrity is not compromised.  
   IY46627 - An FDC file with PROBE ID XY019001 from XUFOPENINIEDIT can  
             be created with message AMQ8501 with a return code of  
    545261579 (LRCE_Q_MGR_NOT_AVAILABLE).  
   IY47486 - runmqsc or amqpcsea hang accessing cluster objects.  
   IY47595 - JMS: V5.3 is unable to use a empty message selector.  
             results in javax.jms.InvalidSelectorException: MQJMS0004:  
             JMS Client has given JMS Provider a message selector with  
    invalid syntax.  
             In MQSeries V5.2 / MA88, the JMS client was able to have an  
    empty message selector.  
   IY47735 - Process amqzllp0 received SIGSEGV caused by a queue having  
             buffers with non-zero write counts on buffers that are  
    NULL.  
   IY47780 - During migration or reinstallation of MQ the directory  
             permissions of existing queue manager directories  
             under /var/mqm/qmgrs are modified to 2775.  
             Many of these directories are created by MQ with different  
             permissions.  
   IY47946 - Scratchpad errors after upgrade from 5.2 to 5.3.  
             Trace shows rrxWriteSync rc=rrcE_RESOLVE_SCRATCHPAD_FAILED  
    Only occurs if IY45615 (in fix pack 5) has not been  
    applied.  
   IY47968 - JMS: non-durable subscriptions created by the application  
    may not be removed or durable subscriptions are still  
    marked as in-use.  This can lead to a buildup of messages  
    or of dynamic queues, as well as MQJMS3023 exceptions (  
    Subscription has an active TopicSubscriber ).  
   IY48070 - Customer writes groups of messages to a queue.  Later, if  
    they try to get a message from this queue, they will  
    receive reason code 2033 (0x000007f1 NO MSG AVAILABLE  
    MQRC_NO_MSG_AVAILABLE).  When this problem occurs, if the  
    customer restarts their queue manager, then the same  
    application is able to get the message successfully.  
   IY48097 - JMS: pubsub applications may encounter problems if they  
             connect to MQ using a TopicConnectionFactory (TCF) that  
    does not specify a queue manager name.  
   IY48122 - JMS: When a pubsub application loses its connection to the  
    queue manager, eg.  by receiving a linked MQException of  
    2009 (MQRC_CONNECTION_BROKEN), 2161 (MQRC_Q_MGR_QUIESCING),  
    2162 (MQRC_Q_MGR_STOPPING) and others, MQ may leave threads  
    hanging in the function SessionAsyncHelper.run().  
   IY48319 - If the reply message from the command server cannot be put  
    to the reply queue passed in the PCF command, the command  
    server fails to put the reply message to the DLQ with an  
    MQPUT1 failure of 2141 MQRC_DLH_ERROR.  
   IY48505 - When a message contains a LineFeed (New Line) character (x  
    15) within the data, MQ is incorrectly converting the x 15  
    character into x 25 .  This data conversion is occurring  
    before the data is passed to the channel Message Receive  
    Exit.  
   IY49061 - Memory leak under agent process when  many dynamic queues  
    are opened using MQOPEN .. MQCLOSE inside a single MQCONN  
    and MQDISC.  
   IY49117 - Clustering: an application may be able to put messages to a  
             cluster queue even if the PUT(INHIBITED) attribute is set.  
   IY49122 - Memory leak in runmqlsr may lead to the queue manager  
    hanging.  
   IY49267 - When using MQPUT1 from a client application to put to a  
    distribution list when the MQOD.Version is set to  
    MQOD_VERSION_2, the call fails with 2136  
    MQRC_MULTIPLE_REASONS (2085, 2086).  It works if the  
    Version is set to MQOD_CURRENT_VERSION (3).  
   IY49278 - When an application puts multiple messages to a queue and  
             they are segmented by the queue manager, it is possible  
    that the program which gets the messages may receive a  
    reason code of MQRC_TRUNCATED_MSG_FAILED if its buffer is  
    not large enough to contain the largest messages on the  
    queue.  
   IY49648 - FDC file with probe ID is created XY180010 when using  
             MQCONNX with connection options MQCNO_HANDLE_SHARE_BLOCK  
    and MQCNO_HANDLE_SHARE_NO_BLOCK.  
   IY49686 - If a multithreaded C++ client application attempts to  
             connect to a Queue Manager which is unreachable the MQCONN  
             waits while the client attempts to connect to the Queue  
    Manager.  During this time all other MQI calls are unable  
    to complete and hang as they are waiting on the MQCONN to  
             return.  This meant potentially other threads would also  
    hang until the MQCONN returned.  
   IY49687 - Message for error AMQ7217 has blank fields.  
   IY49983 - Process amqrmppa creates an FDC file with probe ID of  
    CO400001, component unknown, and major errorcode  
    RRCE_BAD_PARAMETER.  
   IY50128 - FDC file is created if SIGHUP sent to a process running  
             runmqsc.  
   IY50188 - Clustering: sender channels fail to start automatically  
             when messages arrive on the SYSTEM.CLUSTER.TRANSMIT.QUEUE.  
    These channels remain in INACTIVE state after disconnecting  
    normally due to reaching DISCINT.  
   IY50439 - FFST with probe CO052000 is dumped, claiming to have  
             received invalid data. In fact, the invalid data is a copy  
             of part of data just received.
   IY60708 - JMS: Calling the createSender() method on an instance of  
             the MQQueueSession class results in the following exception
             being generated:                                          
                                                                       
             javax.jms.InvalidDestinationException:
             MQJMS0003: Destination not understood or no longer valid.
             at com.ibm.mq.jms.MQQueueSession.
             createSender(MQQueueSession.java:199)
             at com.ibm.ejs.jms.
             JMSQueueSenderHandle(JMSQueueSenderHandle.java:86)
             at com.ibm.ejs.jms.JMSQueueSessionHandle.
             createSender(JMSQueueSessionHandle.java:229)
   75204   - If a queue manager has a name which is a subset of  
             another queue manager name, and if both of these have the  
             same database as an resource manager, then the first queue  
             manager can attempt to resolve indoubt transactions  
             belonging to other queue manager.  
   75816   - JMS: JDBC/XA switch load file and makefile not available  
             HPUX  
   76130   - SSL: Channels may fail if their certificates contain  
             'RFC822Name' information.  
   76370   - runmqsc with no parameters does not show default queue  
             manager name.  
   77458   - Java: java.lang.UnknownError sent to an application if  
        the queue manager is ended while the application is  
    in a sleep.  
   78237   - SSL: Key certificates are not creating with 'CMS' datatype.  
             Please see CSD06 "Special Information" section above for    
             more information and "Upgrading and Downgrading the GSKit"  
             for instructions on how to install a version of GSKit which  
             fixes this problem.                                          
 
 
J) Fix Pack CSD05 (PTFs U487851 and U487852)  
   -----------------------------------------  
 
   This is the fourth fix pack for IBM WebSphere MQ for HP-UX  
   Version 5.3 from IBM. It is delivered via PTFs U487851 and  
   U487852 for APAR IY41941.  
 
   Number of APARs in fix pack = 46.  
 
   It contains fixes for all the problems listed below:  
 
   IC35925 - Cumulative maintenance #04 (fix pack CSD05) for WebSphere MQ for Windows V5.3  
   IY41935 - Cumulative maintenance #04 (fix pack CSD05) for WebSphere MQ for AIX V5.3  
   IY41941 - Cumulative maintenance #04 (fix pack CSD05) for WebSphere MQ for HP-UX V5.3  
   IY41943 - Cumulative maintenance #03 (fix pack CSD05) for WebSphere MQ for Linux for Intel V5.3  
   IY41982 - Cumulative maintenance #03 (fix pack CSD05) for WebSphere MQ for Linux for zSeries V5.3  
   IY41983 - Cumulative maintenance #04 (fix pack CSD05) for WebSphere MQ for Solaris V5.3  
 
 
   IC34863 - JMS: Even though an application is correctly catching and  
             handling MQExceptions being thrown, the error message is  
    still output to System.err.  
   IC35400 - JMS: writeUTF cannot write messages whose length is  
             greater than 256 bytes.  
   IC35424 - Clustering: When a queue was shared in a cluster, but also  
             had a remote queue definition to it, an application was  
             able to put messages on it via the remote queue definition.  
             Puts to it via clustering still fail with  
    MQRC_CLUSTER_PUT_INHIBITED.  
   IC35527 - MQGET of last group msg returns MQRC_INCONSISTENT_UOW if  
             the previous get is backed out.  
   IC35749 - Clustering: where the queue is set to BIND_NOT_FIXED and if  
             a remote queue is set up so that the remote queue manager  
             name is a queue manager alias shared in the cluster, the  
             queue manager name is not filled in on the cluster transmit  
    queue, causing the message to be put to the DLQ on the  
    queue manager which hosts the alias.  
   IC36600 - Application fails to get a message when specific groupid,  
             correlid and msgid are specified, together with a wait  
             interval and the message is put to the queue after the get  
    wait has started.  
   IC36663 - JMS: NullPointerExceptions are created.  
   IC36743 - JMS: the last message in a group is not received when  
             creating a QueueReceiver with a selector of  
    JMS_IBM_Last_Msg_In_Group=TRUE.  
   IY31590 - The programs crtmqm, dltmqm and strmqm hang.  
   IY36646 - An amqpcsea process created an FDC file with probe ID  
             RM487001, which states that a channel that had unexpectedly  
             terminated, but the channel is still running.  
   IY37632 - The sample makefile (xaswit.mak) for sybswit did not    
             work for Sybase V12.                                    
   IY39002 - strmqm may print this message even if setmqcap has been  
             run: "Purchased processor allowance not set (use  
    setmqcap)." if the DefaultPrefix value in the  
    AllQueueManagers stanza is changed in the mqs.ini file or  
             the Windows registry.  The queue manager will continue to  
    start and run normally despite this message.  
   IY40450 - FDCs with probe id KN065001 out of kqiAuthorityChecks with  
             a minor error code of arcE_OBJECT_NOT_FOUND are created  
    when using their own OAM authorization service and have a  
    multi-threaded application.  
   IY40577 - Clustering: SUSPEND status becomes inconsistency between  
             REPOS queue managers and partial queue managers after  
             issuing SUSPEND QMGR CLUSTER(CLSL) command.  
   IY40853 - Queue object becomes damaged when queue contains more the  
             4GB of messages.  Queue shrinks to about 2GB in size.  
   IY41152 - strmqm hangs if the /etc/group file has permissions of 400.  
   IY41671 - MQ hangs if a tuning parameter in qm.ini is set so agents  
             run single threaded.  
   IY42382 - SEGV if NULL queue manager name passed in client MQCONN.  
   IY42481 - Clustering: Workload balancing fails after a clustered  
             queue is put disabled.  
   IY42775 - An application connecting to MQ receives a segmentation  
             fault (SIGSEGV) in the function xllAllocSemNum.  An FDC  
             with Probe Id XC130004 from the function  
    xehExceptionHandler is created.  Near the bottom of the FDC  
    trace, the return code xecS_E_NEED_TO_BE_OWNER is visible.  
   IY43261 - Protocol FDC files with probe RM033006 from function  
             rriReceiveData in the amqrmppa process.  are created as a  
             result of the channel pair being in disagreement over the  
             sequence number.  
   IY43310 - Queue manager crashes after sudden client termination  
             causes a semaphore leak.  
   IY43603 - The MsgId supplied in the PutMsgRecPtr->MsgId is ignored  
             when putting to a distribution list.  
   IY44040 - MQ fails to connect and an FDC file containing Probe Id  
             ZC002040 from component zcpAttachPipe with a Major  
             Errorcode of STOP is created if a tuning parameter in  
    qm.ini is set so agents run single threaded.  
   IY44316 - RQSTR channel fails to start.  
   IY44361 - Failure on restart with an FDC file containing Probe Id  
             AO106010 from component aocRecreateQueue.  
   IY44493 - An FDC file containing Probe Id zc002040 from component  
             zcpAttachpipe is created.  
   IY44507 - crtmqm displays invalid characters when using a Japanese  
             locale.  
   IY44597 - An FDC file containing Probe Id XC015001 from  
             component xcsFreeQuickCell with Major Errorcode  
    xecS_E_BLOCK_ALREADY_FREE is created.  
   IY44669 - Clustering: Following a SUSPEND cluster then an endmqm in  
             quick succession, the amqrmppa process fails to end.  Other  
             MQ processes end and the CPU use increased.  
   IY44673 - SNA channels hang or crash with SEGV reported from  
             cciLu62Receive or cciLu62Send when tracing channel  
             activity.  
   IY44740 - The data in QMgrName (MQCD), ConnectionName (MQCD),  
             ShortConnectionName (MQCD) fields is blank in the MQCD  
    given to a CHannel Auto-Definition exit (CHAD).  
   IY44885 - Memory leak when a process deletes a temp queue while  
             another process has it opened for browse.  
   IY45419 - Listener ends when it receives ECONNABORTED. Error message  
             shows and Errno of 130.  
   IY45566 - When running the PCF command InquireChannelStatus some of  
             the responses contain extra binary zeroes at the end.  
   IY45586 - An FDC file containing Probe Id XY086002 is created.  
   IY45615 - Migration from MQ V5.2 to V5.3 migration causes some  
             channels to go indoubt with error message AMQ9592: Program  
             cannot resolve QMGR object.  EXPLANATION:The attempt to  
             resolve object <objname> on queue manager <name> failed  
    with reason code 2195.  
   IY45940 - After a queue manager ends unexpectedly, it leaves a  
             message on the queue which is not accessible.  
   IY45989 - An MQ listener process terminates with an FDC file showing  
             a SIGBUS error.  
   IY46433 - Attempting to delete a RQSTR channel is rejected because  
             the channel is indoubt.  
   IY49192 - Unexpected errors from MQCONN and FDCs with probe id  
             XY324192 after IPC resources are clean up by the user.  
   SE10945 - SEGV trap when reading a large Nonpersistent queue.  
   69042   - Channel name is missing from message AMQ9514. When  
             displayed by runmqsc.  
   70627   - strmqm fails with return code 71, and an FDC file  
             with probe ID AQ066010 created after MQ processes  
    are forcibly ended.  
   71474   - MQOPEN returns 2018 for SE_Cobol and CICS 5.0.  
             See special instructions above for applications using  
    Cobol V5.0  
   73359   - JMS: Creating connection consumer on a null topic gives  
             exception javax.jms.JMSException: MQJMS1077:  
    Connection/destination mismatch which is incorrect.  
   73645   - When any one SSL channel terminates, it may cause the  
             other channels to end unexpectedly.  
   75058   - Sample programs samples/c/xatm/amqsxag0.c and  
             samples/c/xatm/amqsxas0.sqc now show use of backout count.  
   75611   - JMS: NullPointerExceptions are created.  
   75754   - JMS: When using multiple QueueReceivers receiving on same  
             queue, messages can be lost.  
   75886   - JMS: When attempting to create a connection consumer,  
             get a null pointer exception:  
             java.lang.NullPointerException  
             at com.ibm.mq.FWHelper.fuzzyCompare(FWHelper.java(Compiled Code))  
             ....  
    at com.ibm.mq.jms.MQTopicConnection.createDurableConnectionConsumer(MQTopicConnection.java:511)  
             ....  
   75958   - JMS: When migrating a subscription a null pointer exception  
             in QueueSubStore .close() is created.  
 
 
       
 
K) Fix Pack CSD04 (PTFs U486875 and U486876)  
   -----------------------------------------  
 
   This is the third fix pack for IBM WebSphere MQ for HP-UX Version  
   5.3 from IBM. It is delivered via PTFs U486875 and U486876 for  
   APAR IY38743.  
 
   Number of APARs in fix pack = 37.  
 
   It contains fixes for all the problems listed below:  
 
   IC35383 - Cumulative maintenance #03 (fix pack CSD04) for WebSphere MQ for Windows V5.3  
   IY38742 - Cumulative maintenance #03 (fix pack CSD04) for WebSphere MQ for AIX V5.3  
   IY38743 - Cumulative maintenance #03 (fix pack CSD04) for WebSphere MQ for HP-UX V5.3  
   IY38747 - Cumulative maintenance #02 (fix pack CSD04) for WebSphere MQ for Linux for Intel V5.3  
   IY38762 - Cumulative maintenance #02 (fix pack CSD04) for WebSphere MQ for Linux for zSeries V5.3  
   IY38744 - Cumulative maintenance #03 (fix pack CSD04) for WebSphere MQ for Solaris V5.3  
 
   IC35483 - When importing a self-signed certificate created using  
             selfcert.exe (part of Microsoft Office), on Microsoft  
             Windows XP, using either the GUI or amqmcert, WebSphere  
             MQ V5.3 trapped.  
   IC35648 - Using WebSphere MQ for Windows V5.3 MMC Services GUI in  
             DCOM (remote) mode resulted in a trap.  
   IC35684 - API post-get exit returned an incorrect data length.  
   IC35711 - A damaged queue object occurred following a "clear ql"  
             for an unloaded queue.  If on restart the queue file  
             was not recovered from the logs, then when it was  
             loaded an FDC with probe id AQ123002 from component  
             aqqLoadMsgHdr, followed by an FDC with probe id  
             AQ060020 from component aqhLoadMsgChain, occurred.  The  
             reason code is arcE_OBJECT_DAMAGED.  
   IC35786 - An FDC with probe id AS023000 occurred in component  
             adiDeleteFile when using rcrmqobj with a damaged  
             object.  
   IY38042 - When processing a DUOW, the first thread waited up to  
             120 seconds for the second thread to end, and then if  
             it did not end in that amount of time, it terminated  
             the second thread.  This has now been increased to a  
             300 second delay before terminating the second thread.  
   IY38428 - The MQSeries queue manager removes stale IPC resources  
             on startup.  Each MQSeries IPC resource has an  
             associated file in the /var/mqm/qmgrs/QMGR/ area, and  
             the queue manager searches that area for old files, and  
             removes them and any associated IPC resource.  But that  
             algorithm overlooked the fact that the resource may  
             have been removed and reused by another queue manager  
             due to an IPC key clash.  So it may have removed  
             current IPC resources now owned by another queue  
             manager, not stale ones.  
   IY38476 - A COBOL client application compiled for use with  
             WebSphere MQ V5.3 failed with SIGSEGV.  
   IY38893 - An FDC with probe id CO000002 occurred after a TCP/IP  
             transmission problem which caused more bytes to be  
             transmitted than expected for a given message.  
   IY39949 - The setting of environment variable AMQ_SIGCHLD_SIGACTION
             is not recognised.
   IY40050 - An MQSeries channel event message was not generated  
             after error message AMQ9545 (disconnect interval  
             expired).  
   IY40432 - Under certain circumstances, WebSphere MQ could write  
             an FDC showing probe id AQ066030 from component  
             aqhAllocateSpace.  The major errorcode was STOP_ALL, so  
             this error would terminate the queue manager.  The  
             function stack showed that this error happened while  
             loading a queue into memory as part of MQOPEN  
             processing.  
   IY40722 - When channels were started by runmqsc, the channel  
             processes became defunct when the channel stopped.  
   IY41184 - When importing a certificate into a Queue Manager  
             store, error message AMQ9630 ("an expired SSL  
             certificate was loaded") occurred when using either the  
             Explorer GUI or amqmcert.  
   IY42021 - The runmqchl process became defunct when a channel  
             stopped if that channel had been started by the command  
             server.  
   IY42894 - WebSphere MQ V5.3 was changed to handle SIGABRT  
             differently from the way that MQSeries V5.2 handled  
             SIGABRT, when abort() used to dump a core file and  
             abort the process. But in WebSphere MQ V5.3, this was  
             changed to create an FDC and end the process.  After  
             reviewing this with Development, the following changes  
             will be made to the current behavior in WebSphere MQ  
             V5.3:  
                  1. Do not handle SIGABRT received through an user  
                     application.  As a result of this change,  
                     abort() called through an application results  
                     in a core dump and no longer it generates an  
                     FDC.  
                  2. Do not handle SIGABRT when  
                     MQS_ACTION_ON_EXCEPTION is set to ABORT or  
                     ABORT_ALL.  
   IY43097 - Occasionally a failure with return code 2102  
             (MQRC_RESOURCE_PROBLEM) occurred when trying to connect  
             applications to WebSphere MQ V5.3.  When a large number  
             of applications attempted to perform a get operation  
             with large buffer sizes,  the shared memory set was  
             extended, but with incorrect permissions.  This meant  
             that applications run under a user id which did not  
             have mqm as its primary group could not connect to this  
             extent, getting EACCESS from shmat. This was returned  
             as a resource problem.  
   IY43106 - An FDC with probe id XY242001 was produced from  
             component xcsGetpwnam.  This FDC was introduced by APAR  
             IY36461. The intention of the APAR was to create the  
             FDC if the routine failed because the system had run  
             out of file descriptors. The result has been rather  
             different; any failure to find a userID also caused the  
             FDC to be created.  Such a failure, that a userID does  
             not exist, is not an WebSphere MQ error so it would not  
             be correct to write such a message to the WebSphere MQ  
             error logs, so this FDC has been removed.  
   IY43215 - On Turbolinux 8, setmqcap, dspmqcap, crtmqm, strmqtrc  
             and endmqtrc all hung. They appeared to function  
             correctly but ps -ef showed two threads that did not  
             end. Trace showed that the asynchronous signal monitor  
             thread never returned from a sigwait. SIGWINCH was  
             correctly raised against it and diagnostics showed that  
             it was correctly blocked on that thread.  The problem  
             was due to the default sigaction on Turbolinux being  
             different from other flavours of Linux. The correct  
             sigaction had to be set prior to the sigwait in the  
             asynchronous signal monitor.  
   IY43610 - A number of libraries, including the C++ bindings and  
             SNA libraries, were not shipped with fix pack CSD03.  
             The symptoms which may have been seen prior to  
             application of this interim fix included:  
                -> Segmentation violation in WebSphere MQ  
                -> Abnormal termination of WebSphere MQ applications  
                   using the C++ interface  
                -> Diagnostics (e.g. FDCs) not being produced  
                -> Abnormal trace content  
   IY43940 - An object corruption problem occurred following the  
             reloading of a queue which was unloaded due to  
             inactivity.  FDCs occurring as a result of this problem  
             included AQ060020 from component aqhLoadMsgChain and  
             AQ066000 from component aqqReadMsg.  
   IY43961 - A triggered Java application hung when instantiating a  
             new queue manager object.  
   IY44601 - Using runmqsc to display information about channels  
             resulted in an FDC showing probe id PC031012 from  
             component pcmInquireChannel.  Trace history in the FDC  
             showed return code xecS_E_MEM_SET_NOT_FOUND repeated  
             several times over and error message AMQ9224  
             ('unexpected token detected') also appeared in the  
             error logs reporting an unexpected token in the qm.ini  
             file.  
   IY44618 - WebSphere MQ V5.3 hung after executing endmqm -i whilst  
             the queue manager was quiescing.  
   IY44803 - Two problems were found during the final stages of  
             WebSphere Application Server V5.0.1 Enterprise Edition  
             testing:  
                  a) Whilst running a Process Choreographer  
                     application, an except was written to the  
                     SystemOut logfile.  
                  b) Whilst running a stress test of the  
                     compensation function, core and thread dump  
                     file were generated. No messages were logged  
                     into SystemOut logfile but messages were  
                     written to the SystemErr logfile.  
   IY45013 - WebSphere MQ V5.3 JMS hung due to build issues with  
             libmqjbnd05.so and libmqjbndF02.so.  
   IY45091 - If, in an HACMP cluster, a queue manager was failed  
             over to another machine which also hosted another queue  
             manager, then when the failed over queue manager was  
             started, it was not possible to start channels to that  
             instance of the queue manager.  The channels failed  
             with error messages AMQ9502 and AMQ9547.  
   SA95740 - The queue manager terminated abnormally when a  
             checkpoint process encountered a ghost queue that it  
             could not find.  
   SA96031 - If a full repositories entry in a partial repositories  
             cache had the awaitsRepos flag on, then it would not be  
             selected as a possible full repository to which to  
             publish its cluster specific messages. AwaitsRepos can  
             get set if there has incorrectly been a manual cluster  
             sender defined from the full repository to the partial  
             repository. The change ensures that we correctly  
             publish messages to the full repository regardless of  
             the AwaitsRepos flag.  
   SA96071 - Following the fix for APAR IY27208, the calculation of  
             the oldest LSN is incorrect.  In some cases the oldest  
             LSN calculation will include ghost queues that are no  
             longer required.  In the vast majority of cases the  
             likely damage will be limited to reporting an  
             unnecessarily low media recovery LSN at restart.  
             However occasionally it is possible that this could  
             cause us to report too high a media recovery LSN which  
             could cause data integrity problems following a  
             restart.  
   SE09741 - Damage occurred to a queue file when a clear queue was  
             issued against a queue which had not yet been loaded.  
             When the queue file did finally get loaded (not  
             recovered from the logs), FDCs with probe ids AQ123002  
             from component aqqLoadMsgHdr and AQ060020 from  
             component aqhLoadMsgChain occurred.  
   71806   - Fixed IVTRun -ccsid option.  
   73240   - When attempting to use get with convert from legacy  
             applications, problems occurred on the messages  
             produced, such that nulls were left where there should  
             have been blank characters.  
   73772   - When reading messages in codepage 1051 some  
             applications could have failed with index array out of  
             bounds.  
 
 
L) Fix Pack CSD03 (PTFs U485562 and U486241)  
   -----------------------------------------  
 
   This is the second fix pack for IBM WebSphere MQ for HP-UX  
   Version 5.3 from IBM. It is delivered via PTFs U485562 and  
   U486241 for APAR IY36151.  
 
   Number of APARs in fix pack = 44.  
 
   It contains fixes for all the problems listed below:  
 
   IC34802 - Cumulative maintenance #02 (fix pack CSD03) for WebSphere MQ for Windows V5.3  
   IY36147 - Cumulative maintenance #02 (fix pack CSD03) for WebSphere MQ for AIX V5.3  
   IY36151 - Cumulative maintenance #02 (fix pack CSD03) for WebSphere MQ for HP-UX V5.3  
   IY36157 - Cumulative maintenance #01 (fix pack CSD03) for WebSphere MQ for Linux for Intel V5.3  
   IY36620 - Cumulative maintenance #01 (fix pack CSD03) for WebSphere MQ for Linux for zSeries V5.3  
   IY36149 - Cumulative maintenance #02 (fix pack CSD03) for WebSphere MQ for Solaris V5.3  
 
   IC34272 - Under some circumstances, the QName field in the MQWXP  
             (cluster workload exit parameter) structure was not set.  
             This field should be set so that cluster workload exits  
             can route messages properly.  
   IC34714 - After doing a browse MQGET, if the MsgId or CorrelId is  
             set, or the MatchOptions MQMO_MATCH_CORREL_ID or  
             MQMO_MATCH_MSG_ID are set, the next MQGET with  
             MQGMO_BROWSE_MSG_UNDER_CURSOR or MQGMO_MSG_UNDER_CURSOR  
             (ie. non-destructive or destructive get) does not  
             retrieve the browsed message.  
   IC34717 - Multiple problems occurred with large concentration of  
             channels into a single Queue Manager running on the  
             Windows 2000 platform.  
   IC34739 - Problems occurred with amqmcert on Windows NT and  
             problems occurred when viewing certificates in the GUI  
             on Windows NT.  
   IC34774 - Following an exception in MQDISC processing subsequent  
             WebSphere MQ functions (eg. MQDISC or MQCONN) hang.  
   IC34854 - A trap occurred when browsing a queue in the MMC  
             Explorer snapin.  
   IC34874 - An FDC was generated with probe id XY315147 on the  
             WebSphere MQ server during system shutdown because a  
             remote application was continuing to PUT messages to a  
             queue manager residing on the server machine.  The FDC  
             was seen after a restart of the server machine.  
   IC34883 - An error occurred while opening the SUBSCRIBER queue  
             while performing a subscriber close.  
   IC34910 - An FDC with probe id XY051024 occurred from component  
             InitPrivateServices.  This FDC is intended to  
             demonstrate that there are 2 copies of AMQXCS2.DLL in  
             the system, but in this case the 2 copies of the dll  
             reported had the same path - the difference in the 2  
             paths was that one was uppercase and the other was  
             lowercase.  
   IC34948 - Cluster sender channel did not start automatically.  
   IC34985 - If after defining a queue manager, a listener was  
             defined, deleted and recreated then at this point  
             nothing was written to the registry so a reboot lost  
             that listener.  This also applied to any child service  
             (eg. channel initiators or trigger monitors).  
   IC35037 - Problem in the bindings code that prevented the MQPMR  
             from being updated once the messages had been sent  
             using a application java program that put a message to  
             a distribution list. When the program ran in bindings  
             mode, the message ids that were returned were null. If  
             the program was changed to run in client mode, the  
             message ids were returned correctly. In both scenarios,  
             the message ids were valid on the queues.  
   IC35040 - A JMS publish/subscribe subscriber application  
             failed with error message:  
                javax.jms.JMSException: MQJMS2002: failed to get  
                                        message from MQ queue with  
                                        the linked exception  
                com.ibm.mq.MQException: Completion Code 2, Reason  
                                        2003 (MQRC_BACKED_OUT)  
   IC35047 - The command dmpmqaut showed authorities that were valid  
             for a queue manager (ObjectType = qmgr) when displayed  
             for a queue (ObjectType = queue).  
   IC35050 - When using an RFH2 Header with MQMD.MsgFlags set to  
             MQMF_SEGMENTATION_ALLOWED with a message length that  
             was greater than the maximum message length, then an  
             error occurred with Reason Code 2195 (unexpected  
             error).  
   IC35116 - An MQCONN failed with return code 2059 and an FDC with  
             probe id XY441008 occurred in the Shared Memory server.  
   IC35136 - The error MQRC_BUFFER_ERROR was reported incorrectly  
             for an MQAI COM application (ie. a VB application using  
             the classes in the amqzaix COM library) that used the  
             'item' method to query the value of a string.  
   IC35272 - If a message larger than MAXMSGL was put to a cluster  
             queue with MD.MsgFlags set to MQMF_SEGMENTATION_ALLOWED  
             the message was not segmented on the  
             SYSTEM.CLUSTER.TRANSMIT.QUEUE.  The result was that the  
             message was not gettable from the cluster xmitq and the  
             channel continually failed with  
             MQRC_TRUNCATED_MSG_FAILED returned from MQGET.  
   IC35369 - Error message AMQ8343 or any error message with a  
             higher error number gave the wrong text in German,  
             Brazilian-Portuguese and Traditional Chinese.  
   IC35395 - When reading the Service stanza, it was assumed that  
             SecurityPolicy was the last entry. This was not the  
             case if there was also a NameService stanza, in which  
             case the SecurityPolicy was set correctly when the line  
             was found, and reset to default when the line was not  
             found under the NameService stanza.  
   IY31882 - MQSeries queue open information could have been  
             corrupted by processes that opened the same queue at  
             the same time.  
   IY32730 - The component xcsExecProgram did not trace the path to  
             the failed executable to help determine the cause of an  
             'access denied' message being generated.  
   IY34135 - Improve trace information reported for the rcdmqimg  
             command to help determine which objects are preventing  
             media log advancement.  
   IY34300 - Queue manager failed to start and error message AMQ5525  
             was produced.  The error message was accompanied by  
             FDCs with probe ids ZI095207 and ZF095010.  
   IY35557 - An application connected to WebSphere MQ, then at some  
             point all its threads disconnected. This caused  
             WebSphere MQ to uninitialise tracing for that process.  
             Later, multiple threads from that application connected  
             at the same time. WebSphere MQ needed to re-initialise  
             tracing for the process, but there was a small timing  
             window which allowed multiple threads into the  
             initialisation code, and that tripped the WebSphere MQ  
             consistency check and the resulting FDC with probe id  
             XY078004.  
   IY35756 - An error with reason code 2195 (unexpected error)  
             occurred from an xa_prepare in component  
             tmiPerformPrepare.  
   IY35870 - The CPI-C call cmrcv() failed with a SIGSEGV on HP-UX  
             V11.  
   IY36085 - If an MQI application running over an SVRCONN channel  
             stacked in MQGET with MQWI_UNLIMITED, endmqm -i hung up  
             and never stopped.  
   IY36461 - When the number of File Descriptors was running short  
             for a user, generating both informational FDCs and  
             error logs was not possible. If the errors were to be  
             logged in error logs, it would be necessary to open the  
             message catalog file and the error log file for which  
             there are insufficient File Descriptors.  To avoid this  
             problem error logs will no longer will written in this  
             situation.  
   IY36853 - An FDC with probe ID ZF047010 occurred and an  
             xcsGetGrent call ended with 9 during a crtmqm command.  
             This resulted in the crtmqm command aborting but  
             leaving a partially running Queue Manager with no  
             default objects created.  
   IY37338 - An FDC with probe id AT048005 occurred in component  
             amqzlaa0 from routine atxCommit.  The return code was  
             arcE_XAER_PROTO.  
   IY37545 - When WebSphere MQ encountered an error loading a module  
             or resolving a symbol name within a loaded module, it  
             queried the operating system for error text to help  
             resolve the problem.  In some cases, this text may have  
             been lost or overlayed with new and possibly unrelated  
             error information.  
   IY37611 - An LDAP userid was truncated when used to bind to the  
             server for CRL processing.  
   IY37765 - The WebSphere MQ Using Java manual (SC34-6066-00)  
             refers to a Makefile for use with JTA/JDBC coordination  
             via WebSphere MQ base Java (see chapter 7).  The  
             Makefile was omitted from WebSphere MQ for AIX V5.3 and  
             WebSphere for Sun Solaris V5.3.  
   IY38407 - Error messages AMQ6188 and AMQ7622 occurred when trying to  
             start the Queue Manager.  
   IY39991 - After a JMS application received a message from a  
             queue, it attempted to send that message to two other  
             queues. On the second put, the start of the message  
             data was found to be missing.  
   IY40211 - The listener process terminated abnormally, accompanied  
             by an FDC with a probe id of CO052000 and error message  
             AMQ9207.  
   SA95932 - A queue lock was not released before releasing a data  
             mutex and this resulted in a deadlock condition that  
             caused MQSeries to hang.  
   60225   - Provide support for the WebSphere MQ Extended  
             Transactional Clients.  
   66682   - MQS_ACTION_ON_EXCEPTION was ineffective for XA  
             exceptions.  
   67200   - An FDC with probe id XY078004 occurred from component  
             xtrReleaseTraceLock.  
   67470m  - Unicode Topic names are now supported in WebSphere MQ  
             JMS.  
   70015   - SSL channels did not work on Windows NT.  
   70180   - Windows XP (SP0) system supplied certificate resulted  
             in a channel failure as a result of a user error.  
   70294   - QREMOTE with RNAME=QREMOTE name got stuck on the XMITQ.  
   70527   - REFRESH CLUSTER command did not accept "*" as a  
             parameter.  
   70594   - Client connection failed after the SSL channel failed  
             to start because the assigned certificate had no  
             private key.  
   70595   - Client did not check the date validity of an SSL  
             certificate.  
   70684   - Logfilepages could not be set to more than 9999.  
   70703   - If an application was terminated while it was  
             allocating or freeing a memory block in the shared  
             memory heap, then the queue manager could have been  
             halted.  
   70804   - Platform differences between the SSL state attribute  
             caused certificate search failures.  
   70872   - An FDC with probe id ZF154006 occurred in component  
             wasSecServiceInit from program amqzlaa0.  
   71189   - After a queue with size in excess of 2GB was filled  
             with persistent messages, the queue manager was stopped  
             and restarted.  When the application that was putting  
             messages to this queue was restarted, at the MQOPEN the  
             queue was truncated to 2GB in size and the MQOPEN  
             failed with reason code 2101 (MQRC_OBJECT_DAMAGED).  
   71218   - Failed to find mqm as secondary group.  
   71230   - Problems occurred with the cluster creation GUI.  
   71510   - Memory leaks occurred in the MSCS resource monitor  
             process.  
   71569   - If certain criteria occurred, inquire queue status did  
             not always return a correct queue depth.  
   72076.1 - FDCs and exceptions from zcpDetachPipe following Agent  
             Dead FDCs.  
   72217   - Resolves issues where Channel Terminated messages were  
             being issued when a heavily stressed system has  
             thousands of channels starting and stopping  
             simultaneously.  
   72223   - 100% CPU loop in amqrrmfa in a rare timing condition  
             when the registration chain is updated by two processes  
             simultaneously.  
   72307   - Problem where amqrmppa channel pooling processes  
             were not tracked correctly, resulting in a significant  
             number being launched unnecessarily over time on a  
             system where thousands of channels start and stop  
             frequently.  
   72500   - Resolves problems with wrapping trace including hang  
             during wrapping point and incorrect filenames on the  
             Windows platform only.  
   72562   - An FDC with probe id RM220005 occurred in component  
             rrmRepository from program amqrrmfa.  
   61153   - JMSAdmin - Test for InitialContextFactory on classpath.  
             A common problem has been the inability of Java to find  
             the InitialContextFactory class, as specified in the  
             INITIAL_CONTEXT_FACTORY property, in the classpath.  
             The effect of the fix for this defect is to report  
             "Class specified by INITIAL_CONTEXT_FACTORY not found  
             in CLASSPATH".  
   64266   - Improve JMSAdmin error reporting JMSAdmin -v   :  
             specifying the -v option for JMSAdmin will enable  
             verbose output on commands including exception  
             reporting.  
   67166   - NoClassDefFoundException without jta.jar.  MQ base Java  
             required jta.jar on the CLASSPATH at runtime, for  
             example running the MQIVP without jta.jar available  
             fails with a NoClassDefFoundException on XAException.  
   68116   - Unable to change TopicConnectionFactory TRANSPORT  
             property DIRECT to BIND value.  Switching a Topic  
             Connection Factory or Queue Connection Factories  
             TRANSPORT value in JMSAdmin can cause the PORT value to  
             change :  
                 From    To              PORT value  
                 BIND    CLIENT  Set to 1414 (the default value)  
                 BIND    DIRECT  Set to 1506 (the default value)  
                 CLIENT  DIRECT  Unchanged (remains at the default  
                                 value for CLIENT transport 1414, or  
                                 whatever the user has set)  
                 CLIENT  BIND    The Port Property will be removed  
                                 as not valid with transport BIND  
                 DIRECT  CLIENT  Unchanged (remains at the default  
                                 value for DIRECT transport 1506, or  
                                 whatever the user has set)  
                 DIRECT  BIND    The Port Property will be removed  
                                 as not valid with transport BIND  
   68275   - Minor performance improvement to getMessage. Reduces  
             the amount of browsing needed for message selection  
             over the MQI.  
   68382   - Inconsistent identified producer behaviour. An  
             identified producer (i.e. one tied to a specific  
             destination at creation time) in a Point-to-Point model  
             is unable to send to a specified queue, using  
             QueueSender.send(queue, message). In this situation, a  
             JMSException is thrown, stating that such an attempt is  
             an invalid operation for an identified producer.  
             However when using the Publish/Subscribe model, using a  
             publisher which has been tied to a topic at creation  
             time, succeeds.  This is has been corrected with  
             reference to the JMS 1.0.2b Javadoc for QueueSender and  
             TopicPublisher, where in both cases it should actually  
             throw java.lang.UnsupportedOperationException.  
   68422   - Improve SessionAsyncHelper error handling.  
   68741   - Transactions not working with selectors.  Messages are  
             being got outside syncpoint for transacted and XA  
             sessions when the QueueReceiver is using a message  
             selector.  As a result, rolling back the transaction  
             does not backout the message.  
   68762   - iSeries Storage leak on MQGET - NO_MSG_AVAILABLE. MQGET  
             does not ReleaseByteArrayElements when MQ returns  
             MQRC_NO_MSG_AVAILABLE. This causes the heap space to be  
             consumed and threads to drop when 4MB is used.  
   68775   - Linux native library not statically link with  
             /lib/libgcc_s.so.1. Linux native library was built with  
             a dependency on /lib/libgcc_s.so.1 rather than  
             statically linked.  This may cause problems on systems  
             where this library is not available.  
   68780   - Rationalize syncpoint usage on ConnectionConsumer  
             receive. When using ConnectionConsumer, non-persistent  
             messages are now received out of syncpoint if the  
             Session is non-transacted and AUTO_ACKNOWLEDGE or  
             DUPS_OK_ACKNOWLEDGE. This brings ConnectionConsumer  
             into line with the behaviour of asynchronous delivery.  
             This behaviour can be altered through the  
             SyncpointAllGets property of the ConnectionFactory  
             (from JMSAdmin, this is the SPAG property). If this  
             property is set to true (ie. SPAG(YES)) all receives  
             are performed in syncpoint.  Additionally,  
             ConnectionConsumer no longer performs an unnecessary  
             backout at the end of receipt of a batch messages, if  
             the gets were committed.  
   68905   - get() fails with maxmsgsize of zero. In the 'base' MQ  
             classes for Java API, it was not possible to call  
             MQQueue.get() specifying a zero-length buffer. This is  
             now fixed; the call will complete successfully if the  
             message received has no body or with an appropriate  
             MQRC_TRUNCATED_MSG response if the message has any body  
             data.  
   68938   - Fail if Quiesce values for ConnectionFactory and  
             Destination properties cause unexpected returns. The  
             exact behaviour of the Fail If Quiesce property when a  
             queue manager is quiescing was significantly dependent  
             upon the timing of the calls (for example  
             sending/publishing, and creating a receiver/subscriber)  
             in relation to the closing of the queue manager. Under  
             certain conditions with the ConnectionFactory property  
             set to YES and Destination property set to NO, a  
             JMSException would be thrown when the operation would  
             be expected to succeed. This JMSException contained a  
             linked MQException with error codes of 2161  
             (MQRC_Q_MGR_QUIESCING) or 2033 (MQRC_NO_MSG_AVAILABLE).  
             This behaviour has now been corrected in all feasible  
             scenarios, however a 2033 may still occur if the  
             pub/sub broker has been stopped before it processed the  
             publish operation.  
   69623   - Incorrect message lookup in BrokerSubEng. Broker  
             response is set to MQPS_COMP_CODE rather than  
             MQPS_REASON_TEXT.  
   70052   - NullPointerException from durable subscribe and  
             unsubscribe. If the queue manager is quiescing while  
             subscribing to durable subscription now fails with  
             NoBrokerResponseException, and the durable unsubscribe  
             fails with another NoBrokerResponseException, with  
             linked MQRC 2033.  
   70365   - JMS postcard "nickname" can be truncated. Users may  
             previously have entered a nickname of any length in the  
             graphical user interface, which was silently truncated  
             to 18 characters.  It is now impossible to enter a  
             nickname longer than the allowed length of 18  
             characters.  
   70378   - Unable to parse RFH2 containing <../> empty element  
             form.  When reading a message containing a <usr> folder  
             element of the form <name/>, the parse failed. Such  
             messages were not generated by JMS, but could be  
             created by other applications (eg. MQ Integrator,  
             third-party apps). This is now fixed.  
   70409   - Bad exception if no CertStore class available.  An SSL  
             client application which checks against CRLs on a  
             non-1.4 JVM without the CertStore class, then the JVM  
             will throw a ClassDefNotFound exception rather than an  
             MQException.  
   70413   - get-wait poorly handled in Subscriber.  The wait  
             timeout is not reduced in MQTopicSubscriber.getMessage  
             when processing non-matching msgs. This can result in a  
             lock-in where getMessage will never return because a  
             stream of non-matching msgs are arriving.  
   70463   - Exception while closing the sub with SUBSTORE(MIGRATE).  
             NullPointerException while closing a durable  
             subscription using SUBSTORE(MIGRATE), when the  
             subscription has previously been created using  
             SUBSTORE(QUEUE); i.e. when the subscription had been  
             migrated during createDurableSubscription(). Later uses  
             of the durable subscription were unaffected.  
   70694   - JMS WebSphere Sample 3 improved compatibility.  The JMS  
             WebSphere Sample3 (jmsSample3.jar) is now compatible  
             with the WAS 4.0 and WAS 5.0 ejbdeploy and assembly  
             tools.  
   70862   - Messages not cleared when updating durable  
             subscription.  Old messages not cleared when updating  
             durable subscription while using  
             BrokerSubscriptionEngine.  
                70969:  BrokerSubscriptionEngine cannot open  
                        durableSubscription on non-shared queue  
   71007   - Open handles left against durable subscriber queue.  
             Queue handles could be left open against the subscriber  
             queue following a create and close of a durable  
             subscription using SUBSTORE(QUEUE).  
   71036   - Timestamp based selector fails.  When using  
             MessageSelection=BROKER, selectors which use  
             JMSDeliveryMode, JMSPriority, JMSTimestamp or  
             JMSXGroupSeq, will result in no message being delivered  
             even when the selector should evaluate to true.  
   71038   - Null pointer exception when using setString(null) on  
             MapMessage with trace enabled  
   71069   - PSIVT fails with EBCDIC broker (MQSSR problem).  The  
             PSIVT fails when using an EBCDIC pub/sub broker with  
             BVER(V1). IVT fails reporting a bad message received  
             with "JMS_IBM_Format:MQSSR" instead of "MQSTR".  
   71084   - Get matching by correlid does not work for Linux  
             bindings.  Attempting to get a message, by specifying a  
             correlation ID fails when using the Linux bindings. The  
             symptom of the failure is that the get operation  
             succeeds but does not perform the matching and instead  
             returns the first message found.  
   71102   - StringIndexOutOfBoundsException and mangled NLS  
             messages.  Under heavy load, MQException objects could  
             contain mangled messages; occasionally this would  
             result in StringIndexOutOfBoundsExceptions.  
   71131   - MQTopic incomplete equals and hashcode methods.  Not  
             all of the parameters on MQTopic were included in the  
             hashcode and equals methods.  
   71137   - ConnectionConsumer Performance enhancements.  
   71145   - SUBSTORE(QUEUE) cleanup, BVER(V2), ignores wildcards  
             subscribers.  SUBSTORE(QUEUE)-style cleanup ignores  
             BVER(V2) subscribers which use wildcards in the topic  
             name.  
   71159   - Ignore MsgSelection for IP Transport.  When using  
             Transport=DIRECT the setting of the MsgSelection  
             parameter on the TopicConnectionFactory should be  
             ignored as message selection is always done by the  
             Broker in this case.  Previously, attempting to set  
             MessageSelection=BROKER when Transport=DIRECT caused an  
             exception to be thrown erroneously 71166: Add new error  
             message for UserName too long UserNames longer than 12  
             characters are not supported when using  
             Transport=CLIENT or BIND.  
   71167   - Pacing of publish() requests to Broker.  Erroneous 'No  
             Broker Response" exceptions reported when publishing  
             using multiple Publishers on one Session with a heavily  
             loaded Broker.  
   71233   - Performance: improve MQMessage.read* methods.  When  
             reading many small data elements from an MQMessage, the  
             majority of the overhead is in calls to setMode() and  
             trace statements that are not dependent on a  
             conditional test 'if (Trace.isOn)'.  A tidyup of the  
             trace and changing the calls to setMode() to execute  
             conditionally solves the problem.  
   71318   - Thread leak with broken connections.  The thread  
             created for a bindings connection is normally removed  
             during the disconnect call. If the disconnect fails the  
             thread is not removed, and for customers writing their  
             own fail-over/reconnect logic this causes a build up of  
             unwanted threads.  
   71405   - Durable sub fails with multiple Queue approach.  
             Recreating durable subscription after JVM Crash throws  
             javax.jms.JMSException: MQJMS3022 when multiple Queue  
             Approach is used.  
   71433   - Cannot restart queue manager, ConnectionConsumer  
             holding connections.  The JMS code did not properly  
             disconnect non-XA Sessions created from an XAConnection  
             object.  This caused problems from ConnectionConsumer,  
             which may have given rise to just this problem. The  
             problems related to restarting the queue manager after  
             a failure; without being properly disconnected the  
             queue manager could not restart until the WebSphere  
             Application Server process was stopped.  
   71439   - Cannot send deserialized messages.  If a message object  
             gets serialized and later deserialized, attempting to  
             send the deserialized version gives an 'internal error'  
             JMS Exception.  
   71568   - Missing file /java/lib/jdbc/Makefile.jdbc.  Used for  
             building switch file jdbcxxx had been omitted from the  
             AIX and Solaris installation packages. This is now  
             fixed.  
   71696   - TemporaryTopic error conditions should throw  
             InvalidDestination.  A JMSException is thrown in the  
             following circumstances:  
                1. TemporaryTopic used in createSubscriber against  
                   the wrong Connection  
                2. Deleted TemporaryTopic used in createSubscriber  
                3. TemporaryTopic used with  
                   createDurableSubscription Behaviour changed to  
                   throw InvalidDestinationException as required by  
                   the JMS specification.  
 
 
M) Fix Pack CSD01 (PTFs U484024 and U484131)  
   -----------------------------------------  
 
   This is the first fix pack for IBM WebSphere MQ for HP-UX Version  
   5.3 from IBM. It is delivered via PTFs U484024 and U484131 for  
   APAR IY32728.  
 
   Number of APARs in fix pack = 52.  
 
   It contains fixes for all the problems listed below:  
 
   IY32621 - Cumulative maintenance #01 (fix pack CSD01) for WebSphere MQ for Windows V5.3  
   IY32727 - Cumulative maintenance #01 (fix pack CSD01) for WebSphere MQ for AIX V5.3  
   IY32728 - Cumulative maintenance #01 (fix pack CSD01) for WebSphere MQ for HP-UX V5.3  
   IY32729 - Cumulative maintenance #01 (fix pack CSD01) for WebSphere MQ for Solaris V5.3  
 
   IC33707 - Service startup may not have waited for all queue  
             managers to start.  The process is estimated to start  
             in 45 seconds but when there are many queue managers,  
             this time may be considerably longer.  But the 45  
             second estimate was not changed and this resulted in  
             some of the queue managers being stopped and error  
             message AMQ7880 was written to the log.  
   IC33838 - When using the just in time activation of objects  
             within COM+, the application program worked for a while  
             but then hung because an MQGet was being executed  
             before the commit of the previous transaction had been  
             issued.  The point at which it hung was the getcontext  
             within the MQGet.  
   IC34042 - When a CLUSSDR channel to a full repository went  
             inactive due to a DISCINT expiring and was then stopped  
             by using the Stop Channel command) then if a cluster  
             queue was defined on the queue manager, the channel to  
             the full repository (which was in STOPPED state) went  
             into RUNNING state automatically.  
   IC34123 - The queue manager restarted automatically when it was  
             stopped manually through the services panel.  
   IC34193 - An access violation occurred in the amqzlaa0 process  
             when different security was setup on the receiver  
             channel.  An FDC with probeid XC130031 from component  
             xehExceptionHandler.  
   IC34208 - The AlternateUserId was not being used to open a queue  
             manager object when calling Connect from an ActiveX/COM  
             application.  
   IC34235 - When using remote administration from machine A, signed  
             on with a local id on that machine, to another machine  
             B on which the same userid existed but had limited  
             authority (not in mqm group), then an attempt to view the  
             queue manager properties resulted in a trap in the  
             command server, which when running as a service appeared  
             to be hung.  
   IC34362 - Using a revoked certificate when CRL settings were  
             defined so that verification via an LDAP server should  
             occur, the channel started successfully whereas it  
             should have failed because the certificate was  
             revoked.  
   IC34382 - Multiple copies of listener and trigger monitor  
             occurred following a reboot of the machine, where the  
             queue manager start up process included the trigger  
             monitor, listener and channel initiator.  
   IC34383 - Error message AMQ4082 "Unexpected WebSphere MQ error  
             (3015)" occurred when the "apply on channels" option  
             was chosen on a V5.3 MMC Explorer connected to a V5.2  
             queue manager.  
   IC34402 - Using SSLPEER to check one or more attributes (RDNs) in  
             a DN obtained from a certificate failed when an exact  
             match was required on what turned out to be the last  
             RDN in the DN, but it worked if wildcard was specified  
             at the end of the full RDN.  
   IC34442 - When using the *name for a Queue manager name, ActiveX  
             did not return the actual queue manager name to which  
             the user was connected.  
   IC34551 - If the JMS client retrieved a message greater in size  
             than 2K then the message data was retrieved incorrectly  
             if the message data was not accessed prior to another  
             MQGET occurring.  
   IC34583 - MQPMR fields were not filled in during an MQPUT1 call  
             on MQSeries V5.2 or an MQPUT call on WebSphere MQ V5.3.  
   IC34586 - A handle leak occurred on each MQCONN/MQDISC when they  
             were done in a separate thread.  
   IC34855 - The length of a channel name insert was incorrect in  
             some error messages.  
   IC35242 - Error message AMQ5615 occurred when trying to issue  
             CRTMQM commands after installing fix pack CSD05 on  
             MQSeries for Windows NT and Windows 2000 V5.2.1.  
   IY31724 - When an application calls MQBACK at the end of a  
             two-phase unit of work, MQSeries must invoke the xa_end  
             and xa_rollback methods of all associated resource  
             managers.  If a resource manager returned one of the  
             XA_RB* (ie. rollback) return codes to xa_end, it was  
             allowed to return XAER_NOTA to xa_rollback.  Because  
             this option was not reflected in the XA state tables,  
             WebSphere MQ would return error MQRC_UNEXPECTED_ERROR  
             (return code 2195) from MQBACK and write an FDC with  
             probe id TM05000 from component tmiRollbackTransaction  
             with major error code trcE_UNEXPECTED_RM_ERROR.  
   IY31891 - Additional trace points have been added for WebSphere  
             MQ for AIX V5.3 so that any errno value set by a call  
             to system() can be displayed in the trace.  
   IY32787 - On a newly created V5.3 queue manager, a PCF Inquire  
             Channel command to inquire the status of all Svrconn  
             channels returned incorrect values for the  
             SSLCipherSpec key (MQCACH_SSL_CIPHER_SPEC).  
   IY32885 - The Solaris catgets problem (problem id 417950)  
             resulted in WebSphere MQ failing to print an error  
             message from the message catalogue in the normal  
             fashion when the print string in the catalogue is badly  
             formatted.  Instead of the required message, error  
             message AMQ8101 was received when running RUNMQSC.  
   IY32890 - After migrating from MQSeries V5.2 to WebSphere MQ  
             V5.3, the V5.2 queue manager would not restart  
             successfully.  An FDC with probe id AQ066030 from  
             component aqhAllocateSpace was produced.  
   IY32925 - When WebSphere MQ ran out of file descriptors, an FDC  
             was created with probe id XY017001 from component  
             xufOpenIniRead.  However, it did not report the error  
             number properly.  It was likely to be reported as 0.  
   IY33049 - The listener in WebSphere MQ V5.3 did not use the  
             SO_REUSEADDR socket option.  
   IY33171 - After applying the fix for APAR IY32890 and migrating  
             from MQSeries V5.2 to WebSphere MQ V5.3, the V5.2 queue  
             manager would restart successfully but a warning FDC  
             with probe id AQ065010 from component aqhLocateSpace  
             was produced.  
   IY33246 - An FDC with probe id XC287002 from component  
             xstAllocateMemBlock with minor error code  
             SEM_OWNER_DIED occurred when an application died while  
             holding a lock to the queue manager.  
   IY33346 - A problem occurred in component zlaMain where the  
             application dead count was not reset properly when a  
             connection was reused. This caused frequent FDCs to be  
             generated with probe id ZL000028 out of component  
             zlaMain.  
   IY33612 - Uninitialised shared memory data caused a WebSphere MQ  
             agent thread to believe that it has been told that the  
             queue manager was stopping. This caused the thread to  
             terminate the connection with the application. In order  
             for the uninitialised data to cause this, it had to  
             have exactly the right 32-bit value.  
   IY33836 - After migrating from MQSeries V5.1 to WebSphere MQ  
             V5.3, the V5.1 queue manager failed to start, producing  
             FDCs with probe id ZD007030 from component zdmMQCONN  
             and a Major Error code MQRC_ENVIRONMENT_ERROR.  This  
             also produced error message AMQ6090 (WebSphere MQ was  
             unable to display an error message 7DC).  
   IY33837 - After migrating from MQSeries V5.1 to WebSphere MQ  
             V5.3, the V5.1 queue manager would not restart.  Error  
             message AMQ6118 occurred and an FDC with probe id  
             HL081015 (AIX) or HL081916 (other platforms) from  
             component mqlpgolf in program amqzxma0 was produced.  
   IY33871 - While WebSphere MQ was waiting for work to complete, an  
             endmqm -i was issued.  The endmqm process in turn  
             invoked the shutdown function zxcForceStopLQM which  
             then tried to shutdown the OAM but failed with error  
             code MQRC_CONNECTION_BROKEN (return code 000007D9)  
             because the OAM had already been stopped.  
             Unfortunately, the function zxcForceStopLQM treated  
             this as a bad return code and skipped the shutdown  
             procedure.  
   IY34165 - Messages were being got outside syncpoint for  
             transacted and XA sessions when the QueueReceiver was  
             using a message selector.  As a result, rolling back  
             the transaction did not backout the message.  
   IY34432 - The expiry time on some messages was reduced by the  
             time that has elapsed since the messages were first  
             put.  This occurred when rcdmqimg was executed or the  
             queue manager was stopped and restarted. This resulted  
             in some messages being deleted unexpectedly.  
   IY34454 - The commands setmqaut and dspmqaut incorrectly failed  
             with error message AMQ7085 (Type Q not found).  
   IY34652 - The listener failed after the number of file  
             descriptors had exceeded the limit of 252.  
   IY34717 - Ping for non-existent channel caused the command server  
             to SEGV.  
   IY34818 - If the asynchronous signal monitor was attempting to  
             initialize common services in order to create an FDC  
             while main thread was in the process of bringing common  
             services down, then this resulted in a cascade of locks  
             being backed up which then resulted in a hang  
             condition.  
   IY34825 - An FDC with probe id XC130003 occurred in component  
             xehExceptionHandler from program runmqchl_nd.  
   IY34865 - When a JMS application issued QUEUEBROWSER.CLOSE(), the  
             queue handle was not being released.  
   IY36465 - AMQRMPPA processes were left running after endmqm had  
             finished processing.  
   IY36487 - When an exception handler was set for SIGABRT, the saved  
             signal handler for SIGSEGV was overwritten.  If the  
             handlers were not identical then SIGSEGV was not  
             percolated correctly.  
   IY37431 - If there was only one cluster queue and it was set to  
             be put disabled, then the expected return code 2268  
             (MQRC_PUT_INHIBITED) was not returned when putting from  
             a remote queue manager with bind-not-fixed specified.  
             However the message was "put" successfully and ended up  
             on the local SYSTEM.CLUSTER.TRANSMISSION.QUEUE.  
   PQ65576 - The repository manager on a Solaris or HP-UX queue  
             manager running in a cluster containing WebSphere MQ  
             V5.3 queue managers failed. When the queue manager was  
             restarted, it failed again.  The repository manager  
             failed due to a badly formatted message on the  
             SYSTEM.CLUSTER.COMMAND.QUEUE. On queue manager restart  
             the repository manager tried to process this message  
             again, hence the repeated failure.  
   PQ65725 - On migration from an older release of MQSeries where  
             clustering was used, on channel initiator startup the  
             repository manager terminated abnormally due to an  
             unusually formatted message segment on the  
             SYSTEM.CLUSTER.REPOSITORY.QUEUE. The abend would also  
             be seen on channel initiator restart as the message  
             would be re-processed.  
   PQ66006 - Partial repository queue managers no longer  
             acknowledged all instances of a cluster queue some time  
             after a REFRESH (or ALTER QMGR to change the clusters  
             to which queue manager was the full repository) was  
             carried out on a full repository queue manager.  
   SA95280 - Following an MQPUT, with the put message option  
             MQPMO_NEW_MSG_ID specified, that used distribution  
             lists, then the Msgid field of the MQPMR structure was  
             expected to be populated with a unique message  
             identifier but it was not.  
   SA95694 - When putting a message to a distribution list and a  
             unique message identifier was specified, the specified  
             unique message identifier was ignored and a queue  
             manager generated message identifier was given to the  
             message.  
   SA95741 - While ENDMQM processing was being performed, all MQCONN  
             attempts, other than the first MQCONN processed,  
             resulted in FDCs with probe id XC307070 with major  
             return code xecL_W_LONG_LOCK_WAIT.  This was a  
             significant problem if the ENDMQM processing for an  
             installation took a long to complete.  
   67364   - Provide full command-line support in the IBM Global  
             Security product (GSKit).  
   68457   - AES CipherSpecs are now supported on HP-UX.  
 
 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++  
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++  
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Related Information

[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"APAR \/ Maintenance","Platform":[{"code":"PF010","label":"HP-UX"}],"Version":"5.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

WMQ MQ

Document Information

Modified date:
17 June 2018

UID

swg27007108