IBM Support

II14245: KEY APARS FOR WEBSPHERE MQ FOR Z/OS V6 (5655L8200) AND WEBSPHERE APPLICATION SERVER FOR Z/OS V5.1X, V6X (5655I3500)

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: 12/02/2011 - Beverly Brown
    .
    See II14556 for WebSphere MQ for z/OS V7.0.1.
    See II14484 for WebSphere MQ for z/OS V7.0.0.
    See II13776 for WebSphere MQ for z/OS V5.3.1.
    .
    This informational apar is intended to summarize WebSphere MQ
    for z/OS V6 APARs (5655L8200) that are required for MQ with JMS
    applications to work in a WebSphere Application Server for z/OS
    V51x V6x (compid 5655I3500) environment.  Many of the MQ apars
    also apply to any application using the RRS adapter in MQ.  Also
    listed are WebSphere Application Server for z/OS V51x and V6x
    key APARs related to JMS and MDB applications.
    .
    As these APARs cor-close, they will be added to the WebSphere
    Application Server for z/OS V51x, and V6x PSPs as well. Some
    apars listed here are not yet cor-closed and may or may not have
    early fixes available.
    .
    The MQ apars are applicable to WebSphere MQ for z/OS V6.0.0. We
    would strongly recommend that all WebSphere MQ for z/OS APARs
    marked HIPER also be 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
    V51x and V6x 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.
    V510 service levels are designated by W510xxx where xxx will
    be an increasing number.
    .
    The announcment letter at
    http://www-306.ibm.com/fcgi-bin/common/ssi/ssialias?infotype=an&
    subtype=ca&supplier=897&appname=IBMLinkRedirect&letternum=ENUS20
    5-092#@2h@87@
    lists WebSphere Application Server V4.0.1 for z/OS as the
    minumum level to work with MQ V6.0, but this APAR only contains
    information for the WAS releases supported as of December 2006.
    .
    If a pause on MQGET on a regular interval is observed, please
    refer to this technote for a MQ setting for eoqtimeout:
    http://www.ibm.com/support/docview.wss?uid=swg21228320
    .
    See the Installation Information in the PSP bucket for Upgrade
    MQMESA, Subset HMS6000 at
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=isg1_MQMESA_
    HMS6000#INSTINFO
    The bucket contains important information about configuring WAS
    to use the V6 level of SCSQAUTH.  The interface between the
    batch adapter and the queue manager changed in V6 such that it
    is not possible to use a V5.3.x version of the batch adapter
    with a  V6 queue manager. The V6 batch adapter is downwardly
    compatible. A symptom of using the wrong adapter is
    MQJE001: Completion Code 2, Reason 2018.
    ===========================================================
    = 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   =
    = JMS6008.                                                =
    = Please note that with these fixes, it is only necessary =
    = to apply the APAR corresponding to the latest JMS CSD   =
    = as it will supersede any previous CSDs.                 =
    ===========================================================
    Required MQ Java/JMS Fixpacks in a WebSphere Application Server
    for z/OS environment:
    PM40148 (UK68117) - Fixpack 6.0.2.11 - latest available level
    PM17286 (UK60169) - Fixpack 6.0.2.10
    PM00650 (UK55685) - Fixpack 6.0.2.9
    PK87027 (UK51116) - Fixpack 6.0.2.8
    PK87026 (UK47742) - Fixpack 6.0.2.7
      6.0.2.7 includes a fix for various errors described in
      PK82295 when WebSphere Application server V7 connects to
      WebSphere MQ for z/OS V6 in bindings mode.
    PK82929 (UK45134) - Fixpack 6.0.2.6
    PK67851 (UK41016) - Fixpack 6.0.2.5
      PE'd: See PK77733 (UK44690)
    PK58458 (UK37403) - Fixpack 6.0.2.4
    PK47040 (UK33802) - Fixpack 6.0.2.3
    PK40628 (UK30346) - Fixpack 6.0.2.2
    PK31289 (UK23493) - Fixpack 6.0.2.1
      Adds support for MQ JMS bindings mode connections in 64 bit
      WAS on z/OS. ( 64-bit 64bit )
    PK31288 (UK22808) - Fixpack 6.0.2.0
    PK22728 (UK17743) - Fixpack 6.0.1.1
    .
    See the Local Fix section of PK23658 for circumvention
    instructions if you experience the problems described in the
    APAR and have not yet applied Fixpack 6.0.2.1.
    .
    ===========================================================
    = WebSphere MQ for z/OS APARs:                            =
    = Contact MQ support if there are early fixes available   =
    ===========================================================
    Required HIPER (high impact or pervasive) or Special
    Attention fixes for the described environment:
    PK91444  ABEND 0C4 IN CSQMCTXE AND CSQ3RRSM AND ALSO ABEND 5C6
             RS 00E50076
    PK90539  DUMP TITLE=CSQ1,ABN=0C4-00000011,U=SYSOPR  ,C=L8200.60
             0.SSSC- CSQ3RRSR,M=RRSRFRR ,LOC=CSQ3REPL.CSQ3RRSR+0FFC
    PK80499  ABEND 0C4 IN CSQMCTXE AND CSQ3RRSM+2352 AND ALSO ABEND
             5C6 RS 00E50076
    PK34370  RECEIVED JMSSECURITYEXCEPTION: MQJMS2008 INTERMITTENTLY
             WHEN INVALID USERID IS PASSED TO MQ.
    PK47728  CORRECT THE HANDLING OF XA_CLOSE PROCESSING IN MQ
    PK33713  MESSAGES HIDDEN FROM JMS OR CICS LISTENER AFTER THE
             LISTENER PROCESS BROWSES THE MESSAGE USING
             MQMO_MATCH_MSKENOKEN
    PK26176  AFTER APPLICATION OF UK14585, MQ WORK ON A BINDINGS
             MODE JMS CONN FROM WAS IS DONE OUTSIDE WAS
             TRANSACTION CONTROL
    PK17549  ABEND0C4 IN CSQVIALC AFTER CANCELLING A RRS BATCH JOB,
             THEN QUEUE MANAGER ABEND WITH CSQV086E
    PK17137  INCORRECT CURDEPTH (MESSAGE COUNT NOT DECREMENTED
             CORRECTLY) WHEN USING THE WMQ V6 JMS LISTENER OR
             MQMO_MATCH_MSG_TOKEN
             **See the Local Fix section of the APAR for a**
             **circumvention using the QATVersion property**
    PK15592  ABEND6C6 AFTER RRS IS RECYCLED WITH A LARGE NUMBER OF
             URS OUTSTANDING. MQ ISSUES CSQ3014I FOR EACH INDOUBT UR
             THEN ABENDS
    PK09898  LOOP IN ACE CHAIN WHICH RESULTS IN A QMGR HANG
    ===========================================================
    Other recommended MQ fixes for the described environment:
    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)
    PK69739  WHEN TWO MDB LISTENERS ARE CONNECTED TO THE SAME
             SHARED QUEUE, SOME MESSAGES ARE NOT PROCESSED BY
             EITHER LISTENER AND REMAIN STUCK ON THE QUEUE.
    PK64409  ZWAS CAN'T RECONNECT TO QMGR AFTER A WMQ FAILURE
             (RC=2059 AND J2CA0056I RECEIVED WHEN CREATING
             QUEUECONNECTION). Will need fixpack 6.0.2.5 PK67851.
    PK61806  DUMP TITLE=MQ01,ABN=0C4-00000004,U=SYSOPR  ,C=L8200.60
             0.ASMC- CSQVDISC,M=CSQVDISC,LOC=CSQVGEPL.CSQVDISC+
    
    
    PK60905  CURDEPTH IS NON-ZERO BUT NO MESSAGES ARE RETURNED ON
             GET BY WAS JMS MDB LISTENER
    PK58601  WHEN AN RRS UOW INVOLVING A WAS THREAD GOES INDOUBT,
             THE NID IS INCORRECT AND CAN NOT BE RESOLVED WITH
             INDOUBT"
    PK55326  A WMQ MSG IS NOT SENT TO DLQ AFTER ROLLBACK WHEN THE
             SYSTEM EXCEPTION WAS ISSUED AT THE TIME OF ACCESS TO
             WAS.
    PK52886  Leading up to an IPL, RRS, and MQ were stopping while
             WAS was still up. An ABEND0C4 occurred.
    PK35580  SEVERAL ABENDS 5C6 REASON 00F30052 AFTER RRS WAS
             RECYCLED.  Suppress excessive dumps.
    PK33083  ICH408I AND MQJMS2013 WITH REASON 2035 AFTER MIGRATING
             FROM MQ V5.3.1 TO MQ V6.0
    PK32148  AN MDB WILL FAIL TO RETRIEVE THE FIRST MESSAGE > 4K
             FROM THE QUEUE. SUBSEQUENT > 4K MESSAGES ARE RETRIEVED
             SUCCESSFULLY.
    PK35463  STOPPING OF WAS USING RRSBATCH CONNECTION CAUSED S0C4
             ABEND AT CSQVGEPL.CSQVEUS2+09D2 FOLLOWED BY THREE S0D6
             ABENDS IN CSQ3AMGP
    PK30929  WEBSPHERE APPLICATION SERVER SERVANT ABEND0C4 PIC11 IN
             *PATHNAM/JAVA_COM_IBM_MQ_SERVER_MQSESSION__1MQCONN
    PK26017  ABN=0C4-00000011 U=SYSOPR ,C=L8200.000.IFC -CSQWVZSA,
             M=CSQWVZSA,LOC=CSQWVZPS.CSQWVZPS+09C0
    PK20340  ABEND ABN=0C4-00000004 IN CSQVDISC+0398 WHEN SHUTTING
             DOWN MQ
    PK17549  ABEND0C4 IN CSQVIALC AFTER CANCELLING A RRS BATCH
             JOB, THEN QUEUE MANAGER ABENDS WITH CSQV086E
    PK12917  STORAGE LEAK IN SP229 KEY7 OF MQ SKB STORAGE FOR WEB
             CONTEXTS IN THE WEBSPHERE APPLICATION SERVER JOB
    PK11374  ABEND0C4 IN CSQ3RRSM OCCURRED WHEN DRIVEN BY RRS FOR
             BACKOUT, AND IT CAUSES UNCOMMITTED MESSAGES ON QUEUE
    PK11372  ABEND0C4-11 AT OFFSET X'F36' IN MODULE CSQ3RRSM.
    PK09899  JMS CLIENT MQCONN FAILS WITH RC 2059 AFTER THE QUEUE
             MANAGER IS RECYCLED
    PK08389  SYSTEM ABEND S6C6 - REASON CODE F30905 AT SHUTDOWN OF
             A WEBSPHERE APPLICATION SERVER (WAS)
    ===========================================================
    = WebSphere Application Server z/OS APARs:                =
    = Contact WebSphere support if there are early fixes      =
    ===========================================================
    PK54610  AFTER A MESSAGE IS BACKED-OUT TO AN MQ QUEUE FOR AN
             EXCEPTION AND TRANSACTION ROLL-BACK IN MDB, THE
             MESSAGE ISN'T RE-DELIVERED.
             The fix is included in Service Level (Fix Pack)
             6.0.2.25 (PK58870) of WebSphere Application Server
             V6.0.1 for z/OS.
    PK17823  MQ V6 INTEROPERABILITY ISSUES WITH MDBs running on
             WEBSPHERE for z/OS. EC3 ABEND WITH RC 04130004 DUE TO
             MDB TIMEOUTs and POTENTIAL MDB PERFORMANCE IMPACTs.
             APAR corrects WebSphere MDBs Listening-in-Servant to
             Listen-in-Controller. Fixed in W510230. Equivalent
             APAR is PK18537 for V601, fixed in 6.0.2.9.
    PK13471  ENHANCE ERROR DETECTION IN WEBSPHERE FOR Z/OS
             CONTROLLER WHEN EXCEPTION IS THROWN ON JMS CONNECTION
             USED BY MDB LISTENER PORT.
             Fixed in service level W510230
             Inorder to exploit the Listener Port recovery feature
             provided by this apar to the fullest extent you will
             also need to have the below minimum WebSphere
             MQ service levels
             MQ531  > CSD13
             MQ6    > 6.0.1.1
    PQ90325  Throttle for the XA recovery work
             Fixed in service level W510004.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II14245

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-12-18

  • Closed date

  • Last modified date

    2011-12-02

  • 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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 December 2011