A fix is available
APAR status
Closed as unreproducible in next release.
Error description
RIDS/CSQILPLM#L RIDS/CSQIMPU2 AB/S00C4 PRCS/00000010 The abend occurs when attempting to put a COD report message to the dead-letter queue (in this case the COD is going to the DLQ as ReplyToQ does not exist). The problem is that CSQMREPM is invoking CSQMDLQP with the asid for the message data (and also the key) set to that of the queue-manager, but the message data is actually in the application address space, hence the 0C4 occurs in subsequent processing.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 0 Modification 1. * **************************************************************** * PROBLEM DESCRIPTION: Issuing an MQGET on a message with * * report option MQRO_COD_WITH_DATA set, * * if the put to the specified reply to * * queue fails (such as MQRC 2085, queue * * not found), may result in a 0C4 abend * * in CSQIMPU2, with no dump taken. * **************************************************************** * RECOMMENDATION: * **************************************************************** An MQGET of a message with a COD with data report type set (MQRO_COD_WITH_DATA and MQRO_COD_WITH_FULL_DATA), if the PUT of the report message to the specified reply to queue (ReplyToQ) fails, an attempt to put the report to the dead letter queue can result in a 0C4 abend. The abend does not cause a dump to be taken, and is shown in the getting application. No report is put to the dead letter queue. This occurs when the report message is attempted to be put to the dead letter queue, the put attempts to access the original messages buffer in the queue manager address space, when the message data in this scenario is in the applications address space.
Problem conclusion
Temporary fix
Comments
The process to put a report to the dead letter queue has been altered to ensure the message data put to the queue is accessed through the correct address space of the message buffer. This ensures the message buffer can be accessed without the 0C4 abend, and the resulting report contains the correct data.
APAR Information
APAR number
PM91058
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
010
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-06-13
Closed date
2013-06-26
Last modified date
2013-09-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK95414
Modules/Macros
CSQMREPM
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R010 PSY UK95414
UP13/08/23 P F308
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:
03 September 2013