A fix is available
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 7 * * Release 1 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 (or MQSET) 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. 100Y CSQIDPUT CSQIERS3 CSQIMPUT CSQIMPU2 CSQIPUT1 CSQIPUT2 CSQIPUT5 CSQMCNA1 CSQMPOM CSQMSET CSQMTRG0
Temporary fix
Comments
APAR Information
APAR number
PI74278
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
2016-12-30
Closed date
2017-07-25
Last modified date
2017-10-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI79931 UI47870
Modules/Macros
CSQIDPUT CSQIERS3 CSQIMPUT CSQIMPU2 CSQIPUT1 CSQIPUT2 CSQIPUT5 CSQMCNA1 CSQMPOM CSQMSET CSQMTRG0
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R100 PSY UI47870
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":"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:
02 October 2017