II14484: KEY APARS FOR WEBSPHERE MQ FOR Z/OS V7.0.0 AND WEBSPHERE APPLICATION SERVER FOR Z/OS V6.X AND V7

APAR status

• INTRAN

Error description

• Last updated: 12/14/2009 - Beverly Brown
  .
  See II14245 for WebSphere MQ for z/OS V6.0.0.
  See II14556 for WebSphere MQ for z/OS V7.0.1.
  .
  This document is intended to summarize WebSphere MQ for z/OS V7
  APARs (component id 5655R3600) that are required for MQ JMS
  applications to work in a WebSphere Application Server (WAS) for
  z/OS V6.x or V7 (component id 5655I3500) environment.  Many of
  the MQ fixes apply to any application using the RRS adapter in
  MQ.  Also listed are key WebSphere Application Server for z/OS
  APARs related to JMS and MDB applications.
  .
  It is strongly recommended that all WebSphere MQ for z/OS APARs
  marked HIPER are installed even if they are not listed here.
  To see a list of available WebSphere MQ for z/OS APARs, refer to
  web site:
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006625
  Click on the link under "View service details" for the
  appropriate release.
  .
  For a list of available WebSphere Application Server for z/OS
  V6.x and V7 APARs, PTFs and their corresponding service level
  identifiers, refer to web site:
  http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21175164
  Click on the link to the APAR/PTF table for your WAS release.
  *
  ***IMPORTANT***
  Set PROVIDERVERSION to "6" on the connection factory or in the
  JVM system properties.  See details at:
  - JMS applications using MQ V7 JMS fail when connected to MQ for
  z/OS V7.0.0:
    http://www-01.ibm.com/support/docview.wss?uid=swg21376626
  - Information about using WebSphere MQ as the JMS Provider for
  WebSphere Application Server Version 6.1:
    http://www-01.ibm.com/support/docview.wss?uid=swg21307203
  - Information about using the WebSphere MQ messaging provider
  for WebSphere Application Server Version 7.0
    http://www-01.ibm.com/support/docview.wss?uid=swg21316899
  ***************
  ==========================================================
  = WebSphere MQ for z/OS apars - JMS                       =
  = WebSphere MQ for z/OS ships JMS fixes grouped into      =
  = Fixpacks (previously known as CSDs), which are cross    =
  = referenced below with the APAR numbers that ship them.  =
  = A Fixpack is a corrective service delivery vehicle      =
  = which is cumulative and includes fixes for multiple     =
  = problems.  It corresponds with the same Fixpack number  =
  = on MQ distributed products.  These fixes are for FMID   =
  = JMS7008 ( PTF release R008 ).                           =
  = It is only necessary to apply the PTF for the latest    =
  = JMS Fix Pack as it will supersede previous ones.        =
  ===========================================================
  Required MQ Java/JMS Fixpacks in a WebSphere Application
  Server for z/OS environment:
  PK81737 (UK51276+UK51300) Fixpack 7.0.0.3 - latest available
                                              level
  PK81712 (UK46209)  Fixpack 7.0.0.2
  PK79725 (UK44095)  Fixpack 7.0.0.1
  .
  ===========================================================
  = WebSphere MQ for z/OS APARs:                            =
  ===========================================================
  Required HIPER (high impact or pervasive) or Special
  Attention fixes for the described environment:
  PK97360  DUMP TITLE=CSQ1,ABN=0C4-00000011,U=SYSOPR  ,C=R3600.70
           0.SSSC- CSQ3RRSR,M=RRSRFRR ,LOC=CSQ3REPL.CSQ3RRSR+0F9
  PK80499  ABEND 0C4 IN CSQMCTXE AND CSQ3RRSM+2352 AND ALSO ABEND
           5C6 RS 00E50076
  PK78524  VSM IGVVSERR OUT_OF_SQA ABEND878 RC4 RC8
           SQA exhausted due to leak of pause elements (SSD).
  ===========================================================
  Other recommended MQ fixes for the described environment:
  PK96025  ABEND0C4 IN CSQMEOTC+X'470'
  PK85702  MQ V7 SERVER NOT CORRECTLY HANDLING THE SEQUENCE
           OF NEGOTIATIONS CORRECTLY, CAUSING CSQX547E MESSAGE.
      Workaround: ALTER the SVRCONN channel definition SHARECNV
      parameter. Change SHARECNV(10) default to SHARECNV(0).
  PK84436  CURDEPTH IS NON-ZERO FOR AN XMITQ, BUT THE
           MESSAGES CAN NOT BE GOTTEN DESTRUCTIVELY OR WITH A
           BROWSE
      The cursor can be reset using the MQ command
        /cpf RECOVER QMGR(QDEPTH <qname>)
      where cpf is the command prefix for the queue manager and
            <qname> is the name of the queue(s) to be processed,
      with a '*' wildcard allowed at the end.
      The command needs to be issued from the console.
  PK82295  VARIOUS ERRORS WHEN CONNECTING FROM WEBSPHERE
           APPLICATION SERVER V7 TO WEBSPHERE MQ FOR Z/OS V6 IN
           BINDINGS MODE
      Fixed in WebSphere MQ for z/OS Fixpack 6.0.2.7 (PK87026)
  PK81330  WHEN A WEBSPHERE MQ V7.0 CLIENT IS ACCESSING A Z/OS
           QMGR, THE MCD FOLDER IS MISSING FROM THE RFH2
  PK80807  RACF MESSAGE ICH408I IS PRODUCED IF THE USERID IS LESS
           THAN EIGHT CHARACTERS.
  PK78820  WHEN PROCESSING A MESSAGE CONTAINING AN RFH2 HEADER
           WITH SUPPORTED AND UNSUPPORTED FOLDERS, 2 RFH2'S ARE
           PRODUCED.
           Fixed by PK70759
  PK69598  DUMP TITLE=MQOY,ABN=0C4-00000004,U=SYSOPR  ,
           C=R3600.700.ASMC-CSQVDISC,M=CSQVDISC,
           LOC=CSQVGEPL.CSQVDISC+03BA
  ===========================================================
  = WebSphere Application Server z/OS APARs:                =
  = Contact WebSphere support if there are early fixes      =
  ===========================================================
  PK65675  CLASSNOTFOUNDEXCEPTION SEEN ON WEBSPHERE APPLICATION
           SERVER V6.1 FOR Z/OS WHEN USING WEBSPHERE MQ V7 AS A
           MESSAGING PROVIDER
           This causes MDB listeners to fail to start without any
           clear external indication that there has been a
           problem.
  PK77430  It is not possible to pass some custom properties,
           such as PVER, through to the WebSphere MQ V7.0 JMS
           client.  Properties include PROVIDERVERSION,
           ASYNCEXCEPTION, SENDCHECKCOUNT, TEMPTOPICPREFIX,
           and WILDCARDFORMAT.
           Targeted for inclusion in WAS fixpack 6.1.0.27 and
           7.0.0.5.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

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

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

Fix information

Applicable component levels