#########################################################################                                                                      ## COMPONENT_NAME: Websphere MQ                                         ##                                                                      ## FILE: MEMO.PTF                                                       ##                                                                      ## Program Number 5724-A38                                              ## (C) COPYRIGHT International Business Machines Corp. 1994, 2004 ,2008 ## 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.    ##                                                                      #########################################################################Memo for IBM Websphere MQ version 6.0.2.7 for HP OpenVMS Alpha ==========================================================Websphere MQ Information Available on the Internet----------------------------------------------The Websphere MQ product family Web Site is at:       http://www.ibm.com/software/mqseriesFrom this site you can obtain the latest information on thefollowing topics:      . Websphere MQ Family Products News      . Websphere MQ books in HTML or PDF format      . Websphere MQ SupportPacs      . Closed APARs      . Frequently Asked Questions      . Tips and Techniques      . Forums      Please refer to this site for current news on SupportPac availabilityfor Websphere MQ for HP OpenVMS Alpha V6.0      Service and Technical Support-----------------------------This is the second fixpack release for IBM WebSphere MQ version 6.0 on HP OpenVMS Alpha. Websphere MQ version = 6.0.2.7This fixpack release for IBM WebSphere MQ version 6.0 on HP OpenVMS Alpha includes all applicable APAR fixes included in WebSphere MQ fix pack 6.0.2.7 on other platforms, in addition to OpenVMS specific APAR fixes. After the fix pack is applied, the version reported by the dspmqver command is 6.0.2.7This fixpack contains cumulative fixes since Websphere MQ V6.0 and corresponds to service level FP01. The memo.ptf file for this release contains the following sections:  o   Installation and maintenance information  o   Documentation changes  o   Special information  o   CSD history++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++INSTALLATION AND MAINTENANCE INFORMATION----------------------------------------A) Applying Maintenance   --------------------  Maintenance updates can be supplied on CD-ROM, or they 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      *    *  OpenVMS Alpha.                                              *    *                                                              *    ****************************************************************    For details of installation method please refer to Websphere MQ for HPOpenVMS Alpha Version 6.0 "Quick Beginnings"  Chapter 2.  This chapter must also be read in conjunction with the README locatedon the product CDROM. Any subsequent maintenance release of Websphere MQ for HP OpenVMS AlphaVersion 6.0 will contain instructions for its installation.++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++SPECIAL INFORMATION-------------------This is the second fixpack release for IBM WebSphere MQ version 6.0 on HP OpenVMS Alpha. Websphere MQ Version = 6.0.2.7Following are the changes incorporated into this fixpack release:- IPV6 Support has been included in this Fixpack release. - Users running Java API/JMS clients on OVMS need to convert   CCDT (AMQCLCHL.TAB created on OVMS) from index file format   to sequential file format.   (To convert the file, please refer below URL.     http://www-01.ibm.com/support/docview.wss?uid=swg21294013 )    - From this Fixpack level onwards, migration from WMQ5.3 is now   supported for both queue managers and MQ applications. However   it is always recommended to take a physical backup of the   queue manager directories prior to a migration.  The workaround mentioned in the following URL is an alternate  secondary step from this fixpack level onwards, if automatic  migration fails due to unknown reasons.  http://www-01.ibm.com/support/docview.wss?uid=swg1IC58617- XA transaction support for Oracle V 10.2.0.2.0 for Alpha OpenVMS  has been included in this Fixpack release. We suggest customers   apply latest maintenance level for Oracle-V 10.2.0.2.0 for Alpha  OpenVMS in order to get XA to work with WMQ-V6.0. So on top of   Oracle V 10.2.0.2.0 on Alpha OpenVMS, it is mandatory to apply   V 10.2.0.4 patch set.     IMPORTANT INFORMATION FOR EXISTING WMQ6.0 USERS ------------------------------------------------- Separate 32-bit and 64-bit MQ libraries are included in this   fixpack, replacing the default single set of 64-bit MQ libraries   provided in earlier releases of WebSphere MQ V6.  The 32-bit libraries have the same name as the 32-bit libraries   in WebSphere MQ Version 5.3, allowing migration from WebSphere MQ   Version 5.3 without re-compilation. The 64-bit libraries are   appended with _64.     Due to above changes existing V6 customers must perform a one-off   operation to recompile their 64-bit C and C++ applications to   point at the 64-bit libraries appended with _64.  Reasons for having two sets of 64 bit and 32 bit MQ libraries   and requiring the re-compilation of existing V6 applications:    -- Issues related to WMQ-V6.0 Java API/JMS server binding      applications. The WMQ-V6.0 JNI layer was incorrectly     interacting with 64 bit WMQ-V6.0 libraries opposing the      availability of only 32 bit java support on OpenVMS. In      order to resolve this mismatch, in this fixpack we have      chosen default naming conventions for 32 bit libraries.      This approach will help for both WMQ-V5.3 and WMQ-V6.0      MQ Java API/JMS applications. The 32 bit default naming      conventions going to supersede all 32 bit libraries      provided in WMQ-V5.3 releases. For more information,      please refer following URL.     http://www-01.ibm.com/support/docview.wss?uid=swg1IC64910  -- This approach also simplifies migration from WMQ V-5.3  -- Customers are now allowed chose either 64 bit are 32 bit      applications by linking with the appropriate MQ libraries.      All 64 bit MQ libraries are appended with _64, and all 32      bit libraries supersede the MQ libraries provided in      WMQ-V5.3 releases.  Following are the changes incorporated into FP01------------------------------------------------Queue Manager entry in MQS.INI.For any new Queue Manager created after installing FP01 the entry in MQS.INI file will be created using a UNIX style path e.g.QueueManager:   Name=ivp   Prefix=/mqs_root/mqm   Directory=ivpQueue Managers created before installing FP01 will continue to have the VMS style path.This change has been done for defect # 6011.1 mentioned below. Users maychoose to modify the path if they encounter the defect described frequently, else no modification is required.++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++Fix Pack HISTORY================PTF IP22993 ----------This is the Second fixpack release for IBM WebSphere MQ version 6.0 on HP OpenVMS Alpha. It is delivered via PTF IP22993 for APAR IC63800.Websphere MQ version = 6.0.2.7Number of APARS in PTF = 522Followings are the list of fixes included into this fixpack:IC63800 - Cumulative maintenance #02 (Fix Pack FP02) for WebSphere MQ           for HP OpenVMS Itanium V6.0.IC64910 - WMQ OVMS 6.0 - Missing 32 bit MQ shareable libraries in WMQ           V6.0 for HP OpenVMS Itanium.IC64437 - WMQ for Open VMS will incorrectly mark a queue as damaged           in case of system service(sys$get) failure due to ENQ           quota depletion in heavily stressed environment. IC55327 - The logical name AMQ_SSL_DUMP is not documented and only           works with an PING CHL, it does not work even when           attempting to start it - Doc APAR. IC57273 - Channel initiator program (RUNMQCHI.EXE) may fail with           SIGBUS error while attempting to create socket descriptor. IC64431 - WMQ OPENVMS EXECUTION CONTROLLER FAILS WHEN ATTEMPTING           TO START A CHILD PROCESS. AMQ6109 REPORTED FDC PROBE ID           XC037005. IC64399 - WMQ PROCESS RARELY EXPERIENCE SUBPOOL MEMORY CORRUPTION           FROM THEIR PRIVATE ADDRESS SPACE IN A HIGHLY STRESSED           ENVIRONMENT. IC60671 - PROBE XC130003 WITH SIGBUS WHEN USING CLIENT CONNECTION           WITH SSL AND CA FILE IS NOT AVAILABLE AND SSLCAUTH IS           OPTIONAL.IC60760 - OPENVMS: ALLSUBPOOLS LOCK PROBLEM UNDER HIGH LOAD           CAUSING HANG OF QUEUE MANAGER. IC61039 - WMQ User start noticing FDCs with major error code           "xecL_W_LONG_LOCK_WAIT" associated with abrupt           terminations of MQ applications on WMQ/OpenVMS V-5.3           and V-6.0. IC61156 - WMQ V6 users on OpenVMS, who are members of MQ GROUP           (UIC 400,X ) fail to use MQ APIs, in spite of having           MQM identifier in User Authorization File. IC61313 - THE AMQRMPPA PROCESS GENERATES AN FDC WITH SIGBUS ERROR           IF THE "SSLKEYR" ATTRIBUTE OF THE QMANAGER IS SET TO           BLANK. IC61428 - WMQ5.3/6.0 CLIENT USING SSL ENABLED COMMUNICATION THROWS           A SIGBUS SIGNAL WHEN TRACING IS ENABLED. IC62136 - Users of WMQ-V5.3/6.0/OpenVMS will encounter channel           failure if SSLCIPH channel attribute is configured to           use either of cipherspec NULL_MD5 or NULL_SHA. IC63621 - DSPMQRTE COMMAND WITH OPTIONS -M -Q FAIL WITH MESSAGE           AMQ8670: LOADING OF SERVER MODULE '/MQM/LIB/MQM.EXE'           FAILED. IC64400 - STARTING TRACE WITH FILE SIZE LIMIT IN WMQ 5.3/6.0 ON           OVMS RESULTS SIGBUS CREATING AN FDC WITH PROBE ID           XC130003. IC64405 - WMQ 5.3/6.0: AGENT & RMPPA PROCESS THREAD SET OWNER PID           & TID VALUE -1 IN CASE OF FAILURE TO RELEASE MUTEX HELD           BY ANOTHER PROCESS. IC58617 - OPENVMS EXISTING WMQ V5.3 QUEUE MANAGERS CANNOT BE USED           AFTER MIGRATION TO WMQ V6.0 IC55562 - The queue manager fails to start when it encounters high           value for the size of primary set subpool fetched from           the QMSTAUS.INI file. IC60345 - THE SUBPOOL DATA CONTAINING THE PATH FOR THE EXIT           PROGRAMS HAS NOT BEEN INITIALIZED DURING QMGR STARTUP. IC61212 - MQ OVMS V6.0, Process Manager gets in to a tight CPU           bound after issuing endmqm and continues to run even           after the QMgr ends. IZ35444 - QUIESCE SHUTDOWN IS NOT PROPERLY DETECTING THE ABRUPT           ABNORMAL END OF AN APPLICATION IN THE MIDDLE OF AN           MQCONN REQUEST.IZ32752IZ32933 - PROBE ID XY432030 WITH XECP_E_NO_RESOURCE UNDER HIGH           CONCURRENT CONNECTIONS AND/OR LARGE CONCURRENT MESSAGE           TRAFFIC.           IC58970 - Redundant dns lookup calls, even though connection name is           specified in numeric format.  IC59146 - Cannot display svstatus of service with more than 32           characters.  IC59232 - Messages destined for a cluster queue manager alias           are not reallocated from the sctq when a channel is           not running.  IC59341 - Agent does not close the queue file handle after           processing the query inquire queue status.  IC59375 - Description is not available (security/integrity           exposure).  IC59701 - WebSphere MQ JMS clients fail to parse rfh headers           if the jmstype field of the incoming message contains           a namespace.  IC59803 - Extraneous AMQ7216 message with apiexit on           mqrc_q_mgr_quiescing.          IC60061 - AMQ9209 and AMQ9492 messages from network pinger.  IC60304   WebSphere MQ V6 JMS publish/subscribe applications           intermittently experience fatal connection errors.  IC60331 - Mqrc_converted_string_too_big causes runmqdlq           termination.  IC60571 - Messages higher than AMQ5963 give incorrect message           descriptions on non-english Windows.      IZ33489 - Queue manager hangs as a result of an invalid deletion           of in- use log extents.  IZ36469 - Cluster queue disappears without issuing AMQ9456 error           message.  IZ36875 - The FDC code is not correctly checking the addressability           of allcontrol blocks requested to be included in the FDC.  IZ36924 - An internal call to mqback within a channel process fails           with mqrc_environment_error (but with no undue consequence).   IZ38169 - A trace route message with a non-native encoding specified           in its message descriptor, may fail trace route processing.  IZ38484 - Queue file may get damaged by queue manager after file           system full on queue manager data file system.  IZ38767 - AMQ9526 messages reporting message sequence errors memory           leak leading to performance problem.   IZ38922 - Reset channel returns channel not found error when issued           against an auto-defined cluster sender channel       IZ39475 - Queue manager would not restart after receiving FDC stating           arce_q_space_not_available.  IZ40124 - Performance problems when conversion between queue manager           ccsid and queue manager locale is not supported.  IZ40337 - The MQ exception handling environment in the process           amqldmpa is not properly initialized.  IZ40677 - MQ does not retry operation when user group functions           fail with eintr error.  IZ40708 - Always check qmgr name when adopting clusrcvr  IZ40802 - Repeated fdc's with probe XC308035 after MQ thread ends           abruptly while waiting for a mutex.  IZ41026 - Timing window in checkpoint leads to MQ V5.3 queue manager           crashrecovery restart failure. IZ41187 - Mqrc_cluster_put_inhibited was returned when an out-dated           object definition from the cluster repository was           referenced.  IZ41369 - Multiple FDCs with probe ID AQ200020 are continuously           produced.  IZ42215 - Probe AQ066030 from aqhallocatespace leads to secondary           issue of queue manager crash. IZ42282 - Dlq handler should deliver the message even if it fails           to convert application data.  IZ42583 - Queue manager crash following runmqsc command on a           stressed system: dis ql(*) where( curdepth ...).      IZ42988 - Sigsegv in pthread_kill called from xcsrequestmutexsemfull.   IZ43635 - Delayed acks slow MQ tcp channels, especially over           loopback.  IZ44552 - AMQ9430 error message after refresh cluster. IZ44556 - WebSphere MQ V6 JMS applications get a 2195 error followed           by "MQJE043: insufficient data received from queue manager". IZ44595 - Exception in MQ application code leads to FDC with probe           MQ000101 and the application process then exits.  IZ44619 - Queue manager hangs when it should crash following the           corruption of a newly formatted recovery log extent.   IZ45122 - FDC with probe ID XC076011 produced. AMQ6090 message           generated when trying to run MQ applications such as runmqsc.  IZ45279 - For some errors such as AMQ7027 dspmqtrc returns zero (0)           instead of the expected one (1) for failure.  IZ47182 - Reallocation of messages destined for a failing           cluster-channel to working channel not working           correctly.IZ47195 - Probe XC035021 raised when system under extreme stress,           possiblyfollowed by probes ZC005062, XC308062 and          queue manager hang.  IZ50784 - Description is not available (security/integrity           exposure). SE36657 - Mqbegin fails with MSGMCH0601 F/STRINGHIGHUSE4K           probeid XY353001.  SE36964 - MSGAMQ7472 when starting an active WMQ listener object.  SE37006 - AMQZLSA0 job does not run under user-defined subsystem.   IC57153 - WMQ install fails with AMQ4757 files in use whereas           the real issue is shortage of disk space.  IC57176 - Large application unable to connect because of resource           errors.     IC57902 - An exception can occur if a client mqconn/mqconnx fails.  IC57903 - WebSphere MQ JMS messages are not backed to the backout           queue, in case an error occurs during message header           parsing.IC58590 - A non-mqm user with +ctrl authority is unable to stop           the listener.  IC58751 - Queue manager terminates unexpectedly. FFST generated           in checkpoint thread with probe ID AD020002 and rc 203.  IC58897 - Jmsbytesmessage.getbodylength() does not return the           correct value for WebSphere MQ JMS messages.IC59999 - Uncommitted messages show up incorrectly on qstatus           when viewed from MQ explorer.  IC60063 - Potential MQ data integrity issue following an unexpected           machine outage, such as an operating system crash or power           loss.   IZ13144 - Cluster workload is affected due to change in netprty           behaviour.  IZ25889 - Stop channel mode(inactive) can be ineffective with           triggered channels.  IZ26009 - WMQ script reset_iconv_table causes owner and group           of the iconv configuration files to change.  IZ26191 - Probe XC130003 FDC (sigsegv) in function rricompress.  IZ26339 - Only check indoubt on sender channels at delete.  IZ26894   Sender channel or broker MQGet +mqgmo_wait state           corruption.  IZ27491 - Amqoamd is reporting "message not valid" for some objects.  IZ28253 - MQ is not dlpar aware, but is handling sigreconfig.  IZ28473 - Problems sending compressed messages, such as RM503003           or CO007001 FDCs, or using unusual compression/decompression           method.      IZ30207 - Passing invalid arguments to mqi calls inside API           exits leads to sigsegv in agent.  IZ30247 - The words classname and methodname are hard coded          in the waslogger class.  IZ30457 - FFST with probe ID XC076012 and major error code           xecx_e_conv_not_sup from xcsgetmessage.    IZ30565 - WebSphere MQ JMS applications get a nullpointerexception           thrown when calling queuereceiver.close.  IZ30995 - Object_damaged return code not being handled correctly           by rcdmqimg.  IZ31185 - Message is not rolled back when runtime exception           is thrown fromonmessage() when using the WebSphere           MQ V6 resource adapter.  IZ31193 - Exception thrown from WebSphere MQ resource adapter           during initialisation when extended transaction client           not present.  IZ31348 - Jmssession.recover() method does not cause redelivery           of non-persistent messages in a non-transacted session.  IZ31897 - Segv occurs in pcmcheckcommandaut() function when           xcsgetpwnam() returns -1 (no entry found).  IZ32305 - WebSphere MQ JMS queuebrowser performance issue when           using either a jmsmessageid or jmscorrelationid selector.  IZ32933 - Probe ID XY432030 with xecp_e_no_resource under high           concurrent connections and/or large concurrent message           traffic.  IZ33281 - Incorrect security event output. rc 2035 against namelist           and event written was mqca_process_name instead           mqca_namelist_name.    IZ33796 - Queue manager error logs not recreated after deletion.  IZ33798 - Deadlock if multiple threads are accessing WebSphere           MQ base Java methods concurrently and a communications           failure occurs.     IZ34125 - MQ fails to construct and send an availability msg,           when refreshcluster repos (yes) is issued on QM           with more then 1 clusrcvr.  IZ34130 - Workload balancing in a cluster leads to unexpected           results.  IZ35444 - Quiesce shutdown is not properly detecting the abrupt           abnormal end of an application in the middle of an           mqconn request.      IZ35844 - Correct the time delimiter for intervalstarttime and           intervalendtime fields of the channel statistics message.  IZ35884 - 'totalbytes' in channel statistics should only include           the data bytes in the messages, not admin messages           (heartbeat, etc). IZ36482 - Changes to clusrcvr shared using a namelist not published           to allclusters.  IZ36500 - Mqi accounting message with incorrect application name.           field: applicationname.  IZ36978 - Jmsreplyto always contains queue manager name after APAR           IZ15279HAS been applied.  IZ37511 - Generation of an FDC by repository manager process           causes it to terminate.     IZ40824 - Description is not available (security/integrity exposure).   IC54772 - Mqjms publish subscribe applications MQ channel and           tcpip resources are not freed under some circumstances.    IC55154 - Correction in WMQ system admin guide for availability           of runmqtmc command on Windows and UNIX clients.    IC55218 - Customer unable to start a channel. error message           AMQ9587 found in log. may also get FDC with probe           AD004001 on QM termination.   IC55390 - Sequence number on queue stats msg is always 1.    IC55548 - Wmqjms: JMS applications unexpectedly disconnected           from message broker.  IC56006 - Wmqjava: incorrect put time and date is displayed           when looking at messages on a queue.  IC56009 - Comphdr and compmsg channel attributes can't have spaces           around their values when being accessed by runmqsc.  IC56068 - WebSphere MQ queue statistics data field browsefailcount           is incorrectly incremented. IC56133 - Mqrc_api_exit_not_found reason code not found when           compiling WebSphere MQ V6 Java applications.       IC56352 - Mqrc_uow_enlistment_error (2354) when using extended           transactional client.  IC56408 - AMQ9245 message generated without authority event message           being put onto the system.admin.qmgr.event queue.  IC56432 - Misleading statements in WMQ V6 info-center regarding           support for message grouping & segmentation when using           pub/sub.     IC56662 - Hang in AMQZMUC0 process following the 'disk not ready'           error.  IC56709 - Maximum logfilepages displayed in WebSphere MQ explorer           GUI is 16384 instead of the V6 maximum of 65535.   IC57918 - Delay in delivering large messages to message-driven           beans when using WebSphere MQ with WebSphere application           server.   IZ05857 - WebSphere MQ responds with incorrect XA error code in           a global XA transaction.  IZ13144 - Cluster workload is affected due to change in netprty           behaviour.  IZ14005 - Probe XC130003 FDC (sigsegv) in runmqlsr process with           function rppconnectpool on the mqm stack.  IZ15456 - Very slow initial access to deep queues holding large           numbers of grouped messages.  IZ15677 - Jms: application thread hangs when exception thrown           by mqthread.   IZ16645 - Probe RM554010 rrce_file_corrupt. client program mqconn           fails, reason code 2058. clntconn defns missing from           runmqsc output.  IZ17062 - Jvm userid is not passed while creating an xaconnection           if no userid is specified by the JMS application.  IZ17156 - Strmqm incorrectly displays error code during failure.  IZ17158 - Setting errorlogsize does not take effect for queue           managers whose name contain a "." and/or "/" . IZ17303 - Cluster channel ping fails with segmentation violation           and core dump.  IZ17313 - System.cluster.repository.queue damaged, strmqm failed           with an exception in AMQZXMA0 from rfxqueryclqmgr.  IZ17341 - WMQ may start a user-defined service with all signals           blocked, so a stop service that sends e.g. sigterm           would be ineffective.  IZ18103 - Problem during the truncation of a "ghost" queue file           which is marked for reuse.  IZ18142 - Endmqm can take many minutes to end the queue manager           if there are active svrconn channels.  IZ18716 - Errors may not be propagated from early stanzas during           processing of qm.ini and mqs.ini files.  IZ18954 - Delay in sending messages when pipelining is used with           SSL.  IZ19009 - Arce_object_damaged and probe ID AQ143011 after migrating           from MQ 5.3 to MQ 6.0.   IZ19340 - Mqjms: deadlock condition may occur when an application           thread attempts to close session used by asynchronous           messageconsumer.  IZ19555 - Probes XY179010 and XY180010 from AMQZMGR0.  IZ20546 - High cpu usage in the amqrrmfa process on an hourly           basis for several minutes. applications unable to issue           MQ API calls.    IZ20758 - XC034002 AMQZLAA0 unexpected response to a           pthread_cond_timedwait() request causes waiter chain           corruption.    IZ21318 - WebSphere MQ failure to reserve log space in a queue           manager restart scenario.  IZ21977 - MQRC_OBJECT_CHANGED(2041), AMQ9511           SYSTEM.CLUSTER.TRANSMIT.QUEUE,AMQ9448, repository           manager ends.  IZ22019 - Data conversion performance problems after multiple           unsupported or invalid conversions have been requested.    IZ22272 - AMQ9526 and 'scratchpad in use' errors are seen when           two identically named qmgrs are connecting to same           receiving QM.  IZ22725 - Incorrect statement in manual: queue manager configuration           maxchannels attribute.  IZ22727 - Correct reason code when cluster alias sub is not           acknowledged.  IZ23058 - Workload balancing does not round robin the messages           as expected in a clustered environment.  IZ23230 - Mqjava: unable to use WebSphere MQ Java client to           connect to a tpf queue manager with gmo matching options.  IZ23438 - Cluster cache look ups are taking too long causing           clustered object resolution errors.    IZ23780 - Channel status stopped not migrated to V6.  IZ23789 - Queue manager terminated abruptly and an FDC with           probe ID AT004007 is generated.  IZ23839 - Address alignment exception with the log formatter           when formatting an MQGet log record.  IZ23943 - Hang in duow (pipelined) channel process following           forced termination of a channel xppthreadmutex.  IZ24069 - PCF mqcmd_inquire_auth_recs response messages all           have msgseqnumber 1 in the mqcfh.  IZ24186 - Cluster workload exit sample amqswlm does not           load in MQ6.0.    IZ24944 - Wmqjms: JMS pub/sub cleanup thread (pub/sub) fails           to utilize the username/password specified by the           application.  IZ25171 - During channel termination, an FDC with probe           ID RM409000 followed by many with probe ID RM409001           is produced.  IZ25614 - WebSphere MQ channels terminate with AMQ9604 and           AMQ9208 and get FDCs with XC130003 and RM031101.  IZ25622 - Error 2185 putting group msgs to cluster queue           with persistence as queue definition.  IC53540 - Queue manager fails to start up and FDC with probe           ID XY338011 is generated after amqzmgr.exe is terminated.  IC53819 - "mq java/jms application gives a peer name mismatch           error when the exit-list length is greater than 8". IC53960 - Channel shortretry count will not fall after moving           into retry state even though many attempts were made           to restart.  IC54088 - Automatic startup settings for command server are           lost when migrating from MQ V5.3 to MQ V6 in an           MSCS configuration.IC54095 - FDC with probe ID XC368002 and error 'winnt error           5 from duplicatehandle' is generated when a queue           manager is ended.  IC54182 - Access denied error on an openprocess call during           an mqconn by a customer application.  IC54292 - WebSphere MQ queue manager in MSCS cluster ends           unexpectedly.    IC54459 - Channel stays in binding state for a long time           when it contains an invalid conname value.  IC54584 - PCF message write method does not set MQMD fields           to default values for PCF messages.   IC54608 - Channel statistics messages have queue manager           name padded with zeros instead of blanks.  IC54678 - Display conn command in runmqsc failing to find           any matches whenfiltering by conname.  IC54711 - PCF escape command with dis lsstatus for a listener           of 48 chars returns additional chars in listener           name error message.  IC54888 - Queue manager restart fails with HL080077 following           outage when system has been under severe resource           constraints. IC56162 - "dspmqras.exe folder" file is incorrect. should           be dspmqras.exe.  IZ04683 - JMS client connections not closed in asynchronous           mode when queue is manager stopped.   IZ05045 - FDC generated with probeid ZC004063 when using single           threaded agent.  IZ06097 - Mqconnx fails with reason code 2409 when version 1           mqsco is usedwith WMQ 6.0.  IZ06131 - Setmqaut fails when authority records are not yet           created or are missing.   IZ07198 - Queue manager unresponsive, with a probe XY441020           FDC from function xstaddconnectedthreads.  IZ07206 - An application connect during queue manager startup           may cause startup failure with likely FDCs ZF095010           and RM185002.  IZ07297 - Improved error handling during refresh cluster           command when clusnl() attribute points to a namelist           that doesn't exist.  IZ07778 - The runmqsc changes to amqclchl.tab may not be inserted           in the correct ascii-order. also, amqclchl.tab will           never shrink.   IZ07905 - Delays in getting messages when using the WebSphere           MQ JMS client in bindings mode.  IZ08014 - Illegalstateexception calling createconsumer.  IZ08180 - Qmgr not reporting the appropriate warning if           amqrsyna.dat file is corrupted.  IZ08596 - XC034002 in xcswaiteventsem shortly after           zlaperformhealthcheck returns xecp_e_invalid_pid.  IZ08748 - Deleting queues while PCF inquirequeuenames command           is executing, causes an FDC with probe PC024010.  IZ08754 - Failing publish not retried correctly, stream           repeatedly restarts without republishing.  IZ08783 - Probe AD028004 FDC from adiopenfile (RC=24 from open) in           AMQZXMA0, when migrating to V6. this is a file descriptor           leak.  IZ08829 - Pcf: mqcmd_inquire_channel_names fails if more than 628           channels. can cause probe XC006001 FDC or hang command           server.   IZ09338 - In the case of queue manager recycled infrequently,           the number of accumulated channel stats records becomes           very large.  IZ09419 - Improve AMQ9565 error message.  IZ09519 - Improving queue manager's robustness when application           is using non-unique groupid/msgseqnumber/offset/report-type           combinations.  IZ09591 - Endmqlsr fails with 'no WebSphere MQ listeners for queue           manager' if listener launched using runmqlsr.  IZ09658 - AMQZMGR0 does not clean up shared memory in a timely          fashion when it is the last process to reference that          memory.  IZ10060 - Inconsistent treatment of cluster qmgr alias 2087           mqrc_unknown_remote_q_mgr.  IZ10757 - Amqrrmfa terminates with error rrci_clus_no_clusrcvr_defined.  IZ10800 - Rare command server sigsegv in function pcmbuildmsgparms           when executing PCF command mqcmd_inquire_q_status.  IZ10869 - Occasional deadlock when issuing stop conn runmqsc command           (or PCF equivalent).  IZ11153 - WebSphere V6 may not always consider the mqmaxerrorlogsize           environment variable when writing error log messages.  IZ11458 - Dis qs uncom is not a boolean value. IZ12149 - Cleanup code mistakes socket files as directories and           does not delete them appropriately.  IZ12159 - Receiver channel might not decompress message when           message is sent in multiple segments.  IZ12208 - MQOpen fails with 2042, if the MQ application had           previously failed with unexpected error, holding           the object handle open.  IZ12274 - Unable to determine the exit status of internal           processes started as queue manager services.  IZ12283 - Command server returning 2017 ( mqrc_handle_not_available ).  IZ12497 - Probe KN272002 FDC reported from function           kqiputaccountingqueue when a connection has a large number           of open objects.  IZ12536 - Incorrect output can be given by PCF mqcmd_inquire_auth_recs           command. bad output can also be given by dmpmqaut and amqoamd.  IZ12700 - Very large FDC produced including an extremely large dump           area entitled "active shared memory heap".    IZ12795 - Inquirechannel PCF command with channeltype parameter does           not return complete channel details, only the channel           description.  IZ12796 - Jms: a non thread safe JDK class is declared as a static  IZ12827 - FDC written by WebSphere MQ explorer if mqs.ini file has           stanzas that refer to unavailable locations in filesystem.  IZ13135 - The JMS message.setjmsreplyto() method does not work           correctly when using WebSphere MQ resource adapter (ra).  IZ13247 - Imqqueuemanager::connect() fails when mqcsp authentication           is used even when IY92447 is applied.  IZ13512 - WebSphere MQ loops when queue manager ini file is corrupted.  IZ14279 - Queue manager time calculations must use thread-safe system           calls. IZ14399 - Queue managers rejoining clusters with IY99051 have           incorrect sequence numbers, changes may not be published           in the clusters.IZ14812 - Sigsegv in xcsreleasemutexsem called from rrxreporterror           when using mq_channel_suppress_msgs.  IZ14977 - Missing cluster information when namelists are used to           add and remove queue managers from multiple clusters at           once.   IZ18598 - Client mqconn can cause program to end if already           connected or in a variety of error conditions.  IC52223 - Access violation FDC XC130031 in the amqfcxba process.  IC52320 - FDC with probe XY470022 is incorrectly cut if           connectnamedpipe returns zero and the getlasterror           returns error_pipe_connected.  IC52523 - Resolve channel action(commit) fails to resolve a           manually defined clussdr channel.  IC52603 - Amqrmppa thread calls mqback instead of xa_rollback           in an XA environment.  IC52619 - Executing stop connection leads to an access violation           in the execution controller and the queue manager crashes.  IC52632 - Inquire queue status PCF command incomplete response.  IC52674 - Error AMQ7017 occurs when trying to start a queue           manager and anfdc is generated with probe ID ZX000001. IC52684 - Channel compression from z/OS to Windows results in           message data with 4 extra bytes.  IC52709 - Qmgr is reporting the following probes: HL008001           hlgsetlogrestartlsn and AL020000 almsetoldesttranlsn.      IC52954 - SSL channels defined with sslpeername do not start           after migration from MQV5.3.  IC52989 - Clussdr channel can be deleted even though channel           is in-doubt.  IC53065 - WebSphere MQ queue manager fails with probe XC037003           when started.     IC53204 - WebSphere MQ V6: repeated queue damaged instances.   IC53266 - Listener process does not end on queue manager           termination despite using a listener object configured           with control(qmgr).  IC53286 - Unable to compute putdate and puttime when any one of         - the fields is set to blank.   IC53318 - Queue manager fails to start on MSCS with FDC MC033007.  IC53379 - Memory access violation errors seen in mqconn.   IC53403 - Performance slow on mqput/mqgets and AMQZLAA0 cpu usage           is high when running 100'S of application threads/processes.      IC53545 - The recommended method for removing oam entries.  IC53651 - Handle leak when exclude or suppress messages is set.  IC53676 - Error messages AMQ7315 or AMQ7316 are logged when any           accountingor statistics message is put to the           accounting/statistics queue.  IC53716 - Amqoamd command displays inconsistent results for           '+none' authority.  IC53764 - Nullpointerexception error received when tracing level          set to 5 and messageid is null. IC53782 - Amqrrmfa terminates when the queue manager object           configuration contains an invalid value.  IC53817 - Setmqprd silently fails to convert a trial version           of MQ into a production version.  IC53842 - Queue manager terminates unexpectedly with FDC AD031001           and error_invalid_user_buffer from adiwritefile.  IC53936 - FDC with probe ID RM400001 and error code rrce_bad_parameter           generated upon termination of a client channel.  IC53962 - Application successfully opens cluster queue object on           remote queue manager despite specifying an invalid           user ID as altusr.  IC53967 - Poor performance with large messages on Windows clients           using non-blocking tcp model.  IC53974 - MQSeries service fails to start with error 1053. strmqm           hangs. FDC with probe ID ZX005025 generated.  IC54121 - Cluster channel in retrying state would not start after           command: stop channel(<name>) mode(quiesce) status(inactive).  IC54142 - Thread handle leak from MQ com+ (mts) layer.  IY92377 - Destseqfactor incremented for clusrcvr on remote queue           manager causes unexpected results in workload balancing.  IY93129 - MQ is not honoring the value specified for errorlogsize           in the qm.ini file.  IY95538 - 2080 is issued when MCA agent is trying to get messages           from system.cluster.transmit.queue. no messages are           written to the log.  IY96630 - A deleted damaged object prevents advancement of WMQ           logs. it further causes dltmqm to loop consuming log space.   IY96879 - Messages can arrive in incorrect order via cluster channel.  IY97159 - Repository manager process tries to access the cache while           restoring the cache, resulting in a hang.    IY97558 - Agent process does not return from a MQGet call for a           period of time significantly larger than the time-out           specified.IY97580 - FFST probe XC130003 in ccxsend on server side of SSL           channel. IY97736 - Channel fails to start with error AMQ9519           (rrce_channel_not_found). IY98258 - Not setting user name in MQEnvironment gives 2035           error for WMQ v6.0.IY98550 - Customer user exit gives security exception when           Java2 security is enabled.IY98585 - Lower case userid being passed to z/OS v1.6 with           Websphere MQ 6.0. IY98620 - Queue manager hang during define object when an API           exit is installed.  IY98777 - WebSphere MQ hangs after rc=stop from a call to           xlllistenselectacceptandclose.  IY98973 - Memory deallocation failure due to thread mismatch           when pipelining is used.  IY99050 - Rcdmqimg fails with AMQ7084 for a queue containing           segmented messages.  IY99051 - Queue manager unable to re-establish cluster membership.  IY99057 - MQ error handling in XA protocol violations where xa_end()           called for transaction not associated with current thread.  IY99181 - Amqrfdm at WMQ 6.0 does not work when using isolated bindings.  IY99200 - If the execution controller fails to create a new agent           process, it will sigsegv (from WMQ 5.3 CSD13 or 6.0.1.1).  IY99415 - Extra validation for data received from tcp/ip to handle           case where tsh header overwritten during transit.    IY99598 - An extremely intermittent probe ZI032002 FDC from function           ziistophealththread is reported.  IY99683 - Corrupted message header in dead letter messages produced           by JMS Client. IY99912 - MQ adds too many log extents to the log file header at MQ           shutdown resulting in subsequent qmgr restart failure.  IZ00349 - Locking problem where we try to write an accounting record           whilst already holding a lock on a non-queue object.  IZ00380 - Correct parsing of MQ exception handler override commands.  IZ00609 - XC034071 in xcswaiteventsem with error code einval (22).  IZ00896 - WebSphere MQ messages occasionally delivered out of sequence           under stress on MQ V6.0.   IZ01058 - XC130004 sigsegv when restoring cluster objects during           queue manager start up.  IZ01151 - Probe XC015010 raised by checkpoint task during endmqm           processing . IZ01402 - Broker fails to start or publish or subscribe.  IZ01512 - A failure to start a timer thread when waiting for a critical           mutex causes queue manager failure. IZ01580 - A timing window results in two threads using the same           semaphore to suspend/resume leading to hangs and unpredictable           results.  IZ01599 - Sigsegv in kqiwakeupwaiter when waiter state reset during           stop channel command.  IZ01794 - WebSphere MQ queue manager fails to start when transaction's           first lsn is not in active log after disk space issue.  IZ01835 - WebSphere MQ performance is poor when querying xqmsgsa at           a time when system.cluster.transmit.queue is deep.  IZ02442 - Child broker fails to restart after breaking parent           relationship.  IZ02497 - Receive() with unified factories fails to find messages. IZ02512 - Migration to WMQ 6.0 may corrupt clustering information.  IZ02777 - Queue manager fails to start. FDC with probe AT013011.  IZ02915 - XC130004 FFST in apiunlockexclusive, when attempting to           record a media image of a damaged queue.  IZ03090 - Dis qs does not show userid after appltype(system).  IZ03678 - Mqcmit for a long running transaction generating an           mqrc_unexpected_error return code.  IZ04163 - WMQ channel connection fails with AMQ9213 error 22 over IPV6.  IZ04394 - Queue file corrupted crossing 4MB boundary and no space avail.  IZ04523 - Amqiclen does not clear trace control shared memory.  IZ04767 - Tcf_last with no tcf_first should be detected by WebSphere MQ.  IZ04971 - Missing attributes in the queue manager log stanza causes           queue manager restart to fail.  IZ05005 - AT004018 possible when simultaneous activity from separate           threads attempt to complete an XA transaction concurrently.  IZ05013 - Using data compression on a channel, channel ends with FDC           with probe ID CO052100 generated on receiving side qmgr.  IZ05057 - Qdphiev event messages sent to system.admin.perfm.event           queue incorrectly.   IZ05307 - Dspmqtrn formats XA xids incorrectly.  IZ05527 - When browsing a queue with mqgmo_browse_next the first           message ever put to the queue can be skipped.  IZ05653 - AMQZMUR0 fails with XC006001 and xecs_i_private_memory_error.  IZ05792 - MQRC_NO_CONTEXT_AVAILABLE returned from attempted MQPUT           to dead letter queue after queue backout threshold reached. IZ05950 - Generating non-unique groupid's when using message           segmentation,can cause a queue manager to crash.  IZ06614 - No authority event generated after mqrc_not_authorized           returned to mqconn, despite enabling authority events.  IZ06672 - WMQ queue manager error log locking can be briefly           compromised, but with typically no impact.  IZ07210 - Abstract 2035 if client user name > 12 chars and valid           mcauser.  IZ07794 - Defbind not honoured when alias queue resolves to a           cluster queue.  IZ09339 - Averagequeuetime (mqiamo_avg_q_time) displays negative           values. IZ09383 - Occasional fdc's with probe KN072085 when applications           specify mqgmo_msg_under_cursor with mqgmo_wait.  IZ10294 - Incorrect authorization check when putting directly           to an MQ transmit queue.  IC50588 - FDC AQ109001 from aqhlogicalmsglock during browse,          lock of a segmented message.   IC51005 - Mqrc_security_error returned on a PCF inquire           authority records command submitted with invalid           parameters.  IC51054 - "mqrc_storage_not_available error due to the invalid data           length returned from the MQGet of the message.  IC51315 - WebSphere MQ rolls back prepared transactions if msdtc           goes down. IC51322 - Code changes for optimization of default conversion. IC51324 - WMQ invokes enlistwithdtc to enlist with the transaction           leading to a number of calls in msdtcprx.dll causing a           deadlock.  IC51350 - Warning AMQ8075 logged when a user with an ID of more           than 12 characters issues the change channel command.      IC51451 - Access violation occurs when printing out the object           descriptor and associated object records in trace of           MQOpen.  IC51472 - XC090001 and xecf_e_invalid_parameter.  IC51497 - Get complete msg fails with mqrc_match_options_error. IC51589 - Runmqdlq suffers XC130031 access violation when it           encounters a null message on the dead letter queue.  IC51598 - Damaged object following log errors caused by a           sharing violation on the log itself.   IC51721 - Unable to rebuild a syncfile using rcrmqobj if           using circular logging.   IC51904 - An FDC with probeid XC130031 is generated in           amqrmppa process. IC51952 - Mqrc_truncated_msg_failed error from MQGET call           even though enough buffer is supplied.  IC52019 - Optimize code where MQ reads the sync file to           get the saved channel status. IC52177 - Channel process reports incomplete error messages           if it encounters a TCP error during connect, send           and receive. IC52193 - AMQ9519 when starting auto-defined clussdr channel. IC52257 - Access violation FDC XC130031 in the command server           (amqpcsea.exe).  IC52322 - Queuemanager service does not start a program with           extension .cmd or .bat if the stdout parameter is           not set.   IY87626 - Resolve channel on an auto cluster sender channel           ( in indoubt state ) fails with xecl_e_invalid_param.  IY89755 - Very small timing window whereby pipelined channels           ("dual unit of work", duow) can fail with probe           CO000002 FDCs. IY90873 - FFST with probeid KN111000 continually generated           reports mqrc_stopped_by_cluster_exit.  IY91269 - FFST with probe XC006001 when using channel exits.  IY91348 - Reset non-existent channel in runmqsc results in           memory fault and SIGSEGV.  IY91510 - MQJMS2002 jmsexception thrown when using multiple           consumers with selectors on a transacted session.  IY92011 - Runmqsc "dis q(*)" doesn't display all queues if           one or more of the queues are damaged.  IY92016 - PCF inquirequeuenames command does not handle damaged           objects gracefully.  IY92051 - Amqoamd command generates an erroneous attribute for           setmqaut. IY92141 - Load exit fails with error 'cannot open shared object           file: no such file or directory'. IY92194 - Dis chs fails on clusrcvr channels when using conname           limiter. IY92196 - Xstdisconnectextent causes FFST for applications           using fork without exec. IY92390 - The malformed or unexpected message handling fails           with 2098 error in asynchronous message delivery           scenario.  IY92441 - Bothresh ignored in JMS applications when using           alias queues.  IY92447 - Userid and password not passed across channel.  IY92929 - Logger process amqhasmx (AMQZMUC0 in V6) could           eventually run out of file descriptors some time           after a disk full condition. IY92963 - SIGSEGV in preparedumpareas during crtmqm and resulting           core file. IY93155 - Channel triggering fails due to object_already_exists           error. IY93324 - MQJMS2003 gets generated with a nullpointerexception.  IY93408 - Mqbegin fails with SIGSEGV or SIGBUS when an Oracle           session is killed. FDC file contains probe ZM008001          and XC130003.  IY93506 - SIGBUS from dmpmqlog commands. IY93655 - Performance problems related to resolving high '          lock contention.  IY94013 - Poor performance loading deep queues containing           both persistent and non-persistent messages.  IY94250 - Setting a zero interval via the mq_channel_suppress_interval           environment variable causes SIGFPE FDCs in channel processes.   IY94451 - Queue manager alias definitions with alteration date more than         - 1 month old not successfully deleted from a cluster. IY94625 - Amqfcxba suffering a SIGSEGV in function.           fkirestoresubscription or in function fkxderegistersubscriber. IY94674 - Client applications continuously cycling thread connections           may re-read mqs.ini many times.  IY94700 - Hang in channel processes such as runmqlsr, amqrmppa,           runmqchl.  IY94811 - Nullpointer exception occurs if WebSphere application           server trace is disabled.  IY94832 - Duplicate subscriptions with different subname's cause           SIGSEGV in amqfcxba process.  IY94876 - UNIX file descriptors being left open while generating           FDC for asynchronous signals.  IY94977 - Queue manager fails to start throwing log not available           error following an abrupt failure.   IY95078 - Long delays in multi-threaded puts in WMQ c++ client. IY95181 - JMS null valued causes exception in MQ JMS application. IY95255 - Probe: XC130004, SIGSEGV: address not mapped, function:           aqhaddmsg. problem writing temporary dynamic queue object.  IY95370 - Synchronization issue with the jmsconnection hangs           shutdown of application server. IY95485 - Queue manager is ignoring requests for more than 253           secondary log files on UNIX.  IY95508 - Channel statistics getting collected at the end of the           configured statint after having turned off the statchl           attribute. IY95513 - Probe XC130004 FDC (SIGBUS or SIGSEGV) in xcsendgrent           function.  IY95544 - SSL enabled channel will not run because MQ code is           not able to access the channel status table.  IY95555 - WebSphere MQ authority event message incorrectly shows           mqm as the user ID. IY95566 - Runmqsc ctrl/ctrlx auth not honoured for non-mqm users. IY95706 - Sigsegv immediately following return from zfudoesobjectexist           XC130004 from amqzlaa0, amqrmppa, or amqfcxba.  IY96055 - Messages due to expire do not expire after a queue manager           crash/restart or an HA failover.  IY96066 - MQ JMS publish/subscribe clean up does not process all           applicable messages.  IY96150 - AMQ9509 and RC=2009 errors during endmqm -i, causing           channels to fail abnormally.  IY96282 - Two threads have been concurrently allocated the same           semaphore. IY96442 - Message expiry report not resolved to cluster queue.  IY96924 - JMS applications hang when multiple threads try to           connect to a queue manager which is not running. IY96959 - Exitbuffer parameters not passed to mqxr_sec_parms. IY97755 - SIGSEGV in function rfxaddclqmgr during queue manager           startup. IZ01272 - Potential security exposure in MQ client channels. IC49616 - FDCs with AT040010 and AT003001 while reusing the           agent connection.  IC49717 - MQ external (native) exits called by the Java client           incorrectly.  IC49767 - Sigsegv in amqrrmfa when processing rrmreallocmsgs,           causing the amqrrmfa (repository manager) to terminate.   IC49857 - MQ rc = 2354 mqrc_uow_enlistment_error when using           msdtc in MSCS environment.  IC49914 - IP address not shown properly in the error logs when          'localhost' is used in conname of the channel definition.    IC50327 - FDC with probe KN101001 from kqicloseit during mqdisc.   IC50448 - Unable to deserialize object (JMS1061).  IC50453 - AMQSTRG0 comments say it is using MQTMC2 but the sample           says memcpy(&trig.version, " 1", 4): AMQSTRG0.C.            IY84659 - Unusual sequence of requests on a thread currently           associated with another transaction causes SIGSEGV.  IY84998 - Agent looping inside zlahealththread producing           repeated probe XC330005.  IY85622 - Sigsegv FDC with xpprundestructors on function stack.   IY85679 - Unending series of xecl_w_long_lock_wait FDCs from           function xllosspinlockwaitlock, e.g. probe XY086003.  IY86287 - Sigsegv in atxassociationcheckidle called (indirectly)           from atxassociationremoveall.  IY86322 - Failure in "strmqm -r" during log replay . IY86343 - Connectionname passed to exit or conname displayed           in runmqsc is 0.0.0.0.  IY86361 - WebSphere MQ V6.0 accounting messages display           incorrect info.  IY86365 - XC130003 SIGSEGV in WebSphere MQ conversion routine           xcsconvertstring.  IY86541 - WebSphere MQ message returned even though correlid           does not match.  IY86600 - Accounting messages are not generated after exceeding           account count interval.    IY86827 - Queue manager is not able to write to queue manager           log files.  IY86828 - Delivery problem with two listeners on same-name MQ          destinations.  IY87162 - Problems with stop channel mode(force|terminate) calls.  IY87173 - Memory leak within WebSphere MQ cluster repository           process amqrrmfa.  IY87192 - Mqrc_connection_broken and recursive imq_impl_disc_backout.  IY87310 - FFST by xcssimplepipecleanup with probe ID XY490002. IY87523 - Corrections to ensure proper mapping between euro-enabled           CCSIDs and respective codesets.  IY87638 - Queue handle leak when using producer.send(destination,           message).   IY87797 - MQ runmqsc creates FDC with probe ID XC267011 showing           SIGPIPE.  IY87802 - Output of the amqoamd utility may have spurious trailing           characters for any 48-character queue names.  IY87804 - WMQ acting as an XA resource manager calls ax_unreg in           some exceptional cases disallowed by the XA spec.  IY87834 - A base Java application works fine on MQ 5.3, but when           run on MQ6.0 the application returns mqrc_iih_error.  IY88140 - MQ JMS map/stream/text messages publish with blank           rfh.format.  IY88151 - Problem supplying the userid information via the           mqenvironment when using client channel tables.  IY88246 - A WMQ semaphore set with a semid of 0 may be created           with wrong ownership/permissions, which can hang WMQ           processes.  IY88283 - Channels would not start after upgrading to WMQ V6.  IY88509 - Channel with SSL enabled never goes to retry even when           remote end is not reachable.  IY88514 - Connections left open when an XA create session fails.  IY88551 - Queue manager can fail to start without producing FFST           failure report.  IY88873 - Memory leak in queue session when creating message           consumers.  IY88948 - WMQ channel fails to start with AMQ9202 on Windows.  IY88954 - Poolscavenger is never started and so connections are           not closed in a running JVM.  IY89259 - Nullpointerexception in getconnectionccsid() or spiget().  IY89374 - JMS clients should not assume the default persistence           (defpsist)on the system.broker.control.queue is yes.  IY89484 - ZL000128 zlamain during endmqm after probe XC037008           xcsexecprogram from AMQZMGR0 AMQ6026.  IY89548 - Java / JMS client native user supplied send/receive           exits core dump on close channel, and also fail when           resizing buffer.  IY89674 - Mqrc_dbcs_error returned to client when clustering used.  IY89729 - Passing a blank as a selector causes the listener to           fail reporting invalid parameter.  IY90046 - Messageconsumer.close() may block indefinitely if there           are many messages on the queue that do not meet selection           criteria.  IY90227 - Client channel definition file created from WMQ 5.3 gives           error when read from a WMQ V6.0 Java client when CRL is           configured. IY90244 - Heap corruption can cause MQ exception handler to hang.  IY90460 - Amqrmppa process will not release threads causing high           resource utilization.  IY90548 - Not being able to modify the 5000MS timeout period used           while retrieving messages (internal chunktime value).  IY90566 - Cluster workload algorithm excludes local instances of           cluster queues when putting via alias queues.  IY90707 - Get(disabled) on an alias queue does not wake up           "waiting" gets.  IY90712 - Sigsegv in function rfxaddclqmgr during queue manager           startup when migrating to WebSphere MQ V6.0.  IY90995 - An FDC reporting a SIGSEGV occurs if the queue manager           attempts to obtain the group entry for a group ID that           is undefined.  IY91959 - If the clusrcvr channel is stopped, when it is re-started           the repository cache is not properly updated causing           workload issues.IY93095 - Performance hit when user generated msgIDs are used           rather than MQ generated msgIDs.  IY94369 - A SIGSEGV can occur in function xtrestablishtracestatus           when an application makes MQ C API calls using JNI     IC48241 - Messages received using messagelistener with durable           subscribers are getting backed out once the application           ends.     IC48478 - MQJMS3023 in pub sub application after quiescing and           restarting the queue manager.    IC48555 - JMS pub/sub cleanup utility fails with 2009 in SSL           environment.  IC48576 - Program exceptions in Visual BASIC (vb) applications           using the administration API.  IC48662 - Convert chained header to UCS-2 returns wrong reason code  IC48678 - Listener status inquire fails if the listener name           length is 48.  IC48680 - Stopping the first instance of a receiver channel           which is connected to multiple sender channel throws           AMQ9533 error.  IC48696 - Java .lang . nullpointerexception is received when the           path specified for explorer Java trace is incorrect.  IC48705 - WebSphere MQ creates FDC with probe ZF165008 from           wasreceivedata.  IC48711 - Registry key wrong for explorer excludemessages.  IC48721 - WebSphere MQ explorer message browser tool does not           display some Japanese character sets.  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.  IC48795 - Message browser included in WebSphere MQ explorer (V6)           limits browsing to first 500 messages on queue.  IC48803 - AMQ9207 invalid data received on a channel following a           timeout on the Windows platform. FDC with probe           ID CO052000 is created.  IC48880 - Custom services fail to migrate during migration to           MQ 6.0.  IC48908 - Channel name changed by exit is not picked up when           using the MQ explorer.  IC48913 - Performance problem getting message from a large queue.  IC48914 - Conversion from CCSID 819 to 912 fails on get/convert.  IC48919 - Locking errors when attempting to delete an in-doubt           channel.  IC48920 - Repeated resrcmon.exe FDC's following MSCS related errors.  IC49003 - Multi threaded C++ application hangs.  IC49005 - Mqtcpsdrport environment variable not working with           WebSphere MQ version 6.0 .   IC49093 - WMQ Java client change in the response expected from           a negotiation call which occurred around fap 4.  IC49167 - Data conversion error causes segmented messages to be           dead letter queued (or return mqrc_format_error from mqget).  IC49197 - Performance problem on machines where MQ fails to calculate           a required accuracy from the performance counters.  IC49409 - Clusrcvr disappearing at queue manager startup time.  IC49431 - Z or z in the mqmd.useridentifier field is incorrectly           transcoded to j, causing authentication failures.  IC49533 - Mqrc_not_authorized received on mqconnx for a           user ID passed in a mqcsp structure.  IC49569 - The extended transactional client receives FDCs with           probe ID ZSL33001 and subsequently with probe          ID ZS129001.  IY80410 - MQJMS2013 error when connecting to WebSphere MQ in           bindings mode.  IY80806 - MQ looping during startup when invalid attribute           logbufferpager is located in the log stanza of the           qm.ini file.  IY80952 - Memory leaks in clustered channels, and (V6) PCF           filtering.  IY81353 - AMQ8135 mqrc_not_authorized errors when manually           starting or stopping auto-defined clussdr channels.  IY81358 - Changes to MCAuseridentifier made by security exits           not reflected in channel definitions.   IY81628 - MQJMS2005 reason code 2102 when 2035           mqrc_not_authorized occurred.  IY81661 - Channel created using auto-definition exit has           incorrect fields.  IY81671 - XC308090 when xa_start and xa_rollback or xa_commit           are issued concurrently for same xid.  IY81714 - MQMD userid put in upper case by V6 rcvr channel.  IY81774 - WebSphere MQ as JMS provider not adhering to JMS           specifications as per section "4.3.8 exceptionlistener".  IY81875 - Trace improvements for 'stop channels' functionality           during queue manager ending.  IY81906 - Migration to WMQ V6 sets new clwluseq queue attribute           incorrectly.  IY81941 - Very frequent channel starting and ending may cause           excessive CPU usage in amqrmppa (channel pooling)           processes . IY81945 - Hang in function kqiwakeupwaiter e.g. during quiesce           endmqm . IY82078 - Sigsegv in aqpcopydatabuffers during MQPut to a dynamic           queue.  IY82241 - If a correlid has been set as text, retrieving it as           bytes returns null.  IY82297 - Rcdmqimg records image of damaged object leading to           subsequent rcrmqobj failure.  IY82419 - Probe id's XC332070 and XC034071 from xlswaitevent.  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.  IY82889 - When using cross domain connection factory definitions           in was V6 the TCPIP connection is not released during           the cleanup.  IY83093 - Workload balancing temporarily unbalanced after a lot           balancing.  IY83272 - Amqsstop does not work on big endian machines.  IY83321 - Error messages logged by an application not in mqm group,           may cause the system error log file to exceed the specified           maximum . IY83372 - Xcsfreequickcell reports xecs_e_block_already_free in error.  IY83535 - MQ V6 can attempt to create more than logprimary + logsecondary           log extents.  IY83588 - Extremely long running channel exits cause channels to end           due to hbint not taking the exit time into account.   IY83704 - Java.lang.unsatisfiedlinkerror trying to load           LIBMQJEXITSTUB01.SO for MQ client only installations.  IY83775 - C++ client disconnect causes mqrc_hconn_error in           non-C++ applications.  IY83778 - Messages do not get rolled back in point to point           domain when exceptions occurs in MDB.  IY84127 - When QM runs out of resource and error logic is being           exercised,mq calls xcsfreequickcellblock() instead of           xcsfreequickcell().  IY84356 - Possible loss of queue manager data area if strmqm detects           a problem with files or directories during startup.  IY84410 - FDC with probe AT002001 is generated when           atm.rmidgenerator reaches 2147483647.  IY84479 - Code change for function "strptr" at line 541 of           AMQSAXE0.C.  IY84777 - A probe ZX033006 FDC with errorcode xecs_e_seg_in_use may           be dumped from function zxccleanupwlmserver during endmqm.  IY84934 - FDC showing SIGSEGV in function rrxconvertchannelfromdiskver           or zxcrestoreobject when migrating from WMQ V5.2 to V6.0.  IY85203 - WebSphere MQ script reset_iconv_table may cause blank           file name or incorrect permissions on conversion tables.  IY85541 - AMQ9426 queue manager unable to rejoin cluster.  IY85542 - Reset cluster does not remove deleted repository entry.   IY86606 - Cluster subscriptions made for non-cluster queues.  PTF IP22988-----------This is the First Fix Pack CSD01 for IBM WebSphere MQ for HP OpenVMS Alpha Version 6.0. It is delivered via PTF IP22988 for APAR IC58895.Number of APARS in PTF = 20It contains fixes for all the problems listed below :IC58895 - Cumulative maintenance #01 (Fix Pack CSD01) for WebSphere MQ for HP          OpenVMS Alpha V6.0IC58548 - Cleanup does not happen properly during endmqm,later causes the           dltmqm command to fail.IC58381 - Crtmqm failed and fdc generated. if customer changes lang from 	    ja_jp to c, then crtmqm succeeds.IC58380 - Early tracing caused crtmqm fail.IC58525 - Unable to format wmq trace because dspmqtrc hangs.IC58635 - High cpu usage is noticed while amqzmgr0 process is monitoring its           child processes: command server, channel initiator, etcIC58637 - Monmq show process is throwing vms error code system-f-accvio while 	    fetching the mq processes list.IC59103 - Queue manager crashes under heavy load with probe xc307060.IC59180 - Error log filling up with diagnostic info written by amqrmppa process.IY83535 - MQ V6 can attempt to create more than LogPrimary + LogSecondary log extents.IC57863 - Inconsistency in the log control state between logger and agent processes 	    results in agent loop.IC57862 - During mqputs there was an issue with synchronizing memory access between 	    multiple mq processes.IC58914 - Lseek error in vms error log on webphere mq v5.3 fp13 on hp openvms.IC59029 - FDC not required when an OpenVMS user account which does not have SYSGBL and 	    PRMGBL privileges tries to run an application.This has to be notified to the 	    user that he is not privileged to use the application and the return code 	    should be 2035.IC59947 - During rollover of error log files,issuing error code 65535.Probe XC404023          component XEEROLLOVERLOGFILES.	IC60196 - The failover monitor fails with access violation.	   6011.1  - Endmqcsv - failure on 4th attempt if started and stopped repeatedly.6011.2  - samples EXE's  - fails with an access violation.     6011.20 - Cobol library files which are used for building MQ applications are not present in           the MQS_INCLUDE directory.6011.21 - During installation of MQ v6 on OpenVMS Alpha display an error saying MQMXA.EXE 	    image is not an OpenVMS Alpha image.DOCUMENTATION CHANGES---------------------There are no documentation changes at this time.++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++TRADEMARKS----------The following terms are trademarks of the IBM Corporation in theUnited States or other countries or both:   IBM   WebsphereMQDIGITAL, OpenVMS, HP and Alpha are trademarks of the HPCorporation.++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++