IBM Support

IT18858: xecS_E_MEM_SET_NOT_FOUND FDC ON IBM MQ APPLIANCE QUEUE MANAGER

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

  • Closed as program error.

Error description

  • When starting a queue manager, a failure data capture (FDC)
    record such as this is
    created by the amqzmuc0 process:
    
    | Probe Id          :- ZD040010
                                                  |
    | Program Name      :- amqzmuc0
                                                  |
    | Thread            :- 23    DurSubsMgr
                                          |
    | Major Errorcode   :- xecS_E_MEM_SET_NOT_FOUND
                                  |
    | Minor Errorcode   :- OK
                                                        |
    | Probe Type        :- INCORROUT
                                                 |
    | Probe Severity    :- 2
                                                         |
    | Probe Description :- AMQ6125: An internal IBM MQ Appliance
    error has        |
    |   occurred.
    
    +---------------------------------------------------------------
    --------------+
    
    MQM Function Stack
    zmuThreadMain
    zmuDurableSubscriptionManagerTask
    kpiDurableSubscriptionManagerTask
    kqiReconcileDurableSubscribers
    kqiTopicRegisterSubscriber
    zruNotify
    xcsFFST
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This may affect users who have defined a subscription to the
    $SYS/MQ/INFO/QMGR/queue_manager_name/Monitor class of
    meta-topics
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    At queue manager startup a shared memory resource is created by
    one thread and accessed by another.   The shared memory resource
    may not have been created when the accessing thread tried to use
    it and so an FDC record was created.
    

Problem conclusion

  • The code has been modified so that the thread which is trying to
    access the shared memory resource will ignore the fact that the
    resource does not exist rather than report an error.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.7
    v9.0 CD    9.0.3
    v9.0 LTS   9.0.0.2
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT18858

  • Reported component name

    IBM MQ APPL M20

  • Reported component ID

    5725Z0900

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-17

  • Closed date

    2017-02-28

  • Last modified date

    2017-02-28

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

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

Fix information

  • Fixed component name

    IBM MQ APPL M20

  • Fixed component ID

    5725Z0900

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"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:
28 February 2017