IBM Support

PI36469: WMQ DISPLAY CHSTATUS RETURNS SUBSTANTIALLY LARGE NETTIME VALUES WHEN ISSUED ON DISTRIBUTED SENDER CHANNELS THAT CONNECT TO Z/OS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DISPLAY CHSTATUS was issued on queue managers (x86 Linux and
    Windows) for SENDER and CLUSSDR channels connecting to a z/OS
    QMGR instance. This returned substantially high values for
    NETTIME for idle channels (where only HEARTBEAT flows were being
    passed) but also on channels where active messaging was being
    done. Level 3 analysis finds rriReceiveData should be resetting
    rfpTCF2_CMIT_INTERVAL on the rfpTST_HEARTBEAT reply.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a sender channel on a distributed  *
    *                      queue manager is connected to a         *
    *                      receiver channel on a z/OS queue        *
    *                      manager, the NETTIME for the channel    *
    *                      shows an unexpectedly high value when   *
    *                      heartbeating is enabled.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a receiver channel on the z/OS queue manager receives a
    heartbeat, which has the rfpTCF2_CMIT_INTERVAL flag set. In this
    case, a commit interval is now supplied for the heartbeat reply
    back to the distributed queue manager, while leaving the flag
    set. This results in the first 4 bytes of the returned LUWID
    being used as the commit interval, which results in an
    unexpectedly high calculated NETTIME value.
    

Problem conclusion

  • The flag has been cleared on the heartbeat reply. This results
    in the commit interval not being used, and the NETTIME not
    being miscalculated.
    100Y
    CSQXRMTR
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI36469

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-06

  • Closed date

    2015-04-24

  • Last modified date

    2015-07-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PI36564 PI38518 UI27027

Modules/Macros

  • CSQXRMTR
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI27027

       UP15/06/03 P F506

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 July 2015