IBM Support

PI83240: FREQUENT QUEUE SERVICE INTERVAL HIGH EVENTS BEING GENERATED AFTER MAINTENANCE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Queue service interval high events are getting generated more
    frequently after maintenance was applied.
    
    If multiple getters are checking for service interval high
    events at the same time, it is possible for the sequence of
    processing on two threads to result in a negative service
    interval being calculated. Because a negative interval is not
    expected, it is interpreted as a very large interval which
    exceeds the service interval threshold defined on the queue, so
    a service interval high event is issued.
    .
    Additional keywords:
    QSVCINT QSVCIEV HIGH
    SYSTEM.ADMIN.PERFM.EVENT
    MQRC_Q_SERVICE_INTERVAL_HIGH
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Frequent queue service interval high    *
    *                      events may be produced when multiple    *
    *                      applications are serving messages on    *
    *                      the same queue.                         *
    ****************************************************************
    With performance events enabled, and an appropriate high service
    interval set on the queue. When multiple applications are
    servicing messages on the queue, if multiple gets occur within a
    short period of time, CSQMIAGM may wait for the object latch for
    the queue. However this may result in the calculation for
    elapsed time to return a negative value into an unsigned value.
    This results in the service interval high performance events
    being produced more frequently than expected.
    

Problem conclusion

  • The processing has been altered to correctly calculate the time
    used prior to issuing the events to correctly deal with multiple
    getters waiting on the same object latch.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI83240

  • Reported component name

    MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-19

  • Closed date

    2017-07-05

  • Last modified date

    2018-01-16

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

    PI81927

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

    UI48529 PH03169

Modules/Macros

  • CSQMIAGM
    

Fix information

  • Fixed component name

    MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI48529

       UP17/08/10 P F708

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 January 2018