IBM Support

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

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • Last updated: 05/28/2013 - Beverly Brown
    .
    See II14484 for WebSphere MQ for z/OS V7.0.0.
    See II14245 for WebSphere MQ for z/OS V6.0.0.
    .
    This document is intended to summarize WebSphere MQ for z/OS
    V7.0.1 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.
    *
    *
    - 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      =
    = Fix Packs (previously known as CSDs), which are cross   =
    = referenced below with the APAR numbers that ship them.  =
    = A Fix Pack is a corrective service delivery vehicle     =
    = which is cumulative and includes fixes for multiple     =
    = problems.  It corresponds with the same Fix Pack number =
    = on MQ distributed products.  These fixes are for FMID   =
    = JMS7018 ( PTF release R018 ).                           =
    = 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:
    .
    PM72574 (UK93962)          Fixpack 7.0.1.10 - lastest level
    PM69576 (UK80595)          Fixpack 7.0.1.9
    PM59172 (UK76621)          Fixpack 7.0.1.8
    PM42759 (UK74191)          Fixpack 7.0.1.7
    PM32344 (UK70159)          Fixpack 7.0.1.6
    PM24788 (UK66975)          Fixpack 7.0.1.5 - minimum recommended
    PM19089 (UK64044)          Fixpack 7.0.1.4
    PM09662 (UK59811)          Fixpack 7.0.1.3
    PM03853 (UK56957+UK56956)  Fixpack 7.0.1.2
    PM03843 (UK53422)          Fixpack 7.0.1.1
    .
    ===========================================================
    = WebSphere MQ for z/OS APARs:                            =
    ===========================================================
    Required HIPER (high impact or pervasive) or Special
    Attention fixes for the described environment:
    .
    PM58239  WMQ: A GETWAIT LASTS FOR THE WHOLE DEFINED WAITINTERVAL
             ALTHOUGH THE MESSAGE IS ALREADY ON THE QUEUE
    PM54691  WMQ 7.0.1 QUEUE MANAGER ENDED ABNORMALLY WITH S30D
             ABEND
    PM01922  STORAGE LEAK, SUBPOOL 0 KEY 8, IN WSAS SERVANT REGION
    PM12231  WMQ 7.0.1: CEE3204S PROTECTION EXCEPTION IN
             CSQBCSPIGETM WHEN WSAS IS CONNECTING TO A QUEUE-SHARING
             GROUP USING BINDING MODE
    PK97360  DUMP TITLE=CSQ1,ABN=0C4-00000011,U=SYSOPR  ,C=R3600.70
             0.SSSC- CSQ3RRSR,M=RRSRFRR ,LOC=CSQ3REPL.CSQ3RRSR+0F9
    .
    ===========================================================
    Other recommended MQ fixes for the described environment:
    .
    PM81522 DELAY IN RESETTING THE BROWSE-MARKS AND CAN CAUSE A
            DELAY IN GETTING THE MESSAGE.
    PM74575 WMQ Z/OS: ABEND0C4 IN CSQMCTXE+00000770
    PM70109 WEBSPHERE MQ V7, ABEND 0C4-00000011 IN CSQXSGET, PROBLEM
            WILL ONLY OCCUR WHEN A WAS ADDRESS SPACE IS ENDING
    PM60235 DURING WSAS ASYNC MESSAGE CONSUME THE WRONG BLOA IS
            USED BY THE CONSUMER
    PM56881 WMQ Z/OS: AN MDB LISTENER IS NOT RECOVERED AFTER A
            QUEUE MANAGER FAILURE WHEN USING ASYNC CONSUME AND
            A 64 BIT JVM
    PM57579 WMQ Z/OS: HANG DURING MEMTERM OF AN ALLIED ADDRESS
            SPACE USING RRS
    PM51907 HANG IN ASYNC CONSUME PROCESSING WHEN AN MDB IS
            LISTENING ON A NON-DURABLE SUBSCRIPTION AND IS
            CONNECTING TO THE QSG NAME
    PM37311 WMQ Z/OS: ABEND5C6-00E20028 IN CSQSTACK+00000146
    PM37311 WMQ Z/OS: ABEND5C6-00E20028 IN CSQSTACK+00000146
    PM37158 WMQ Z/OS 7.0.1: ABEND0C4 OCCURS IN CSQIMGE9 + X'60CA'.
            THE APPLICATION MAY RECEIVE MQRC 2195 MQRC_UNEXPECTE
    PM37003 AFTER MIGRATION TO WEBSPHERE MQ V701 AN MDB NO LONGER
            RETRIEVES MESSAGES FOR A SPECIFIED SELECTOR.
    PM36582 WMQ V7 JMSCC0108 MESSAGE WEBSPHERE CLASSES FOR JMS IS
            RECEIVED WHEN USING MDBS CONNECTING TO SHARED QUEUES.
    PM28478 WMQ: ABEND0C4-00000004 IS REPORTED IN CSQWVCOL.
    PM25396 ABEND 052 REASON 00000512 ABEND052 CSQYALLI, CSQYEATE
            DURING QMGR SHUTDOWN.
    PM21113 WMQ DIFFERENT HANDLING OF CCSIDS IN WMQ V6 AND WMQ V7
            ON Z/OS MQMD CCSID DIFFERENCES RFH2
    PM15119 AFTER MIGRATING TO V701, THE SMF116 TYPE 1 ENTRIES FOR
            GETN FOR JMS PROGRAMS ARE 0
    PM14268 CSQ1,ABN=30D-00000000,U=XXXXXXXX,C=R3600.701.ASMC-CSQVSR
            ,M=CSQVSRRX,PSW=070C00008111D186,ASID=00FE
    IC64098 APPLICATION DOES NOT AUTOMATICALLY RECONNECT TO THE
            QUEUE MANAGER IF CONNECTION IS LOST WHEN USING THE MQ
            RESOURCE ADAPTER.
            The problem is with a connection to a V6 queue manager.
            Fixed in Fix Pack 7.0.1.1 for distributed platforms
    PM01003  ARRAYINDEXOUTOFBOUNDSEXCEPTION RECEIVED WHEN USING AN
             ACTIVATION SPECIFICATION IN WEBSPHERE APPLICATION
             SERVER V7
    PM01980  DOC UPDATE - USING JAVA MANUAL NEEDS CORRECTION FOR
             JVM SUPPORT (64-bit)
    PM01660  ABEND0C4 IN CSQMEOTC+X'470'
    .
    ===========================================================
    = 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 number

    II14556

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-03-11

  • Closed date

  • Last modified date

    2013-05-28

  • 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

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
28 May 2013