PI53058: CUMULATIVE MAINTENANCE FIXPACK 8.0.0.5 FOR THE JMS FEATURE OF IBM MQ FOR Z/OS VERSION 8.0.0.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Fixpack 8.0.0.5 for IBM MQ for z/OS Version 8.0.0
  provides fixes for the problems described in this APAR.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
  *                 Release 0 Modification 0 with the MQ Java    *
  *                 Feature.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Service offering 8.0.0.5 for WebSphere  *
  *                      MQ for z/OS V8.0.0 provides fixes for   *
  *                      the problems described in this APAR.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  PI52839 - Package error with V8.0 jms/java code
  IT09266 - A classcastexception is issued when connection is
            broken between a classes for Java client and a queue
            manager.
  IT10205 - JMSCMQ0002: the method 'mqctl' failed JMSCMQ0001
            ('mqcc_failed')reason
            '2534' ('mqrc_operation_not_allowed')
  IT10708 - Ibm MQ rc 2142 (mqrc_header_error) putting an
            mqmessage more than once
  IT10775 - Java.lang.outofmemory exception using JMS
            messagelistener due tohigh number of dispatchthreads
  IT10777 - WebSphere MQ JMS trace displays incorrect numerical
            date format
  IT10837 - WebSphere MQ channel start fails with AMQ9637 when
            using a tls 1.2 cipher running in an Oracle JRE
  IT11161 - WebSphere MQ V7.5 PCF response messages do not have an
            expiry set and can be orphaned on the reply queue.
  IT11278 - WebSphere MQ ams always generate trace points in mft,
            classes for Java and classes for JMS trace output
  IT11291 - Ibm MQ 8.0 JMSWMQ2001: failed to close destination
            'my_queue', using a read ahead close policy.
  IT11318 - WMQ V8: if a password is not provided when using
            connauth, MQ base Java applications can still connect
            to a queue manager
  IT11393 - Activation spec endpoint pauses before the sequential
            message failure limit has been reached
  IT11517 - WebSphere MQ V7.5: MQ resource adapter incorrectly
            uses automatic client reconnection in Java ee
            application server
  IT11544 - V7 JMS client applications connecting to WMQ V8 queue
            manager flow incorrect password data.
  IT11843 - Mqgetmessageoption.segementstatus set to blank on
            messages over 4KB in length.
  IT12097 - Modify the pcfmessageagent to disable the strict
            checking of pcfresponses by default
  IT12709 - MQ 8 classes for Java application gets exception with
            reason code 3013 when getting activity trace message
  IT12884 - After upgrade to MQ 8.0.0.4 a
            java.lang.nullpointerexception occurs when using the
            mqsimpleconnectionmanager
  IT13141 - Java application throws filenotfoundexception when
            running under the security manager
  IT13265 - Nullpointerexception thrown within MQ classes for
            java/jms when trace is enabled without write access to
            filesystem
  IT13767 - WebSphere MQ classes for Java and classes for JMS FDC
            with probeid MP005001 does not contain queue manager
            name
  IV74821 - When upgrading MQ client from 6.0.2 to 7.1 message
            data in is unreadable and only "?" are displayed.
  IV75442 - JMS client connected to EBCDIC queue-manager fails to
            open the backout queue and the message is put to the
            dlq
  IV76399 - Setting a bigdecimal into a message causes
            "invalid xml" writteninto the message without
            incurring a Java exception
  

Problem conclusion

• Java level info:
  
  Name:        WebSphere MQ classes for Java
  Version:     8.0.0.5
  Level:       V800-PI53058-L160520
  Build Type:  Production
  
  
  JMS level info:
  
  Name:        Java Message Service Client
  Version:     8.0.0.5
  Level:       V800-PI53058-L160520
  Build Type:  Production
  
  Name:        WebSphere MQ classes for Java Message Service
  Version:     8.0.0.5
  Level:       V800-PI53058-L160520
  Build Type:  Production Built on IBM Corporation
                          pmz6470sr5-20130619_01 (SR5) z/OS
  
  Name:        IBM WebSphere MQ JMS Provider
  Version:     8.0.0.5
  Level:       V800-PI53058-L160520 mqjbnd=V800-PI53058-L160520
  Build Type:  Production
  
  Name:        Common Services for Java Platform, Standard Edition
  Version:     8.0.0.5
  Level:       V800-PI53058-L160520
  Build Type:  Production
  008Y
  CSQ8JTR1
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI38168

Modules/Macros

• CSQ8JTR1
  

Fix information

• Fixed component name

  WMQ Z/OS 8

• Fixed component ID

  5655W9700

Applicable component levels

• R008 PSY UI38168

     UP16/05/27 P F605 ¢

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.