IBM Support

IC74752: INSTALLING WMQ V7.0.1.4 MAINTENANCE CAUSES HA CLUSTER FAILOVER TO FAIL. AN FDC WITH PROBE ID ZT374003 IS GENERATED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After installing WebSphere MQ v7.0.1.4 maintenance (fix pack),
    failing over the queue manager resource in a HA cluster
    environment fails. The queue manager fails to come online
    (start) on the passive node. Instead, a FFST (FDC) with probe
    id ZT374003 for component zutRequestQMFileLocks is generated
    for the MQ execution controller (amqzxma0.exe). The major
    error code reported is lpiRC_Q_MGR_LOCK_UNAVAILABLE with
    comments "Active LockFile and current MQM SID mismatch". The
    FFST function stack is as follows:
    
    MQM Function Stack
    ExecCtrlrMain
    zutRequestQMFileLocks
    xcsFFST
    

Local fix

  • Modify the 'active' lock file with the correct SID for the local
    'mqm' group.  The active file is located in the queue managers
    data folder.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Customers using Microsoft Cluster Server (MSCS) with WebSphere
    MQ V7.0.1.4
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    During the queue manager creation, WebSphere MQ stores the
    host name, lock id and the SID of the group 'mqm' in a file
    which resides in the location <drive>:\WebSphere MQ\qmgrs
    \<QMNAME>\active. Under MSCS control this file is  updated
    with the information pertaining to the current node where the
    queue manager is active. The FDC with probe id ZT374003 is
    created if the SID of the mqm group is not same as the SID
    stored in the active lock file. The content of the active file
    is not cleared before the data with the information of the
    active node is written to it.  The length of the data written
    by both the nodes are different, this results in some trailing
    characters in the active file. The comparison fails since the
    length of the SID read from the active file is incorrect.
    

Problem conclusion

  • WebSphere MQ is modified so that the data read from the active
    file is correctly interpreted.
    
    | MDVREGR 7.0.1-WS-MQ-Windows-FP0004        |
    | MDVREGR 7.0.1-WS-MQ-Windows-FP0005        |
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.6
    --------           --------------------
    Windows            U200328
    
    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

    IC74752

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-02

  • Closed date

    2011-03-24

  • Last modified date

    2011-08-09

  • 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 WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R701 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 March 2023