IBM Support

PI46158: WMQ: CLUSTER CHANNEL AUTO-DEFINITION EXIT ABENDS 0C4 REASON 10 15/08/21 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CSQX111E xxx CSQXDISP User channel exit error, TCB=008BBA6
    reason=0C4000-00000010
     Change team found the 0C4 occurs after the fix for PI27234
    when a cluster-sender is started due to a copy of the channel
    being taken from the cluster cache which may have ClusterPtr
    set to a residual value.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: After application of the PTFs for APAR  *
    *                      PI27234 (UI23827), starting an          *
    *                      auto-defined cluster channel after only *
    *                      the channel initiator has been          *
    *                      restarted, can result in an 0C4 abend   *
    *                      when a Channel Auto-Definition (CHAD)   *
    *                      Exit is used.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    APAR PI27234 corrected a storage leak when a CHAD exit is
    defined (CHADEXIT queue manager attribute set). However a logic
    issue exists in the case where the channel definition is read
    from the cluster cache after the channel initiator has been
    restarted (without the queue manager being restarted), the value
    for the list of clusters for the channel is not recalculated,
    allowing the CHAD exit and the relevant processing to
    dereference an invalid pointer address, resulting in an 0C4
    abend.
    

Problem conclusion

  • The processing when only the channel initiator is restarted has
    been altered to clear the ClusterPtr, which will result in the
    ClusterPtr being recalculated the next time the auto-defined
    cluster channel is started.
    000Y
    CSQURFXC
    CSQXREXT
    CSQXRFXC
    CSQXRMAS
    CSQXRMSS
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI46158

  • Reported component name

    WMQ Z/OS 8

  • Reported component ID

    5655W9700

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-03

  • Closed date

    2015-08-26

  • Last modified date

    2015-11-03

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

    PI37337

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

    UI30535

Modules/Macros

  • CSQURFXC CSQXREXT CSQXRFXC CSQXRMAS CSQXRMSS
    

Fix information

  • Fixed component name

    WMQ Z/OS 8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY UI30535

       UP15/10/07 P F510 Ø

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.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
03 November 2015