IBM Support

IT15208: MQ V8: FDC WITH PROBE ID ZX092012 GENERATED WHEN ENDING QUEUE MANAGER WITH -P FLAG

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When performing a pre-emptive shutdown of the queue manager
    (endmqm -p), a failure data capture (FDC) file may be generated
    by the amqzmur0 process with probe ID ZX092012.
    This behaviour may be observed on queue managers running on the
    MQ Appliance or on distributed platforms.
    The contents of the FDC file are similar to the following:
    +---------------------------------------------------------------
    --------------+
    |
                  |
    | WebSphere MQ First Failure Symptom Report
                  |
    | =========================================
                  |
    |
                  |
    | Date/Time         :- Wed April 27 2016 02:06:15 BST
                  |
    | UTC Time          :- 1461719175.094935
                  |
    | UTC Time Offset   :- 60 (GMT)
                  |
    | Operating System  :- IBM MQ Appliance ()
                  |
    | PIDS              :- 5725-S14
                  |
    | Product Long Name :- IBM MQ Appliance
                  |
    | Vendor            :- IBM
                  |
    | Data Path         :- /var/mqm
                  |
    | Installation Path :- /opt/mqm
                  |
    | Installation Name :- MQAppliance      (1)
                  |
    | Probe Id          :- ZX092012
                  |
    | Application Name  :- MQM
                  |
    | Component         :- zmuStatisticsCollector
                  |
    | SCCS Info         :- /build/slot1/p800_P/src/lib/zu/amqzmus0.c
    ,             |
    | Line Number       :- 495
                  |
    | Effective UserID  :- 100 (mqm)
                  |
    | Real UserID       :- 101 (mqsystem)
                  |
    | Program Name      :- amqzmur0
                  |
    | Arguments         :- -m QM2
                  |
    | Addressing mode   :- 64-bit
                  |
    | LANG              :-
                  |
    | Process           :- 54219
                  |
    | Process(Thread)   :- 54232
                  |
    | Thread            :- 8    Statistics
                  |
    | QueueManager      :- QM2
                  |
    | UserApp           :- FALSE
                  |
    | ConnId(1) IPCC    :- 18
                  |
    | ConnId(2) QM      :- 34
                  |
    | Last HQC          :- 4.0.0-53504
                  |
    | Last HSHMEMB      :- 0.0.0-0
                  |
    | Last ObjectName   :-
                  |
    | Major Errorcode   :- zrcX_STATISTICS_UNAVAILABLE
                  |
    | Minor Errorcode   :- OK
                  |
    | Probe Type        :- MSGAMQ5043
                  |
    | Probe Severity    :- 2
                  |
    | Probe Description :- AMQ5043: Statistics recording is unavaila
    ble due to    |
    |   error code 2009.
                  |
    | FDCSequenceNumber :- 0
                  |
    | Arith1            :- 2009 (0x7d9)
                  |
    |
                  |
    +---------------------------------------------------------------
    --------------+
    

Local fix

  • These FDCs will only be observed when starting and stopping the
    queue manager in quick succession, and can be ignored.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This is a very low impact problem and only affects customers
    that start and stop queue managers in very quick succession.
    
    
    
    
    Platforms affected:
    AIX, HP-UX Itanium, HP-UX PA-RISC, IBM iSeries, Linux on Power,
    Linux on S390, Linux on x86, Linux on x86-64, Linux on zSeries,
    Solaris SPARC, Solaris x86-64, Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The FDC indicates that one of MQ's internal tasks received
    MQRC_Q_MGR_STOPPING during initialisation, but there was no
    provision in the internal logic of the task to handle this
    reason code at this point. The task ended as a result of this
    issue but it had no impact because the queue manager was ending
    anyway.
    

Problem conclusion

  • The affected internal tasks within the MQ queue manager have
    been updated to correctly handle the MQRC_Q_MGR_STOPPING reason
    code.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.5
    v9.0 LTS   9.0.0.1
    
    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

    IT15208

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-10

  • Closed date

    2016-05-19

  • Last modified date

    2017-02-22

  • 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

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7251

Applicable component levels

  • R800 PSY

       UP

[{"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.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
22 February 2017