IBM Support

PI79931: WMQ TRIGGER MESSAGE FOR APPLICATION IS NOT GENERATED FOR TRIGTYPE(DEPTH)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Change team finds that a trigger message has not been generated
    as expected. It occurs as the MQPUT of the second message was
    started when the queue had NOTRIGGER (before the ALTER command
    against the queue) A copy of the object is taken at the start of
    the MQPUT processing and is used to check for triggering once
    the message had been put to the queue. In this case the message
    is very large and the ALTER command was able to complete before
    the MQPUT had completed, resulting in this situation with a
    trigger message not being generated.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Trigger messages can be missing in      *
    *                      initiation queues when putting messages *
    *                      to queues with trigger type MQTT_DEPTH. *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a local queue has triggering configured with trigger type
    MQTT_DEPTH, trigger is off (NOTRIGGER) and an application puts a
    message reaching the trigger depth threshold that is processed
    concurrently with the command ALTER QLOCAL(nnn) TRIGGER (or
    MQSET) can result in the trigger message not being generated in
    the initiation queue.
    
    The trigger message is not generated because MQPUT does not
    detect that triggering has been enabled and the ALTER command
    does not see the message that causes the queue DEPTH to reach
    the trigger depth threshold.
    

Problem conclusion

  • The process for trigger type MQTT_DEPTH has been changed to
    synchronize the MQPUT process and the ALTER (or MQSET) command
    to avoid missing the generation of trigger messages.
    000Y
    CSQIDPUT
    CSQIERS3
    CSQIMPUT
    CSQIMPU2
    CSQIPUT1
    CSQIPUT2
    CSQIPUT5
    CSQMCNA1
    CSQMPOM
    CSQMSET
    CSQMTRG0
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI79931

  • 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

    2017-04-13

  • Closed date

    2017-07-25

  • Last modified date

    2017-10-02

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

    PI74278

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

    PI79932 UI48305

Modules/Macros

  • CSQIDPUT CSQIERS3 CSQIMPUT CSQIMPU2 CSQIPUT1 CSQIPUT2 CSQIPUT5
    CSQMCNA1 CSQMPOM  CSQMSET  CSQMTRG0
    

Fix information

  • Fixed component name

    WMQ Z/OS 8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY UI48305

       UP17/09/07 P F709

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:
02 October 2017