IBM Support

IT34118: Miscalculation of expiry time for SYSTEM.CLUSTER.HISTORY.QUEUE messages.

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

  • The expiry time of messages put to the queue
    SYSTEM.CLUSTER.HISTORY.QUEUE is incorrectly set to 15 days
    rather than 150 days.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of the SYSTEM.CLUSTER.HISTORY.QUEUE may be affected by
    this problem.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The SYSTEM.CLUSTER.HISTORY.QUEUE (SCHQ) was introduced in IBM MQ
    version 7.0.1
    (https://www.ibm.com/support/pages/new-queue-introduced-refresh-
    pack-websphere-mq-701-called-systemclusterhistoryqueue).  The
    default expiry for messages put to this queue is documented at
    150 days, which consists of:
    
    [Cluster object lifetime (90 days)] + [2 * Cluster 'grace'
    period (2*30 days)]
    
    Expiry time is expressed in tenths of a second but a coding
    error meant that the expiry time for messages on this queue were
    set as if they were seconds.
    
    Dumping a message from the SCHQ shows that the expiry is out by
    a factor of 10:
    
    (dmpmqmsg output)
    
    A EXP 12959201 = 14.999 days
    

Problem conclusion

  • The code was corrected so that the expiry for messages on the
    SCHQ matches the documented 150 days.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.9
    v9.2 LTS   9.2.0.3
    v9.x CD    9.2.3
    
    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

    IT34118

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-04

  • Closed date

    2021-04-29

  • Last modified date

    2021-04-29

  • 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 BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

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

Document Information

Modified date:
30 April 2021