IBM Support

PH08561: IBM MQ Z/OS V9:IMPROVEMENT FOR SELECTORS ON QUEUES IN SMF

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Selectors on queues are not reflected well in the SMF
    statistics and accounting data.
    
    *SELCOUNT and SELMAXLN:
    Looking at the statistics collection logic, these fields were
    implemented as part of the MQSUB API call. As such, they
    currently only record when a subscriber application uses a
    selector to open a topic.
    Selectors on queues don't appear to have been considered in
    this case,  but it would make sense to record these values when
    a connection specifies a selector on an MQOPEN of a queue.
    
    *GETA and GETS (and the equivalent browse fields GETBRWA and
    GETBRWS):
    Prior to the introduction of selectors, the distinction between
    a generic get (getting any available message) and a specific
    get (get only a subset of messages) was only relevant to
    getters specifying one or more of the match options in the
    MQGMO. The accounting data was recorded in GETS if any match
    options were used, and all other gets were recorded in GETA.
    
    Selectors have introduced another way of specifying a criteria
    for getting only a subset of messages on a queue. However, the
    statistics logic wasn't changed to reflect this. As a result,
    gets with selectors are currently recorded in GETA.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 0 Modification 0 and Release 1       *
    *                 Modification 0.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using selectors on an MQOPEN call  *
    *                      of a queue, not all of the relevant     *
    *                      fields are populated in the SMF data.   *
    ****************************************************************
    The logic that is used to detect selectors in the MQSUB call was
    not implemented in the MQOPEN call meaning selector specific
    fields in the SMF data were not being populated when using
    selectors on an MQOPEN of a queue.
    

Problem conclusion

  • A similar logic that is used in the MQSUB call has now been
    implemented in the MQOPEN. This means selector specific fields
    are now populated in the SMF data when using an MQOPEN call of
    a queue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH08561

  • Reported component name

    IBM MQ Z/OS VUE

  • Reported component ID

    5655VU900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-14

  • Closed date

    2020-03-11

  • Last modified date

    2020-06-01

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

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

    UI68312 UI68313

Modules/Macros

  • CSQ7COLL
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI68313

       UP20/05/28 P F005

  • R100 PSY UI68312

       UP20/05/28 P F005

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
02 June 2020