IBM Support

PM83397: WMQ Z/OS:MQRC_MATCH_OPTIONS_ERROR BEING RETURNED ON SVRCONN CHANNEL AFTER MIGRATING TO V701.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MsgSeqNumber is not being correctly set
    when a client channel uses async consume
    to get the message, leading to
    MQRC_MATCH_OPTIONS_ERROR.
    .
    In the GTF trace, check the trace entry
    of CSQMGETV.  You will not find MSGSEQNUMBER
    field in the trace.
    The MQRC_MATCH_OPTIONS_ERROR (x'000008C7) is set
    in CSQMGSGW.
    

Local fix

  • Change the SHARECNV parameter for SVRCONN
    channel to zero;  SHARECNV(0).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 0 Modification 1 and WebSphere MQ    *
    *                 for z/OS Version 7 Release 1 Modification 0. *
    ****************************************************************
    * PROBLEM DESCRIPTION: A MQGET with wait, with a match option  *
    *                      of MQMO_MATCH_MSG_SEQ_NUMBER, from a    *
    *                      V7+ client, with SHARECNV > 0 on the    *
    *                      channel the client uses, can result     *
    *                      in MQRC_MATCH_OPTIONS_ERROR.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    MQRC_MATCH_OPTIONS_ERROR may occur when a valid MsgSeqNumber is
    provided, with match option MQMO_MATCH_MSG_SEQ_NUMBER specified,
    on a V7+ client MQGET. This only occurs with a V7+ client
    application with get message option MQGMO_WAIT, with the client
    application connection through a channel with SHARECNV set as a
    value greater than 0.
    
    This is due to the MsgSeqNumber field of the MQMD passed into
    the MQGET request not being correctly copied internally within
    the queue manager for this scenario. When the match processing
    is executed, this field is not found, which causes the
    MQRC_MATCH_OPTIONS_ERROR.
    

Problem conclusion

  • The code has been amended to ensure the passed in MsgSeqNumber
    field of the MQMD is copied correctly internally in the queue
    manager in this case. This should ensure the match will work
    correctly, returning matching messages and not returning
    MQRC_MATCH_OPTIONS_ERROR when the match options are valid.
    010Y
    100Y
    CSQMGETV
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM83397

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    010

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-02-22

  • Closed date

    2013-03-18

  • Last modified date

    2013-06-04

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

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

    UK92613 UK92614

Modules/Macros

  • CSQMGETV
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UK92613

       UP13/05/08 P F305

  • R100 PSY UK92614

       UP13/05/08 P F305

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.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 June 2013