A fix is available
APAR status
Closed as program error.
Error description
When MQ activity recording is enabled, a message exit is used on a channel, and that channel receives a trace route message, this may result in an ABEND in Metal C code. In this case MQ incorrectly fails to turn on trace route processing which results in messages being incorrectly processed. This can result in a loop adding trace route data to a valid message, followed by a subsequent abend. . Additional keywords: ABEND0C4 ABENDS0C4 0C4 00C4 S0C4 S00C4 00000004 00000011
Local fix
Turn off activity recording via ALTER QMGR ACTIVEREC(DISABLED)
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM MQ for z/OS Version 9 * * Release 0 Modification 0 and Version 9 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: When a queue manager with activity * * reporting enabled receives a trace * * route message that fails a message * * exit, trace route processing does not * * get turned off and therefore subsequent * * messages are incorrectly getting trace * * route data appended. This may cause a * * storage overlay which can cause * * unpredictable behaviour and can result * * in an abend. * **************************************************************** When a queue manager has both activity reporting enabled and a message exit defined on a receiver channel receives a trace route message that fails in the message exit, trace route reporting does not get turned off. As a side effect of this the final activity report is not sent. Therefore when subsequent messages flow over the channel they are incorrectly appended with trace route data which may cause a storage overlay which can cause unpredictable behaviour and can result in an abend.
Problem conclusion
When a message fails on a message exit for a receiver channel there is now a check if trace route processing is turned on. If trace route processing is on then it will be turned off to ensure future messages are not treated as trace route messages. If there is an outstanding activity report then it will be sent prior to the reset.
Temporary fix
Comments
APAR Information
APAR number
PH18843
Reported component name
IBM MQ Z/OS V8
Reported component ID
5655W9700
Reported release
000
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-11-05
Closed date
2020-02-12
Last modified date
2020-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI67848 UI67850
Modules/Macros
CSQXRMTR
Fix information
Fixed component name
IBM MQ Z/OS V9
Fixed component ID
5655MQ900
Applicable component levels
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":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
27 March 2020