A fix is available
APAR status
Closed as program error.
Error description
An ABEND S0C4-10 occurs in CSQIMPU2 right before an S0E0-31 ABEND in MVMQ CSECT MMAHPCST. PIDS/5655R3600 RIDS/CSQILPLM#L RIDS/CSQIMPU2 AB/S00C4 PRCS/00000010 REGS/C7B84 RIDS/CSQGFRCV#R SYMPTOM DESCRIPTION ------- ----------- PIDS/5655R3600 PROGRAM ID: 5655R3600 RIDS/CSQILPLM#L LOAD MODULE NAME: CSQILPLM RIDS/CSQIMPU2 CSECT NAME: CSQIMPU2 AB/S00C4 SYSTEM ABEND CODE: 00C4 PRCS/00000010 ABEND REASON CODE: 00000010 REGS/C7B84 REGISTER/PSW DIFFERENCE FOR R0C:-7B84 RIDS/CSQGFRCV#R RECOVERY ROUTINE CSECT NAME: CSQGFRCV DATE ASSEMBLED: 20140620 MODULE LEVEL: UI19014 SUBFUNCTION: DMC CSQIMPU2CSQIMPU2-R Additional Symptom; ABN=0C4-00000010 taken in CHIN LOC=CSQMLPLM.CSQMPOM +
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: When event messages are enabled, if the * * system event queue is defined as an * * alias queue to a topic, the put * * processing to the QAlias may abend * * 0C4-00000010 in CSQIMPU2. * * * * Additionally after this abend, if a * * vendor product is hooked into MQ, * * following the 0C4, a 0E0-00000031 abend * * may also been seen. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the event message is being put to the event queue, in the case where it is a QAlias which targets a topic, the ASID of the message buffer of the event message is set to the application address space. However the message buffer is actually within the queue managers address space, which results in the 0C4-00000011 abend. Following this, when a vendor product is being used, a 0E0-00000031 abend may occur as recovery processing following the 0C4 does not set the linkage stack level, SDWALSLV, correctly.
Problem conclusion
Event message processing has been changed for this scenario, to use the correct ASID for the message buffer, when putting the event message to a topic in this scenario. Additionally recovery processing has been updated, to correctly handle saving the linkage stack position, when a vendor hook is being used with MQ. 100Y CSQGFRCV CSQIMPU2 CSQMIARC
Temporary fix
Comments
APAR Information
APAR number
PI56213
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-01-28
Closed date
2016-07-08
Last modified date
2016-08-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
CSQGFRCV CSQIMPU2 CSQMIARC
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R100 PSY UI39250
UP16/07/28 P F607
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:
12 August 2016