A fix is available
APAR status
Closed as program error.
Error description
There is a problem with a discrepancy between the data in a CF structure and the data in the SMDS dataset. The following error messages are issued: CSQI034E =xxxx CSQELBK1 Block 1 of the message data for entry id xxxxxxxxxxxxxxxxxxxxxxxx in CFSTRUCT(sssssss) refers to SMDS(ssid) control interval xxxxxxxx but the stored data does not match the entry id CSQE006I xxxx CSQECLOS Structure CSQ_ADMIN connection name CSQEyyyyxxxx02 disconnected *CSQV086E =xxxx QUEUE MANAGER ABNORMAL TERMINATION REASON=00C510AB RC=00000B08,xxxx,ABN=5C6-00C94522, LOC=CSQELPLM.CSQELBK1 CSQE006I =xxxx CSQECLOS Structure CSQ_ADMIN connection name CSQEyyyyxxxx02 disconnected CSQV086E =SQ3C QUEUE MANAGER ABNORMAL TERMINATION REASON=00C510AB This problem appears when the control information related to a SMDS dataset has more than DSBLOCK - 4K, in this case 4K, during disconnection of a SMDS dataset.
Local fix
Use a higher DSBLOCK value. The default value of 256K allows for 63GB to be used for data before a second space map is required.
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 * * Release 0 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: CSQI034E 'Block x of the message data * * for entry id xxxxxxxxxxxxxxxxxxxxxxxx * * in CFSTRUCT(ssssssss) refers to * * SMDS(ssid) control interval xxxxxxxx * * but the stored data does not match the * * entry id' and abend 5C6-00C94522 occur * * when using SMDS. * * Additional symptoms that can also occur * * depending on the operation encountering * * the error include: * * - CSQI037I reporting that the affected * * non-persistent message was deleted * * - CSQI036I reporting that the * * structure was marked as failed * * - abnormal queue manager termination * * 6C6 with REASON=00C510AB * **************************************************************** * RECOMMENDATION: * **************************************************************** When disconnecting from a structure configured to use SMDS, each spacemap block that has been used is stored in the SMDS. If multiple spacemap blocks have been used (i.e. if more data has been stored in the SMDS than the first spacemap block can cover), all of the spacemap blocks are stored contiguously at the start of the SMDS, overlaying message data blocks. When an attempt is made to read messages using the overlaid blocks (for example, by MQGET or BACKUP CFSTRUCT), the overlay is detected, leading to the reported abend. If the affected message is non-persistent, it is deleted. If the affected message is persistent, the structure containing the message is failed so that the message can be recovered from the logs during structure recovery, however when the spacemap is stored at the end of structure recovery processing the same problem occurs, reintroducing the overlay.
Problem conclusion
CSQEDSS1 is changed to fetch/store additional spacemaps from the correct location, immediately before the range of blocks covered by each spacemap block. In addition it will detect when spacemap blocks were stored in the wrong location, in which case the spacemap will be rebuilt. CSQEDSS4 is changed to validate any blocks that were potentially overlaid while rebuilding the spacemap to detect any damaged messages. CSQI034E will be issued for each damaged message detected and the following action will be taken: - non-persistent messages that are damaged will be deleted. CSQI037I will be issued for each non-persistent message that is deleted. - if any persistent messages are damaged, CSQI036I is issued and the structure will be failed, allowing the damaged message to be restored when the structure is recovered. MQSMDS/K 000Y CSQEDSS1 CSQEDSS4
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI42580
Reported component name
WMQ Z/OS 8
Reported component ID
5655W9700
Reported release
000
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-09
Closed date
2015-07-23
Last modified date
2015-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI29658
Modules/Macros
CSQEDSS1 CSQEDSS4
Fix information
Fixed component name
WMQ Z/OS 8
Fixed component ID
5655W9700
Applicable component levels
R000 PSY UI29658
UP15/08/11 P F508 ¢
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":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
02 September 2015