IBM Support

PI42711: MQ Z/OS V7.1: A TRANSACTION EXPIRES IN IMS DFS3688I IS RETURNED WHEN EXPIRY VALUE AND NO REPORT OPTION ARE SET ON INPUT MESSAGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using MQ v7.1 and IMS v13 customer was testing MQ/IMS bridge
    transactions expiration in IMS.
    If the transaction expires in IMS they do not expect a reply to
    be sent unless a report has been requested.
    They found that:
    If they request an expiry report then they correctly get
    the reply message with MQMD-FEEDBACK set to 258, and no
    DFS3688I message.
    However if they specify no MQMD-REPORT option on the input
    message, they still receive a reply from IMS which is a
    DFS3688I message.
    
    If a message with the same expiry and report setting is expired
    by OTMA rather than IMS, then
    a message is not returned to the application so there is an
    inconsistency here.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: A DFS3688I reply message is put to the  *
    *                      reply queue when IMS expiry is enabled  *
    *                      in the IMS bridge, and an IMS bridge    *
    *                      transaction expires, even if no         *
    *                      expiration reports were requested.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a message is put to an IMS bridge queue with an Expiry
    value in the MQMD, and no expiration reports are requested in
    the MQMD Report field (MQRO_EXPIRATION*), no reply should be
    returned to the application if the transaction expires, however
    CSQ2QCP1 does not account for this and incorrectly puts the
    DFS3688I (transaction expired) response to the reply queue.
    

Problem conclusion

  • CSQ2QCP1 is changed to no longer put the DFS3688I response to
    the reply queue if the request message specified an expiry
    interval in the MQMD and no expiration report options. The
    response will still be put if the request message specified
    unlimited expiry (MQEI_UNLIMITED) and the transaction expired
    for some other reason (for example, if the transaction is
    defined to IMS with the EXPRTIME parameter).
    100Y
    CSQ2MTOO
    CSQ2OTOM
    CSQ2QCP1
    

Temporary fix

Comments

  • ×**** PE16/02/16 FIX IN ERROR. SEE APAR PI57299  FOR DESCRIPTION
    ×**** PE16/04/28 FIX IN ERROR. SEE APAR PI61445  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI42711

  • 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-06-10

  • Closed date

    2015-09-25

  • Last modified date

    2016-05-16

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

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

    PI48687 UI31498

Modules/Macros

  • CSQ2MTOO CSQ2OTOM CSQ2QCP1
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI31498

       UP15/11/11 P F511

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:
16 May 2016