APAR status
Closed as program error.
Error description
The following error message is a sample recorded in the queue manager error log. AMQ9469: Update not received for CLUSRCVR channel ClusterName.QmgrName hosted on queue manager QmgrName_2018-01-14_17.42.01 in cluster ClusterName. EXPLANATION: The repository manager detected that the CLUSRCVR channel has not been re-published by its owning queue manager. This re-publish action should have happened automatically XX days ago, or in the time between then and now. ---------------------------------------------------------------- The above error message would be seen when the the cluster transmission queue is configured with a custom expiration time using CUSTOM(CAPEXPRY(n)). Refer to: Enforcing lower expiration times https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com. ibm.mq.ref.dev.doc/q097495_.htm
Local fix
Remove the custom expiry time from the cluster transmit queue.
Problem summary
**************************************************************** USERS AFFECTED: Users who have set capped expiry times on their cluster transmission queues using CUSTOM(CAPEXPRY(n)). Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: Expiry times of around 30 days are set on cluster internal state messages by IBM MQ, and it is not appropriate to have these expiry times reduced. If the cluster transmission queue is configured with a custom expiration time lower than 30 days, internal MQ cluster state update messages being sent to Full Repositories can expire prematurely and are not sent. This causes the AMQ9469 message in the MQ error logs. Capped expiry times are set using CUSTOM(CAPEXPRY(n)) in a DEFINE QLOCAL or ALTER QLOCAL command.
Problem conclusion
The MQ code has been modified such that the cluster repository manager process will ignore a configured CAPEXPRY value when it puts internal state messages to cluster transmission queues. CUSTOM(CAPEXPRY(n)) should not be used on any queues that will hold MQ internally-generated messages. For example, any SYSTEM.CLUSTER.* queue, the SYSTEM.PROTECTION.POLICY.QUEUE, etc. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.12 v9.0 LTS 9.0.0.7 v9.1 CD 9.1.3 v9.1 LTS 9.1.0.3 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT28022
Reported component name
IBM MQ BASE MP
Reported component ID
5724H7251
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-02-07
Closed date
2019-03-22
Last modified date
2019-05-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
IBM MQ BASE MP
Fixed component ID
5724H7251
Applicable component levels
[{"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.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
09 May 2019