A fix is available
APAR status
Closed as program error.
Error description
CURDEPTH value of the same shared queue is non-zero on one queue manager while it is zero on other queue manager in one queue sharing group. Customer has defined all of the queues etc and then backed-up the CF structures and taken copies of the queue- managers' logs and page-sets as well as image copies of the DB2 tables. All of these copies have been taken before "the queues in question" have been used (i.e. no MQOPENs). Customer has not used "the queues in question" before they copied CF structures, logs, image copies and so on. But some queues which are not related to this problem have been used before the copies have been taken. Then customer has restored the page-sets and logs from the copies taken, as well as the DB2 tables from the image copies. The problem then occurs after recovering the CF structures. Additional Symptom(s) Search Keyword(s):
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 0 Modification 1 and WebSphere MQ * * for z/OS Version 7 Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: Following structure recovery, the * * CURDEPTH value returned from the DIS Q * * command may not be consistent for * * members of a queue sharing group. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a structure in a queue sharing group is recovered, an LHQC is written to it for a previously defined shared queue that has never been opened. When an application then opens the queue, since the LHQC already exists, other queue managers in QSG do not get informed about the use of this queue. Once a message is put on the queue, a DIS Q command displays a CURDEPTH of 1 for the qmgr on which the open occurred. However, since the MQSH.CFCACHE flag has not been set for other qmgrs, they return a CURDEPTH of 0 from a DIS Q command for the same queue.
Problem conclusion
Code has been changed to prevent creation of the LHQC during structure recovery if the MQSH.CFCACHE is off. 010Y 100Y CSQERCF3
Temporary fix
Comments
APAR Information
APAR number
PI45688
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
010
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-07-26
Closed date
2015-08-24
Last modified date
2015-11-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI46958 UI30445 UI30446
Modules/Macros
CSQERCF3
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
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":"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 November 2015