A fix is available
APAR status
Closed as program error.
Error description
1. An MQ client puts a message on the OTMA-Q consisting of an IMS command 2. The MQ IMS Bridge puts the COA message on the Reply-Q 3. The IMS reply message arrives on the Reply-Q 4. The MQ client does an MQGET of the COA message from the Reply-Q. In case of V701, the COA (Confirm on Arrival) WITH DATA report message contains message data which starts with the IIH header. The data length is 64 bytes and contains the IMS command, which is correct. However in the case of V710, the COA WITH DATA report message contains message data which starts with an MD. The data length is 64 bytes but doesn't contain the IIH or IMS command, which is wrong. The problem is the COA WITH DATA report message contains the message data which starts with an MD. This means there is an MD followed by another MD. In both cases, the MQMD has a FORMAT field of MQIMS. The V701 data starts with these eyecatchers: | IIH ............ | | ...sMQIMSVS .... | | | | MQIMSVS ........ | The V710 data starts with these eyecatchers: | MD .......{.... | | ...............s | | MQIMS ........ | Additional Symptom(s) Search Keyword(s): 2142
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: COA, exception, and expiry report * * messages generated by the IMS bridge * * contain invalid data, leading to * * applications processing these messages * * failing MQRC_HEADER_ERROR (2142). * * * * In some cases, abend 5C6-00F20058 * * occurs in module CSQ2QCP0, and is * * accompanied by message CSQ2004E * * "ERROR USING QUEUE xx, MQRC=2004" * **************************************************************** * RECOMMENDATION: * **************************************************************** When CSQ2QCP0 generates report messages an error in one of the parameters it passes to a subroutine cause the wrong address to be passed to MQPUT1 when putting the report message to the reply to queue. Depending on the contents of the wrong address, invalid data can be included in the report message, or the MQPUT1 request can fail with MQRC_BUFFER_ERROR (2004), resulting in message CSQ2004E and abend 5C6-00F20058 being issued.
Problem conclusion
CSQ2QCP0 is changed to pass the address of the report message to MQPUT1 correctly. 100Y CSQ2QCP0
Temporary fix
Comments
APAR Information
APAR number
PI52379
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
2015-11-12
Closed date
2015-11-27
Last modified date
2016-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI33366
Modules/Macros
CSQ2QCP0
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R100 PSY UI33366
UP16/01/08 P F601
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:
01 February 2016