A fix is available
APAR status
Closed as program error.
Error description
CSQX469E Update not received for CLUSRCVR channel <channel-name> hosted on queue manager <qmid> in cluster <cluster_name>, expected <n> days ago, <m> days remaining is reported on the MQ cluster Full Repository queue manager only. A Partial Repository queue manager does not report CSQX469E when the update is not received from a specific cluster queue manager. It will remove the cluster queue manager and all related cluster resource associated with this cluster queue manager from cluster repos cache 60 days later. Then reason code 2041 MQRC_OBJECT_CHANGED error is thrown when accessing the cluster queue associated with this cluster resource afterwards.
Local fix
REFRESH CLUSTER(cluster-name) REPOS(YES) can help to refresh cluster repos cache and work around the problem.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM MQ for z/OS Version 9 * * Release 1 Modification 0 and Release 2 * * Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: When a full or partial repository has * * a queue where an update would be * * expected but hasn't been received, a * * CSQX456I message is issued. For queue * * manager objects in the same situation, * * a full repository will issue a CSQX469E * * message, but partial repositories * * don't issue a message for the queue * * manager object. * **************************************************************** The partial repository queue manager intentionally didn't issue a message for the QMGR object that is out of sync in the cluster.
Problem conclusion
The code has now been changed to issue a CSQX456I message in the partial repository for the queue manager object that is out of sync in the cluster. The IBM MQ for z/OS Version 9.1.x and Version 9.2.x Knowledge Center are updated: IBM MQ 9.1.x/9.2.x IBM MQ Reference Messages IBM MQ for z/OS messages, completion, and reason codes Messages for IBM MQ for z/OS Distributed queuing messages (CSQX...) CSQX456I/E (https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/ com.ibm.mq.ref.doc/csq_x.html) (https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.2.0/ com.ibm.mq.ref.doc/csq_x.html) Changed message CSQX456I: " csect-name Full repository update not received, cluster cluster_ name queue q-name (queue manager qmgr-name) " is changed to " csect-name Full repository update not received, cluster cluster_ name cluster object object_name (queue manager qmgr_uuid) " " Explanation The repository manager found a cluster queue that had been used sometime in the last 30 days, and for which updated information should have been received. However, no such information has been received. The queue is q-name in cluster_name, and its queue manager is qmgr-name. If the queue manager is a partial repository for the queue, the updated information should have been sent from a full repository . If the queue manager is a full repository, the updated information should have been sent from the queue manager on which the queue is defined. " is changed to " Explanation The repository manager found a cluster object that had been used sometime in the last 30 days, and for which updated information should have been received. However, no such information has been received. The cluster object is object_name in cluster_name, and its queue manager is qmgr_uuid. If the queue manager is a partial repository for the object, the updated information should have been sent from a full repository. If the queue manager is a full repository, the updated information should have been sent from the queue manager on which the object is defined. " " System action The repository manager keeps information about this queue for a further 60 days from when the error first occurred. If information has not been sent to a full repository then this queue is not used to satisfy any new requests for cluster resources made to this full repository. " is changed to " The repository manager keeps information about this object for a further 60 days from when the error first occurred. If information has not been sent to a full repository then this object is not used to satisfy any new requests for cluster resources made to this full repository. " " System programmer response If the queue is still required, check that: -The cluster channels to and from the queue manager that is the full repository for the cluster, and between there and the queue manager where the queue is located, are able to run. -The repository managers on those queue managers have not ended abnormally. " is changed to " System programmer response If the object is still required, check that: -The cluster channels to and from the queue manager that is the full repository for the cluster, and between there and the queue manager where the object is located, are able to run. -The repository managers on those queue managers have not ended abnormally. " Additionally, the Version 9.2.x Knowledge Centre CSQX456E message is updated with: " System programmer response If the queue is still required, check that: -The cluster channels to and from the queue manager that is the full repository for the cluster, and between there and the queue manager where the queue is located, are able to run. -The repository managers on those queue managers have not ended abnormally. -There is not a long-running problem with the cluster receiver channel to the local queue manager in cluster cluster_name. If there is a problem, correct the problem urgently, to ensure that updates for the cluster are received. -There is not a long-running problem on the cluster sender channel of the remote queue manager in cluster cluster_name. If there is a problem, correct the problem urgently, to ensure that updates for the cluster are sent. -The remote queue manager is not out of step with this queue manager, potentially due to a restore of the remote queue manager from a backup. If the remote queue manager is out of step, issue a REFRESH CLUSTER command on the remote queue manager to synchronize with other queue managers in the cluster. -The remote queue manager is not out of step with this queue manager, potentially due to a disaster recovery exercise in which a replacement queue manager with the same cluster receiver channel name was created, was run for a while, then ended. If this has happened, then the remote queue manager qmgr-name must now issue a REFRESH CLUSTER command to synchronize with other queue managers in the cluster. -If the above items have been checked, and this problem persists over several days (causing repeats of this error message in the error logs of the local queue manager) contact your IBM support center. " is changed to " System programmer response If the object is still required, check that: -The cluster channels to and from the queue manager that is the full repository for the cluster, and between there and the queue manager where the object is located, are able to run. -The repository managers on those queue managers have not ended abnormally. -There is not a long-running problem with the cluster receiver channel to the local queue manager in cluster cluster_name. If there is a problem, correct the problem urgently, to ensure that updates for the cluster are received. -There is not a long-running problem on the cluster sender channel of the remote queue manager in cluster cluster_name . If there is a problem, correct the problem urgently, to ensure that updates for the cluster are sent. -The remote queue manager is not out of step with this queue manager, potentially due to a restore of the remote queue manager from a backup. If the remote queue manager is out of step, issue a REFRESH CLUSTER command on the remote queue manager to synchronize with other queue managers in the cluster. -The remote queue manager is not out of step with this queue manager, potentially due to a disaster recovery exercise in which a replacement queue manager with the same cluster receiver channel name was created, was run for a while, then ended. If this has happened, then the remote queue manager qmgr_uuid must now issue a REFRESH CLUSTER command to synchronize with other queue managers in the cluster. -If the above items have been checked, and this problem persists over several days (causing repeats of this error message in the error logs of the local queue manager) contact your IBM support center. "
Temporary fix
Comments
APAR Information
APAR number
PH34265
Reported component name
IBM MQ Z/OS V9
Reported component ID
5655MQ900
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-02-08
Closed date
2021-03-10
Last modified date
2024-02-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI74357 UI74358
Modules/Macros
CMQXRMNT CSQFXLAT
Fix information
Fixed component name
IBM MQ Z/OS V9
Fixed component ID
5655MQ900
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"100","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]
Document Information
Modified date:
02 February 2024