IBM Support

IT29638: The DISPLAY CHSTATUS command output for an AMQP client instance always shows AMQPKA(0) instead of the actual value

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 displaying the channel status of connected AMQP client
    instances using a command like:
    
    DISPLAY CHS(*) CHLTYPE(AMQP) CLIENTID(<clientid>) ALL
    
    the value of AMQPKA for each client channel instance
    (representing the time interval between keep alive frames sent
    from the queue manager's AMQP service to the connected client)
    always displays as 0, whatever the value of this property was
    set to initially, or negotiated to when the AMQP client
    connected.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users inquiring the time interval between
    keep alive frames sent from an IBM MQ AMQP channel to the
    connected AMQP client in the channel status output for that
    client.
    
    
    Platforms affected:
    Windows, Solaris x86-64, Solaris SPARC, Linux on x86-64, AIX,
    Linux on Power, Linux on S390, HP-UX Itanium
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When displaying the status of IBM MQ AMQP channel instances, the
    value of the AMQPKA attribute was always shown as being 0. This
    was wrong. The AMQPKA attribute should have had a value
    representing the AMQP channel instance's AMQPKA interval, as
    negotiated on the channel.
    

Problem conclusion

  • The channel status for a AMQP channel instance now displays a
    value for AMQPKA representing the interval between keep alive
    frames sent from the AMQP channel to a connected AMQP client.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.16
    v9.0 LTS   9.0.0.12
    v9.1 LTS   9.1.0.8
    v9.2 LTS   9.2.0.2
    v9.x CD    9.2.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

    IT29638

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-05

  • Closed date

    2020-12-17

  • Last modified date

    2020-12-17

  • 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

    5724H7251

Applicable component levels

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

Document Information

Modified date:
12 January 2021