IBM Support

IT42368: KN941001 FDC records every 5 seconds after suspending a queue manager from a uniform cluster

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

  • Repeated FDC records are generated after suspending a queue
    manager from a uniform cluster.
    
    This problem only happens if there are applications connected to
    that queue manager, that have connected without the
    MQCNO_RECONNECT option.
    
    These are some details from the FDC:
    
    Probe Id  :- KN941001
    Component :- kqiEjectApplicationInstance
    
    MQM Function Stack
    zmuThreadMain
    zmuIQMCommsManagerTask
    kpiIQMCommsManager
    kqiEjectAllApplications
    kqiEnumerateApplGrps
    kqiEjectAllInstancesForApplication
    kqiEnumerateApplGrpConns
    kqiEjectApplicationInstance
    xcsFFST
    
    These lines of trace history may appear, or similar:
    ------{ kqiStopConnInternal
    Data: 0x635d2924 0x229c8a01
    Data: 0x00003ea4 0x00000014 0x00005e78 0x0000000d
    ------} kqiStopConnInternal rc=lpiRC_CONN_NOT_STOPPED
    -----} kqiMoveApplGrpConn rc=lpiRC_CONN_NOT_STOPPED
    -----{ xcsFFST
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users with a uniform cluster, in which they issue the SUSPEND
    QMGR CLUSTER(clusname) command.
    
    Also, this queue manager has client applications connected
    without using the MQCNO_RECONNECT option.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The problem is in the IBM MQ code on the queue manager that runs
    to move a connected client application from one queue manager in
    the uniform cluster to another.  This code was failing to move
    the non-reconnectable client.
    
    However, it is reasonable that this client cannot be moved, so
    some changes were required in the MQ code on the queue manager
    side, so that this condition is handled gracefully.
    

Problem conclusion

  • The IBM MQ queue manager logic has been corrected, so that this
    condition is handled gracefully.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.10
    v9.x CD    9.3.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

    IT42368

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-10-29

  • Closed date

    2022-11-25

  • Last modified date

    2022-11-25

  • 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

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
26 November 2022