A fix is available
APAR status
Closed as program error.
Error description
Customer complained CSQX053E and CSQX456I for queue objects and a kind of following messages were shown in CHIN joblog: CSQX053E CSQXFFST Error information recorded in CSQSNAP data set CSQX456I CSQXREPO Full repository update not received, cluster CLUS01 queue Q1 (queue manager CSQ1) PSW at entry to snap shows: * X...XFFSrrmCheck * *SubsForQueue............MOVR....* *......3.X...XINS................ * ... * ....Missing subscription * *WQR .......M....Q1 * *CSQ1 * The issue occurs when a cluster object (in this case a queue) is not used on a partial repository for some time (more than 30 days). As the object is not in use, the subscriptions for that object expire, but the object remains in the cluster cache. If the qmgr is added to another cluster, then there will be new subscriptions created for the queue in the new cluster. However, as the subscriptions for the existing clusters had expired, this will result in a mismatched set of subscriptions for the object.
Local fix
REFRESH CLUSTER can fix the messages CSQX053E and CSQX456I.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM MQ for z/OS Version 9 * * Release 0 Modification 0 and Release 1 * * Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: CSQX456I is issued during cluster * * maintenance processing reporting * * missing updates from the Full * * repositories for a cluster queue. * * * * CSQX053E is also issued, and an FFST * * reporting "Missing subscription" is * * written to the CSQSNAP DD card by * * rrmCheckSubs. * **************************************************************** The cluster cache for a partial repository queue manager contained one or more cluster queue objects that were in the grace period, and consequently had no subscriptions. When the queue manager was added as a partial repository to another cluster, a subscription was made for these cluster queues in the new cluster. When the queue was next used, the existing subscription in the second cluster was found, and so no new subscriptions were created, and the queue was marked as in use. When cluster maintenance next ran, it detected that the affected cluster queues had no subscriptions for the cluster they were in, and captured the FFST to report the unexpected state.
Problem conclusion
When a queue manager is added to a new cluster as a partial repository, it will create a subscription for any locally known queues in the cluster cache for each cluster in which it is a partial repository.
Temporary fix
Comments
APAR Information
APAR number
PH19559
Reported component name
IBM MQ Z/OS V9
Reported component ID
5655MQ900
Reported release
000
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-11-22
Closed date
2019-12-09
Last modified date
2020-09-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI66876 UI66877
Modules/Macros
CSQXRRMF
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.
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0"}]
Document Information
Modified date:
24 September 2020