IBM Support

PI55568: A LOGICAL GROUP FLAG HAS BEEN SET DUE TO RSTCHECKFORONEMESSAGE IN THE CHIN ISSUING AN MQGET WITH A 'DIRTY' V2 MQMD.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A logical group flag has been set due to rstCheckForOneMessage
    in the CHIN issuing an MQGET with a 'dirty' V2 MQMD.
    The problem occurs when the last byte of MQMD MQMD.MsgFlags
    has a residual value with either the x10 or x08 bit set.
    The MQMD.MsgFlags are copied by CSQMGGRV into an internal
    MDE, and this internal MDE is used by CSQMGET at the
    end of MQGET processing to see if MQGS_LAST_MSG_IN_GROUP
    or MQGS_MSG_IN_GROUP needs to be set.
    ..
    Additional Symptom(s) Search Keyword(s):
    
    +0060 FFFFFFFF 00000000 00000000 00000000 | ................ |
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: An MQGET may return incorrect flags in  *
    *                      the returned GMO, when the message      *
    *                      retrieved is not representative of the  *
    *                      flags, when MsgFlags are set in the MD  *
    *                      or MDE passed to the MQGET call.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a MQGET call is made, the MQMD or MQMDE passed with the
    call is used for later processing. When the MsgFlags field is
    set, such as MQMF_MSG_IN_GROUP or MQMF_LAST_MSG_IN_GROUP these
    may be kept during the MQGET processing. With these fields set,
    the GMO returned with MQGET call can have GroupStatus field set
    to a value showing the message returned is a member of a group
    or last message in a group, even when the message retrieved is
    not in a message group.
    
    This problem is caused by the MQMDE passed in (or extracted from
    the MD) being used during the internal get from the specified
    queue. Some of the flags, which control the status flags
    returned in the MQGMO, are not cleared, resulting in the later
    processing of the MQGET setting the GMO flags, possibly
    incorrectly if the message retrieved does not represent this
    status.
    

Problem conclusion

  • The processing for an MQGET in this circumstance has been
    altered to ensure the MD is valid and clean prior to the setting
    the GMO.GroupStatus, to ensure the correct output is returned.
    000Y
    CSQMGET
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI55568

  • Reported component name

    WMQ Z/OS 8

  • Reported component ID

    5655W9700

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-18

  • Closed date

    2016-01-27

  • Last modified date

    2016-04-05

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

    PI52073

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

    UI34769

Modules/Macros

  • CSQMGET
    

Fix information

  • Fixed component name

    WMQ Z/OS 8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY UI34769

       UP16/03/03 P F603

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":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
05 April 2016